Annotation of pkgsrc/bootstrap/README.Linux, revision 1.10
1.10 ! gdt 1: $NetBSD: README.Linux,v 1.9 2021/02/12 13:00:48 cjep Exp $
1.1 grant 2:
1.10 ! gdt 3: # General
1.1 grant 4:
1.10 ! gdt 5: Generally, bootstrapping on GNU/Linux is expected to Just Work with
! 6: gcc.
! 7:
! 8: # Compilers
! 9:
! 10: ## gcc
! 11:
! 12: gcc is the standard approach.
! 13:
! 14: As of 2022 it has been reported that systems with gcc 4.8 (e.g. RHEL7)
! 15: do not bootstrap, but that gcc7 (AWS-flavored RHEL7) and gcc8 (RHEL8) succeed.
! 16:
! 17: ## clang
! 18:
! 19: There are no reports of success or failure with clang.
! 20:
! 21: ## icc
! 22:
! 23: Long ago, it was reported that icc (Intel C++ Compiler) 8.0 and 8.1
! 24: have been tested on i386. See the old section at the end.
! 25:
! 26: # Debian and derivatives
1.4 dmcmahil 27:
1.6 sevan 28: For Debian and derivatives such as Ubuntu the following packages should be
1.10 ! gdt 29: installed prior to attempting bootstrap:
1.6 sevan 30:
1.9 cjep 31: apt-get install cvs libncurses5 libncurses5-dev gcc g++ zlib1g-dev \
32: zlib1g libssl-dev libudev-dev
1.6 sevan 33:
1.10 ! gdt 34: # RedHat and derivatives
! 35:
! 36: ## Old, undated, information
1.6 sevan 37:
1.4 dmcmahil 38: Some versions of Linux (RHEL3 Update 2 for i386 for example) have a
39: /usr/lib/libacl.la libtool archive file that lists /lib/libattr.la as a
40: dependency. However, libattr.la does not exist in /lib/libattr.la. If
41: this is the case, the bootstrap will fail with
42:
43: grep: /lib/libattr.la: No such file or directory
44: /usr/pkgsrc/bootstrap/work/wrk/pkgtools/pkg_install/work/.tools/bin/sed: can't read /lib/libattr.la: No such file or directory
45: libtool: link: `/lib/libattr.la' is not a valid libtool archive
46:
1.5 prlw1 47: The solution is to copy /usr/lib/libattr.la to /lib/libattr.la with:
1.4 dmcmahil 48:
49: cp -p /usr/lib/libattr.la /lib
50:
1.10 ! gdt 51: # General old, undated information
1.4 dmcmahil 52:
1.10 ! gdt 53: ## Details of using icc
1.2 grant 54:
55: To bootstrap using icc, assuming the default icc installation
56: directory:
57:
58: env CC=/opt/intel_cc_80/bin/icc LDFLAGS=-static-libcxa \
59: ac_cv___attribute__=yes ./bootstrap
60:
1.3 grant 61: note: icc 8.1 needs the `-i-static' argument instead of
62: -static-libcxa.
63:
1.2 grant 64: icc supports __attribute__, but the GNU configure test uses a nested
65: function, which icc does not support. #undef'ing __attribute__ has the
66: unfortunate side-effect of breaking many of the Linux header files, which
67: cannot be compiled properly without __attribute__. The test must be
68: overridden so that __attribute__ is assumed supported by the compiler.
69:
70: After bootstrapping, you should set PKGSRC_COMPILER in mk.conf:
71:
72: PKGSRC_COMPILER=icc
73:
74: The default installation directory for icc is /opt/intel_cc_80, which
75: is also the pkgsrc default. If you have installed it into a different
76: directory, set ICCBASE in mk.conf:
77:
78: ICCBASE=/opt/icc
79:
80: pkgsrc uses the static linking method of the runtime libraries
81: provided by icc, so binaries can be run on other systems which do not
82: have the shared libraries installed.
83:
84: Libtool, however, extracts a list of libraries from the ld(1) command
85: run when linking a C++ shared library and records it, throwing away
86: the -Bstatic and -Bdynamic options interspersed between the libraries.
87: This means that libtool-linked C++ shared libraries will have a
88: runtime dependency on the icc libraries until this is fixed in
89: libtool.
CVSweb <webmaster@jp.NetBSD.org>