Bensuperpc/dockcross
1
0
Fork 0
mirror of https://github.com/bensuperpc/dockcross.git synced 2024-11-10 05:07:26 +01:00
Code Issues Packages Projects Releases Wiki Activity
8ad158c976
dockcross/manylinux1-x64/Dockerfile.in

38 lines
1.1 KiB
Docker
Raw Normal View History

manylinux: Reference custom manylinux images providing Python3.8 This commit updates the version of manylinux base images to use custom flavor having Python 3.8. See https://github.com/scikit-build/manylinux#available-branches Python 3.8.0a2 was initially added to upstream manylinux after integrating https://github.com/pypa/manylinux/pull/273. But considering that Python 3.8 is still an alpha release and that (1) the associated ABI is not yet stable and (2) incompatibilities are expected between wheels generated for alpha/beta/rc and final version of python 3.8.0, the manylinux maintainers decided to revert the update.
2019-03-02 00:19:49 +01:00
FROM scikitbuild/manylinux1_x86_64:91cb02fb8
manylinux-x64: Initial addition
2016-09-20 17:35:18 +02:00
MAINTAINER Matt McCormick "matt.mccormick@kitware.com"
Rename manylinux images to manylinux1
2019-05-22 09:05:11 +02:00
ENV DEFAULT_DOCKCROSS_IMAGE dockcross/manylinux1-x64
manylinux-x86: Fix build of Openssl and CMake This commit fixes the error reported below by ensuring openssl and CMake are configured and build as x86 binaries. It also removes the download of CMake binaries that was introduced by mistake in 1354fe2 (manylinux-x86: Initial addition). Error: ``` Configured for linux-x86_64. making all in crypto... make[1]: Entering directory `/usr/src/openssl-1.0.2j/crypto' /usr/bin/perl ../util/mkbuildinf.pl "gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM" "linux-x86_64" >buildinf.h gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -c -o cryptlib.o cryptlib.c cryptlib.c:1:0: sorry, unimplemented: 64-bit mode not compiled in /* crypto/cryptlib.c */ ^ make[1]: *** [cryptlib.o] Error 1 ```
2016-11-05 22:55:58 +01:00
manylinux: Consolidate common content into common.manylinux
2016-11-04 02:33:24 +01:00
#include "common.manylinux"
manylinux: Grant current user password less sudo access. This will allow build script like "build-wheels.sh" to run command like the following (see [1]): sudo yum install -y atlas-devel It will also allow to pip install using sudo and avoid error reported in [3]. That said, instead of running pip using sudo, the recommended approach is to specify the "--user" flag [2] [1] https://github.com/pypa/python-manylinux-demo/blob/893d92517e9e289b9d2ee063f19c3216a39534ab/travis/build-wheels.sh [2] http://stackoverflow.com/questions/7143077/how-can-i-install-packages-in-my-home-folder-with-pip#7143496 [3] Error reported when running pip without "sudo pip install <packagename" or "pip install --user <packagename>" ``` Exception: Traceback (most recent call last): File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/site-packages/pip/basecommand.py", line 215, in main status = self.run(options, args) File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/site-packages/pip/commands/install.py", line 317, in run prefix=options.prefix_path, File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/site-packages/pip/req/req_set.py", line 736, in install requirement.uninstall(auto_confirm=True) File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/site-packages/pip/req/req_install.py", line 742, in uninstall paths_to_remove.remove(auto_confirm) File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/site-packages/pip/req/req_uninstall.py", line 115, in remove renames(path, new_path) File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/site-packages/pip/utils/__init__.py", line 267, in renames shutil.move(old, new) File "/opt/_internal/cpython-2.7.11-ucs2/lib/python2.7/shutil.py", line 303, in move os.unlink(src) OSError: [Errno 13] Permission denied: '/opt/_internal/cpython-2.7.11-ucs2/bin/easy_install' ```
2016-09-22 07:11:12 +02:00
ENH: Compile git with SSL support Older versions of git included in older linux distributions are not able to download source from Github. A newer version is required with a newer OpenSSL. This requires to also build curl with the same OpenSSL. CMake is downloaded precompiled if available (64bits system) or compiled from source otherwise.
2018-04-13 20:56:49 +02:00
#include "common.docker"
manylinux-x64: Initial addition
2016-09-20 17:35:18 +02:00
ENV CROSS_TRIPLE x86_64-linux-gnu
ENV CROSS_ROOT /opt/rh/devtoolset-2/root/usr/bin
base,manylinux-x64: Use sed for Dockerfile composition Suggested-by: Jean-Christophe Fillion-Robin <jchris.fillionr@kitware.com>
2016-09-20 19:17:15 +02:00
ENV AS=${CROSS_ROOT}/as \
AR=${CROSS_ROOT}/ar \
CC=${CROSS_ROOT}/gcc \
CPP=${CROSS_ROOT}/cpp \
CXX=${CROSS_ROOT}/g++ \
Added fortran compiler * Added FC to all Dockerfiles * Changed cmake toolchains to use environment variables for compilers
2018-05-25 18:34:20 +02:00
LD=${CROSS_ROOT}/ld \
FC=${CROSS_ROOT}/gfortran
manylinux-x64: Initial addition
2016-09-20 17:35:18 +02:00
COPY linux-x64/${CROSS_TRIPLE}-noop.sh /usr/bin/${CROSS_TRIPLE}-noop
Rename manylinux images to manylinux1
2019-05-22 09:05:11 +02:00
COPY manylinux1-x64/Toolchain.cmake ${CROSS_ROOT}/../lib/
manylinux-x64: Initial addition
2016-09-20 17:35:18 +02:00
ENV CMAKE_TOOLCHAIN_FILE ${CROSS_ROOT}/../lib/Toolchain.cmake
dockerfile: Keep track of buildtime metadata This commit build each images with the following arguments: * IMAGE: Name of the image (e.g dockcross/base, dockcross/manylinux-x64, ...) * VCS_REF: dockcross/dockcross commit from which this image is built * VCS_URL: this repository obtained reading remote.origin.url * BUILD_DATE: Date and time when the build was initiated Then, within the Dockerfile, the metadata are associated with the image using the "LABEL" instruction. See https://docs.docker.com/engine/reference/builder/#/label The corresponding labels can be found here: http://label-schema.org/rc1/#build-time-labels See #28
2016-10-31 04:57:04 +01:00
# Build-time metadata as defined at http://label-schema.org
ARG BUILD_DATE
Rename manylinux images to manylinux1
2019-05-22 09:05:11 +02:00
ARG IMAGE=dockcross/manylinux1-x64
versioning: Set DEFAULT_DOCKCROSS_IMAGE based on the image tag This ensures that the dockcross script will continue to use the specific tagged version of the image that generates it.
2019-01-13 21:50:24 +01:00
ARG VERSION=latest
dockerfile: Keep track of buildtime metadata This commit build each images with the following arguments: * IMAGE: Name of the image (e.g dockcross/base, dockcross/manylinux-x64, ...) * VCS_REF: dockcross/dockcross commit from which this image is built * VCS_URL: this repository obtained reading remote.origin.url * BUILD_DATE: Date and time when the build was initiated Then, within the Dockerfile, the metadata are associated with the image using the "LABEL" instruction. See https://docs.docker.com/engine/reference/builder/#/label The corresponding labels can be found here: http://label-schema.org/rc1/#build-time-labels See #28
2016-10-31 04:57:04 +01:00
ARG VCS_REF
ARG VCS_URL
LABEL org.label-schema.build-date=$BUILD_DATE \
org.label-schema.name=$IMAGE \
versioning: Set DEFAULT_DOCKCROSS_IMAGE based on the image tag This ensures that the dockcross script will continue to use the specific tagged version of the image that generates it.
2019-01-13 21:50:24 +01:00
org.label-schema.version=$VERSION \
dockerfile: Keep track of buildtime metadata This commit build each images with the following arguments: * IMAGE: Name of the image (e.g dockcross/base, dockcross/manylinux-x64, ...) * VCS_REF: dockcross/dockcross commit from which this image is built * VCS_URL: this repository obtained reading remote.origin.url * BUILD_DATE: Date and time when the build was initiated Then, within the Dockerfile, the metadata are associated with the image using the "LABEL" instruction. See https://docs.docker.com/engine/reference/builder/#/label The corresponding labels can be found here: http://label-schema.org/rc1/#build-time-labels See #28
2016-10-31 04:57:04 +01:00
org.label-schema.vcs-ref=$VCS_REF \
org.label-schema.vcs-url=$VCS_URL \
org.label-schema.schema-version="1.0"
versioning: Set DEFAULT_DOCKCROSS_IMAGE based on the image tag This ensures that the dockcross script will continue to use the specific tagged version of the image that generates it.
2019-01-13 21:50:24 +01:00
ENV DEFAULT_DOCKCROSS_IMAGE ${IMAGE}:${VERSION}
Reference in New Issue Copy Permalink