Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've been using Linux for a few years now, having gone through all the major distributions (openSuSE, Red Hat, Fedora, and now mostly Ubuntu), and now I'm jumping into LFS to learn a little bit more.
I've run into a funny error, though, when trying to compile glibc 2.8.x or 2.9.x(Latest). The config runs flawlessly, but when I run the make command I get this error well into the compile:
../misc/syslog.c: In function ‘__vsyslog_chk’:
../misc/syslog.c:123: sorry, unimplemented: inlining failed in call to ‘syslog’: function body not available
../misc/syslog.c:155: sorry, unimplemented: called from here
make: *** [/mnt/adm/sources/glibc-build/misc/syslog.o] Error 1
make: Leaving directory `/mnt/adm/sources/glibc-src/misc'
make: *** [misc/subdir_lib] Error 2
make: Leaving directory `/mnt/adm/sources/glibc-src'
make: *** [all] Error 2
So `_vsyslog_chk' isn't implemented? Is it a deprecated function?
I'm running Ubuntu Intrepid Ibex 8.10 with all the updates, an Intel Dual-Core 6300 @ 1.86 GHz, 1.8 GB ram.
Aha! So I've finally gotten GCC compiled right. I restarted with a Xubuntu host and used all the updated files (even GCC 2.9). I think my problem might have been with the sed command before the configure -- I wasn't running it when cd'd into the GCC source folder. No wonder the command always returned a "file not found" error. Heh.
The build was flawless, and tested without any errors. Cool!
Same problem but dont understand the workaround(solution)
So diangming you say that the probelm is the gcc that comes by default with the ubuntu distribution and I have to compile or reinstall a better version of it or is it the gcc compiled before? Thats because I'm not using the gcc compiled before to compile glibc as a tool program and get the same compilation problem. Hmmm very strange. because in lfs when compiling the tools it says you dont need any sed command to run before compileing gcc and anyway lfs book says to compile glibc agains ubuntus default gcc not against the gcc you compiled b4. Very strange pls tell me if you know where the problem is
OK guys i have found what the problem was. First of all b4 compiling be sure that CC is set right and make a echo $CC it should be
gcc -B/usr/bin if not run CC="gcc -B/usr/bin" but that wasnt enough in my case i still got the error then i began to read the INSTALL in the source folder and there it says that you should try to avoid as much as posible to compile it as root. And it worked when i tryed to compile it as lfs not as root.
PS: I have also set the profile for root as that for fls as it was explained but that wasnt enough. So profile wasnt the probleme here and settings also not. Very strange but now it works fine as lfs user.
So I advise you to be somthing else as root at least on ubuntu when you compile glibc.
Need to add -U_FORTIFY_SOURCE to the gcc invocation. I found this in Ubuntu's Debian packaging for glibc. I believe this is an Ubuntuism. Ubuntu enables -D_FORTIFY_SOURCE=2 by default.
See Ubuntu's CompilerFlags wiki page.
glibc bug 10375 reports this issue, but it has not been addressed.