post yourn0rbi666 wrote:Recompiled binutils and gcc with multislot flag - didn't help, still I have the same error
Code: Select all
gcc-config -lpost yourn0rbi666 wrote:Recompiled binutils and gcc with multislot flag - didn't help, still I have the same error
Code: Select all
gcc-config -lCode: Select all
n0rbi ~ # gcc-config -l
[1] i686-pc-linux-gnu-3.4.5
[2] i686-pc-linux-gnu-3.4.5-hardened
[3] i686-pc-linux-gnu-3.4.5-hardenednopie
[4] i686-pc-linux-gnu-3.4.5-hardenednopiessp
[5] i686-pc-linux-gnu-3.4.5-hardenednossp
[6] i686-pc-linux-gnu-4.1.0 *I got this, but I if I want to using glibc-2.4, seems these patches were not included in the portage, does this means, I must use the glibc-2.4 overlay?nxsty wrote:You can either use my overlay or 2.3.6-r3 in portage, but then you have to modify the ebuild to not exclude the patches.SteveYin wrote:May I ask a stupid question?
If I want the the ld optimization flags, (like -Bdirect) and using binutils in the overlay, then the glibc overlay is a must have or should have?
Sorry for my poor english.
I mean do I must using the glibc in overlay in order to use the binutils in overlay?
Code: Select all
case ${CATEGORY}/${PN} in
"category/package-name")
export LDFLAGS="<Your Flags for This Package Only>"
;;
esacThank you very much! And this will override the global ldflags from make.conf?nesl247 wrote:Code: Select all
case ${CATEGORY}/${PN} in "category/package-name") export LDFLAGS="<Your Flags for This Package Only>" ;; esac
Yes that will overwrite the global ldflags. If you want, you can even do cflags, cxxflags.. Anything that can be passed to portage via the command line. And yes gento uses some ldflags by default (unless I am mistaken). Some are --enable-new-dtags, and -z now (I think). Not positive on the ldflags, but pretty sure.piwacet wrote:Thank you very much! And this will override the global ldflags from make.conf?nesl247 wrote:Code: Select all
case ${CATEGORY}/${PN} in "category/package-name") export LDFLAGS="<Your Flags for This Package Only>" ;; esac
Curious, does Gentoo use any ldflags as default? Or do individual programs specify any ldflags themselves?
Code: Select all
-z keyword
The recognized keywords are:
...
dynsort
Sorts dynamic link sections, to reduce cache misses during linking.
Code: Select all
/bin/sh ../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -O2 -march=nocona -fomit-frame-pointer -pipe -fno-ident -Wl,-O1 -Wl,-z,now -o usermod usermod.o ../libmisc/libmisc.a ../lib/libshadow.la -lpam -lpam_miscCode: Select all
x86_64-pc-linux-gnu-gcc -O2 -march=nocona -fomit-frame-pointer -pipe -fno-ident -Wl,-O1 -Wl,-z -Wl,now -o useradd useradd.o ../libmisc/libmisc.a ../lib/.libs/libshadow.a -lcrypt -lpam -lpam_miscCode: Select all
Calculating dependencies... done!
Traceback (most recent call last):
File "/usr/bin/emerge", line 3263, in ?
if "resume" in portage.mtimedb and \Code: Select all
checking for ld --version-script... no
*** WARNING: You should not compile GNU libc without versioning. Not using
*** versioning will introduce incompatibilities so that old binaries
*** will not run anymore.
*** For versioning you need recent binutils (binutils-2.8.1.0.23 or newer).
checking for .previous assembler directive... yes
checking for .protected and .hidden assembler directive... yes
checking whether __attribute__((visibility())) is supported... yes
checking for broken __attribute__((visibility()))... no
checking for broken __attribute__((alias()))... no
checking whether to put _rtld_local into .sdata section... no
checking for .preinit_array/.init_array/.fini_array support... no
configure: error: Need linker with .init_array/.fini_array support.
!!! ERROR: sys-libs/glibc-2.4 failed.
Call stack:
ebuild.sh, line 1557: Called dyn_compile
ebuild.sh, line 966: Called src_compile
glibc-2.4.ebuild, line 1300: Called toolchain-glibc_src_compile
glibc-2.4.ebuild, line 290: Called glibc_do_configure 'nptl'Code: Select all
sys-devel/binutils-2.16.91.0.6Code: Select all
n0rbi ~ # binutils-config -l
[1] i686-pc-linux-gnu-2.16.91.0.6 *
I remember having the same problem with the same version of binutils before reinstalltion becouse of other problems (was then using glibc2.4, biuntils-2.16.91.0.6, gcc-4.1). However have never the problem occured for me using latest ~x86 binutils in portage, gcc-3.4.x and glibc-2.4 (both portage and nxstys)...n0rbi666 wrote:I'm usingCode: Select all
sys-devel/binutils-2.16.91.0.6What overlay do you use for gcc ?Code: Select all
n0rbi ~ # binutils-config -l [1] i686-pc-linux-gnu-2.16.91.0.6 *
What packages are in toolkit ?