Re: [lfs-support] PROBLEM IN GCC-4.7.1 PASS 1 COMPILATION
On Wed, Feb 20, 2013 at 6:15 AM, Rubin Saifi rubinsa...@live.com wrote: here is the error that i am getting -- checking for __gmpz_init in -lgmp... yes checking for MPFR... no configure: error: libmpfr not found or uses a different ABI (including static vs shared). make[1]: *** [configure-mpc] Error 1 make[1]: Leaving directory `/lfs/sources/build-gcc' make: *** [all] Error 2 -- i don't know how to get it done i have done all of the steps that are mentioned in the LFS-7.2 guide Book please Provide the solution for it Did you untar gcc-4.7.1 Did you cd gcc-4.7.1 before doing this below? Did you do this section carefully? Including reading the note? 5.5.1. Installation of Cross GCC GCC now requires the GMP, MPFR and MPC packages. As these packages may not be included in your host distribution, they will be built with GCC. Unpack each package into the GCC source directory and rename the resulting directories so the GCC build procedures will automatically use them: Note There are frequent misunderstandings about this chapter. The procedures are the same as every other chapter as explained earlier (Package build instructions). First extract the gcc tarball from the sources directory and then change to the directory created. Only then should you proceed with the instructions below. tar -Jxf ../mpfr-3.1.1.tar.xz mv -v mpfr-3.1.1 mpfr tar -Jxf ../gmp-5.0.5.tar.xz mv -v gmp-5.0.5 gmp tar -zxf ../mpc-1.0.tar.gz mv -v mpc-1.0 mpc -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] PROBLEM IN GCC-4.7.1 PASS 1 COMPILATION
The compile is not finding MPFR as your error log states. There's not enough of the log presented in this email for me to much more than guess at your problem, but I would look at where you extracted the mpfr and gmp tarballs. If this happens to be just a symptom of a more elusive error, there's not enough information to reveal any clues that I can detect. Hoping that it's a simple fix: Be sure that you are in the gcc-4.4.1 source directory for that extraction process before changing to the gcc-build directory for the configure process. I am only guessing, but I would expect your particular error if a) the two steps were somehow reversed, or b) the extraction of mpfr and gmp was done from the /mnt/lfs/sources/ level instead of /mnt/lfs/sources/gcc-4.4.1/... I hope I'm contributing positively to your efforts. I feel that most of the seasoned active responders on this list are a few timezones behind me... perhaps better ideas are on their way. Nicholas McCurdy mindwarpstud...@aim.com -Original Message- From: Rubin Saifi rubinsa...@live.com To: lfs-support lfs-support@linuxfromscratch.org Sent: Wed, Feb 20, 2013 12:15 pm Subject: [lfs-support] PROBLEM IN GCC-4.7.1 PASS 1 COMPILATION here is the error that i am getting -- checking for __gmpz_init in -lgmp... yes checking for MPFR... no configure: error: libmpfr not found or uses a different ABI (including static vs shared). make[1]: *** [configure-mpc] Error 1 make[1]: Leaving directory `/lfs/sources/build-gcc' make: *** [all] Error 2 -- i don't know how to get it done i have done all of the steps that are mentioned in the LFS-7.2 guide Book please Provide the solution for it Thanks -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Problem compiling GCC-4.7.1, Chapter 6.17, LFS 7.2
Hi there! I tried once again to get me a LFS-system. Intel i3, 8GB RAM, SSD 60GB + HD 2TB So 64 bit comes natural. I tried several approaches to compile gcc regarding to chapter 6.17, first with user package management... then as root, too. I fear there might be some problems with the compiled-as-user programs prior to gcc which leaves gcc in a state that it can't be compiled, but I hope it's not the case and I'm just overlooking something. Compiling as root, 'configure' and 'make' both run fine (similar when compiling as user), but after the 'ulimit' command the 'make -k check' gets me errors I also get when compiling gcc as user. A 'make install' afterwards ends into a similar error message with virtually no files installed. Every help and idea is appreciated. Here is the output I get. First just the summaries: === gcc Summary === # of expected passes85590 # of unexpected successes 5 # of expected failures 256 # of unsupported tests 1229 /root/gcc-build/gcc/xgcc version 4.7.1 (GCC) === g++ Summary === # of expected passes48564 # of expected failures 286 # of unsupported tests 541 /root/gcc-build/gcc/testsuite/g++/../../g++ version 4.7.1 (GCC) === libstdc++ Summary === # of expected passes8849 # of expected failures 43 # of unsupported tests 151 === libmudflap Summary === # of expected passes1435 # of unexpected failures1 === libgomp Summary === # of expected passes1247 === libitm Summary === # of expected passes26 # of expected failures 3 # of unsupported tests 1 Now here comes the compile protocol, starting from a position with no errors. As said, this is the 'root' compiling, but I get similar results as non-root, too. === libmudflap Summary === # of expected passes1435 # of unexpected failures1 make[4]: *** [check-DEJAGNU] Error 1 make[4]: Leaving directory `/root/gcc-build/x86_64-unknown-linux-gnu/libmudflap/testsuite' make[3]: *** [check-am] Error 2 make[3]: Target `check' not remade because of errors. make[3]: Leaving directory `/root/gcc-build/x86_64-unknown-linux-gnu/libmudflap/testsuite' make[3]: Entering directory `/root/gcc-build/x86_64-unknown-linux-gnu/libmudflap' true AR_FLAGS=rc CC_FOR_BUILD=gcc CFLAGS=-g -O2 CXXFLAGS=-g -O2 -D_GNU_SOURCE CFLAGS_FOR_BUILD=-g -O2 CFLAGS_FOR_TARGET=-g -O2 INSTALL=/tools/bin/install -c INSTALL_DATA=/tools/bin/install -c -m 644 INSTALL_PROGRAM=/tools/bin/install -c INSTALL_SCRIPT=/tools/bin/install -c JC1FLAGS= LDFLAGS= LIBCFLAGS=-g -O2 LIBCFLAGS_FOR_TARGET=-g -O2 MAKE=make MAKEINFO=makeinfo --split-size=500 --split-size=500 PICFLAG= PICFLAG_FOR_TARGET= SHELL=/bin/sh RUNTESTFLAGS= exec_prefix=/root/fake/usr infodir=/root/fake/usr/share/info libdir=/root/fake/usr/lib prefix=/root/fake/usr includedir=/root/fake/usr/include AR=ar AS=/root/gcc-build/./gcc/as CC=/root/gcc-build/./gcc/xgcc -B/root/gcc-build/./gcc/ -B/root/fake/usr/x86_64-unknown-linux-gnu/bin/ -B/root/fake/usr/x86_64-unknown-linux-gnu/lib/ -isystem /root/fake/usr/x86_64-unknown-linux-gnu/include -isystem /root/fake/usr/x86_64-unknown-linux-gnu/sys-include CXX=/root/gcc-build/./gcc/g++ -B/root/gcc-build/./gcc/ -nostdinc++ -nostdinc++ -I/root/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/root/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include -I/root/gcc-4.7.1/libstdc++-v3/libsupc++ -I/root/gcc-4.7.1/libstdc++-v3/include/backward -I/root/gcc-4.7.1/libstdc++-v3/testsuite/util -L/root/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/src -L/root/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs -B/root/fake/usr/x86_64-unknown-linux-gnu/bin/ -B/root/fake/usr/x86_64-unknown-linux-gnu/lib/ -isystem /root/fake/usr/x86_64-unknown-linux-gnu/include -isystem /root/fake/usr/x86_64-unknown-linux-gnu/sys-include LD=/root/gcc-build/./gcc/collect-ld LIBCFLAGS=-g -O2 NM=/root/gcc-build/./gcc/nm PICFLAG= RANLIB=ranlib DESTDIR= DO=all multi-do # make make[3]: Leaving directory `/root/gcc-build/x86_64-unknown-linux-gnu/libmudflap' make[2]: *** [check-recursive] Error 1 make[2]: Target `check' not remade because of errors. make[2]: Leaving directory `/root/gcc-build/x86_64-unknown-linux-gnu/libmudflap' make[1]: *** [check-target-libmudflap] Error 2 make[2]: Entering directory `/root/gcc-build/x86_64-unknown-linux-gnu/libssp' true AR_FLAGS=rc CC_FOR_BUILD=gcc CFLAGS=-g -O2 CXXFLAGS=-g -O2 -D_GNU_SOURCE CFLAGS_FOR_BUILD=-g -O2 CFLAGS_FOR_TARGET=-g -O2 INSTALL=/tools/bin/install -c INSTALL_DATA=/tools/bin/install -c -m 644 INSTALL_PROGRAM=/tools/bin/install -c INSTALL_SCRIPT=/tools/bin/install -c JC1FLAGS= LDFLAGS= LIBCFLAGS=-g -O2 LIBCFLAGS_FOR_TARGET=-g -O2 MAKE=make
Re: [lfs-support] Problem compiling GCC-4.7.1, Chapter 6.17, LFS 7.2
Ralf Bauerfeind wrote: Hi there! I tried once again to get me a LFS-system. Intel i3, 8GB RAM, SSD 60GB + HD 2TB So 64 bit comes natural. I tried several approaches to compile gcc regarding to chapter 6.17, first with user package management... then as root, too. I fear there might be some problems with the compiled-as-user programs prior to gcc which leaves gcc in a state that it can't be compiled, but I hope it's not the case and I'm just overlooking something. Compiling as root, 'configure' and 'make' both run fine (similar when compiling as user), but after the 'ulimit' command the 'make -k check' gets me errors I also get when compiling gcc as user. That's one error in libmudflap and it's documented in the book. A 'make install' afterwards ends into a similar error message with virtually no files installed. What error? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problem compiling GCC-4.7.1, Chapter 6.17, LFS 7.2
On Thu, Nov 08, 2012 at 09:08:16PM +0100, Ralf Bauerfeind wrote:
I tried several approaches to compile gcc regarding to chapter 6.17,
first with user package management... then as root, too.
I fear there might be some problems with the compiled-as-user programs
prior to gcc which leaves gcc in a state that it can't be compiled, but
I hope it's not the case and I'm just overlooking something.
Possible, but here on -support we only see the problems. So, I
think your other programs should be assumed to be ok until we see
evidence of errors.
Compiling as root, 'configure' and 'make' both run fine (similar when
compiling as user), but after the 'ulimit' command the 'make -k check'
gets me errors I also get when compiling gcc as user.
Errors are to be expected - that is why we use -k.
A 'make install' afterwards ends into a similar error message with
virtually no files installed.
Every help and idea is appreciated.
Here is the output I get. First just the summaries:
I see a failed test ('unexpected failure') in libmudflap for both
versions, the rest of the summaries seem to all be ok, on a quick
look.
I also don't see what error you are getting in the install.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
[lfs-support] problem in gcc-4.5.2 compiliation
Hi. I started compiling LFS 6.8 and i got stuck while compiling the gcc-4.5.2 in pass 1 itself. The error reads as: checking for x86_64-unknown-linux-gnu-gcc... /mnt/lfs/sources/gcc-build/./gcc/xgcc -B/mnt/lfs/sources/gcc-build/./gcc/ -B/tools/x86_64-unknown-linux-gnu/bin/ -B/tools/x86_64-unknown-linux-gnu/lib/ -isystem /tools/x86_64-unknown-linux-gnu/include -isystem /tools/x86_64-unknown-linux-gnu/sys-include checking for suffix of object files... configure: error: in `/mnt/lfs/sources/gcc-build/x86_64-unknown-linux-gnu/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. make[2]: *** [configure-stage1-target-libgcc] Error 1 make[2]: Leaving directory `/mnt/lfs/sources/gcc-build' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/mnt/lfs/sources/gcc-build' make: *** [all] Error 2 I got this error when i executed the make command. my PWD was /mnt/lfs/sources/gcc-build and i was logged in as lfs user i had extracted gcc-4.5.2 in the sources directory and then extracted mpc, mpfr and gmp inside the gcc-4.5.2 extracted directory. Then i created another directory in /mnt/lfs/sources named gcc-build and then i execcuted the configuraion commands for gcc.. Please tell me if im going wrong. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Problem Compiling GCC Ch5 Stage 1
As the title says. Initially reported here: http://www.mail-archive.com/lfs-book@linuxfromscratch.org/msg13114.html then more recently here: http://www.mail-archive.com/lfs-book@linuxfromscratch.org/msg14502.html The solution was found here: http://www.mail-archive.com/lfs-book@linuxfromscratch.org/msg12674.html It's happened again just in the last couple of days, this time on an AMD Athlon-XP 2400+ with a Gentoo LiveCD as the host. The rest of the build has no problems (as usual). So, I've discounted the antique hardware, CFLAGS CXXFLAGS are unset and the host OS and target version of LFS are pretty much out of the picture. I'm lost as to what else could be a factor here. Apart from the initial posting of the solution to use make all-gcc all-target-libgcc instead of make and make install-gcc install-target-libgcc instead of make install, am I the only one who suffers this oddity? Looking for any sensible ideas/suggestions. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Problem on GCC pass 2 (chapter 5.10.1)
Being pretty new to LFS, it's high chance I fucked up somewhere. But up till now everything seemed to work. When i try to apply the patch patch -Np1 -i ../gcc-4.5.1-startfiles_fix-1.patch while being in the gcc-directory, i get the following error: patching file gcc/gcc.c Hunk #1 FAILED at 6370. 1 out of 1 hunk FAILED -- saving rejects to file gcc/gcc.c.rej I did interrupt the LFS-building after adjusting the toolchain, but I picked it up again, reset the variables where needed and had no troubles with binutils pass 2 thanks and sorry if i'm being ignorant, pieter -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problem on GCC pass 2 (chapter 5.10.1)
pieter blomme wrote: Being pretty new to LFS, it's high chance I fucked up somewhere. But up till now everything seemed to work. When i try to apply the patch patch -Np1 -i ../gcc-4.5.1-startfiles_fix-1.patch while being in the gcc-directory, i get the following error: patching file gcc/gcc.c Hunk #1 FAILED at 6370. 1 out of 1 hunk FAILED -- saving rejects to file gcc/gcc.c.rej Check the md5sums of the patch and the package. Delete the extracted directory and re-extract. Make sure you are in the correct directory when patching. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problem on Gcc(Passs 2) compilation!
I start again from the beginning and I get it. Sorry for my wrong. Thanks for attention! 2009/11/17 Karl Cardoso k...@karlbr.com Hi! I get this problem when a run make on the GCC (Pass 2) compilation. I'm reading the book 6.5 Problem: cp/cp-lang.o stub-objc.o cp/call.o cp/decl.o cp/expr.o cp/pt.o cp/typeck2.o cp/class.o cp/decl2.o cp/error.o cp/lex.o cp/parser.o cp/ptree.o cp/rtti.o cp/typeck.o cp/cvt.o cp/except.o cp/friend.o cp/init.o cp/method.o cp/search.o cp/semantics.o cp/tree.o cp/repo.o cp/dump.o cp/optimize.o cp/mangle.o cp/cp-objcp-common.o cp/name-lookup.o cp/cxx-pretty-print.o cp/cp-gimplify.o tree-mudflap.o attribs.o c-common.o c-format.o c-pragma.o c-semantics.o c-lex.o c-dump.o i386-c.o c-pretty-print.o c-opts.o c-pch.o incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o c-gimplify.o c-omp.o tree-inline.o dummy-checksum.o main.o libbackend.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a ../libcpp/libcpp.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/mnt/lfs/sources/gcc-build/./gmp/.libs -L/mnt/lfs/sources/gcc-build/./gmp/_libs -L/mnt/lfs/sources/gcc-build/./mpfr/.libs -L/mnt/lfs/sources/gcc-build/./mpfr/_libs -lmpfr -lgmp /mnt/lfs/tools/bin/../lib/gcc/i686-lfs-linux-gnu/4.4.1/../../../../i686-lfs-linux-gnu/bin/ld: BFD (GNU Binutils) 2.19.1 internal error, aborting at ../../binutils-2.19.1/bfd/merge.c line 873 in _bfd_merged_section_offset /mnt/lfs/tools/bin/../lib/gcc/i686-lfs-linux-gnu/4.4.1/../../../../i686-lfs-linux-gnu/bin/ld: Please report this bug. collect2: ld returned 1 exit status make[2]: *** [cc1plus-dummy] Error 1 make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/gcc' make[1]: *** [all-gcc] Error 2 make[1]: Leaving directory `/mnt/lfs/sources/gcc-build' make: *** [all] Error 2 Thank you! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: problem concerning gcc
On Wed, 2009-01-14 at 01:50 +0800, mobile Parmenides wrote: Hi I am reading stable lfs book of 6.3 version. On page 96, I'm puzzled to the following two commands: ln -sv ../usr/bin/cpp /lib ln -sv gcc /usr/bin/cc For the first command, the current dircetory is /source/gcc-build, and the path in the command does not exsit. For the second command, the intendance is to make /usr/bin/cc point to gcc. But , gcc is in the current directory, and after installing, the current directory is to be deleted. What's the meaning of the link? A little late replying, but where others have said read the man page, I don't personally find it very clear on the subject. The short version is that if you create a symlink with a relative path, that path is interpreted relative to the symlink itself, not to the current directory - hence, the first example should be read as /lib/../usr/bin/cpp, and the second as /usr/bin/gcc The reason is that the value you provide isn't interpreted when the symlink is created - it's interpreted when the symlink is actually referenced. If you try running ls on the links: ~$ ll /lib/cpp /usr/bin/cc lrwxrwxrwx 1 root root 14 2008-06-04 21:05 /lib/cpp - ../usr/bin/cpp lrwxrwxrwx 1 root root 3 2008-06-04 21:05 /usr/bin/cc - gcc See the file sizes - 14 bytes, and 3 bytes. The same number of characters in the '../usr/bin/cpp' and 'gcc' respectively. Not a coincidence. :) Note that as a result, a link pointing from /lib to ../usr/bin/cpp isn't the same thing as a link pointing to /usr/bin/cpp. The latter will always point to the same place, but the former will change if the location of the symlink does - e.g if /lib is mounted as /mnt/lfs/lib at some point. Hope that provides a little illumination... Simon. signature.asc Description: This is a digitally signed message part -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: problem concerning gcc
Scott wrote: Then, RTFM. :-) I meant to respond yesterday when I read the original mail, but forgot. This issue is covered in a FAQ ( http://www.linuxfromscratch.org/faq/#wrong-ln-s-command ) so typically I will only respond with: man ln -- Randy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
problem concerning gcc
Hi I am reading stable lfs book of 6.3 version. On page 96, I'm puzzled to the following two commands: ln -sv ../usr/bin/cpp /lib ln -sv gcc /usr/bin/cc For the first command, the current dircetory is /source/gcc-build, and the path in the command does not exsit. For the second command, the intendance is to make /usr/bin/cc point to gcc. But , gcc is in the current directory, and after installing, the current directory is to be deleted. What's the meaning of the link? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Problem with gcc
Hello, I get an error when configuring gcc for re-installation (LFS 6.1 - section 5.11.1 ). Here is the output : loading cache ./config.cache checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking for a BSD compatible install... /usr/bin/install -c *** This configuration is not supported in the following subdirectories: target-libf2c target-libffi target-boehm-gc target-zlib target-libjava zlib fastjar target-libobjc (Any other directories should still work fine.) /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld: warning: ld-linux.so.2, needed by /tools/lib/libc.so.6, not found (try using -rpath or -rpath-link) /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' /tools/lib/libc.so.6: undefined reference to [EMAIL PROTECTED]' collect2: ld returned 1 exit status *** The command '/tools/bin/gcc -o conftest -g -O2 conftest.c' failed. *** You must set the environment variable CC to a working compiler. Maybe I missed some previous instruction but I can't find which one. Thanks for your help. Julien Demoor -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problem with gcc
[EMAIL PROTECTED] wrote: /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld: warning: ld-linux.so.2, needed by /tools/lib/libc.so.6, not found (try using -rpath or -rpath-link) Something went wrong with your glibc installation. /tools/lib/ld-linux.so.2 should be installed by chapter 5 glibc (section 5.6). The errors that follow are all caused by therefore trying to link to your host system's glibc, I think. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problem with gcc
In /mnt/lfs/tools/ I have a link ld-linux.so.2 redirecting to ld-2.3.4.so (in the same directory). Is that correct ? Matthew Burgess wrote: Something went wrong with your glibc installation. /tools/lib/ld-linux.so.2 should be installed by chapter 5 glibc (section 5.6). The errors that follow are all caused by therefore trying to link to your host system's glibc, I think. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problem with gcc
It actually worked well at first. I just tried again and it's broken now, the error message is similar to the one in my originat post and the same happens whether I call cc or gcc. It would seem so, yes. That suggests that the toolchain adjustment stage didn't work correctly. Did the 'sanity check' (in the big caution box) work correctly? Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problem with gcc
I did some tests and I find the results very strange. Since the error message seemed to mean that gcc searched for ld-linux in /tools/bin (in /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld: warning: ld-linux.so.2, needed by /tools/lib/libc.so.6, not found (try using -rpath or -rpath-link) ) I created a symetric link /tools/lib/ld-linux.so.2 to /tools/bin/ld-linux.so.2 . Then I ran again the test with dummy.c. It was compiled without error message. The strange thing commes when I run readelf. I get : Requesting program interpreter : /lib/ld-linux.so.2 I guess I badly set some variable but I can't find which one. JD Julien Demoor wrote: It actually worked well at first. I just tried again and it's broken now, the error message is similar to the one in my originat post and the same happens whether I call cc or gcc. It would seem so, yes. That suggests that the toolchain adjustment stage didn't work correctly. Did the 'sanity check' (in the big caution box) work correctly? Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
