On 09/06/17 15:51, Pierre Labastie wrote: > On 06/09/2017 19:30, [email protected] wrote: >> I had been working through the 8.1 rc2 build and then 8.1 was released. >> >> I went back and made sure that I had adjusted for any of the corrections that >> were made to the book for the official release. >> >> I am having an issue with Ch 6.09 glibc-2.26, specifically the ../configure >> portion: >> >> CC="gcc -isystem $GCC_INCDIR -isystem /usr/include" \ >> ../configure --prefix=/usr \ >> --disable-werror \ >> --enable-kernel=3.2 \ >> --enable-stack-protector=strong \ >> libc_cv_slibdir=/lib >> unset GCC_INCDIR >> >> produces the following: >> >> ....... >> checking for python3... no >> checking for python... no >> configure: WARNING: >> *** These auxiliary programs are missing or incompatible versions: msgfmt >> python >> *** some features or tests will be disabled. >> *** Check the INSTALL file for required versions. >> checking LD_LIBRARY_PATH variable... ok >> checking for bash... /bin/bash >> checking for perl... /usr/bin/perl >> checking for install-info... /tools/bin/install-info >> checking for bison... bison >> checking version of bison... 3.0.4, ok >> checking for .set assembler directive... no >> checking linker support for protected data symbol... no > I have yes for those two tests. Looks like something is wrong with the > assembler and/or the linker. > You said you had built part of LFS-8.1-rc2 before stepping back for 8.1 > release. Where had you stopped in rc2? Had you built chapter 6 glibc before, > so that this build is in fact a rebuild? > > Pierre > Pierre,
I was able to get to 6.24 in previous builds, but to make sure that I don't have residuals from previous builds, I always restart fresh, from the point of re-partitioning the disk & remaking the file systems; so to directly answer your question, no, it is not a rebuild. It is a clean build. >> checking for broken __attribute__((alias()))... no >> checking whether to put _rtld_local into .sdata section... no >> checking whether to use .ctors/.dtors header and trailer... configure: error: >> missing __attribute__ ((constructor)) support?? >> root:/sources/glibc-2.26/build# >> >> I have not been able to find anything recently posted associated with this >> error through Google. Any suggestions as to where I need to look? >> >> Regards, >> >> Edwin James I have found a dated (2011-08-03) reference to the " checking whether to use .ctors/.dtors header and trailer... configure: error: missing __attribute__ ((constructor)) support??" error. https://www.mail-archive.com/[email protected]&q=subject:%22Re%3A+missing+__attribute__+((constructor))+support%3F%22&o=newest&f=1 <https://www.mail-archive.com/[email protected]&q=subject:%22Re%3A+missing+__attribute__+%28%28constructor%29%29+support%3F%22&o=newest&f=1> The suggestion was to try appending 'libc_cv_ctors_header=yes' to the configure instructions. I tried it to see what it would do, and yes, it did allow me to finish the configuration. However, the ensuing build failed later, so I really don't think that that is the proper fix.... Regards, Edwin James
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
