LFS-3.3 bash-2.05a installation problem...
Hai, I tried to install bash-2.05a as suggested by the book. While ./configure ... it was fine. But while 'make' it gave the following error(at end of the mail). I am using fedoracore 3, glibc-2.3.3, gcc-3.4.2 I am following LFS-3.3 I am not a subscribed member of this mailing list. Thank you. vignesh /usr/lib/gcc/i386-redhat-linux/3.4.2/../../../libc.a(malloc.o)(.text+0x1380): In function `free': : multiple definition of `free' ./lib/malloc/libmalloc.a(malloc.o)(.text+0xa7c):/mnt/kernel/usr/src/bash-2.05a/lib/malloc/malloc.c:1072: first defined here /usr/bin/ld: Warning: size of symbol `free' changed from 22 in ./lib/malloc/libmalloc.a(malloc.o) to 175 in /usr/lib/gcc/i386-redhat-linux/3.4.2/../../../libc.a(malloc.o) /usr/lib/gcc/i386-redhat-linux/3.4.2/../../../libc.a(malloc.o)(.text+0x2c70): In function `malloc': : multiple definition of `malloc' ./lib/malloc/libmalloc.a(malloc.o)(.text+0xa48):/mnt/kernel/usr/src/bash-2.05a/lib/malloc/malloc.c:1057: first defined here /usr/bin/ld: Warning: size of symbol `malloc' changed from 22 in ./lib/malloc/libmalloc.a(malloc.o) to 373 in /usr/lib/gcc/i386-redhat-linux/3.4.2/../../../libc.a(malloc.o) /usr/lib/gcc/i386-redhat-linux/3.4.2/../../../libc.a(malloc.o)(.text+0x30a0): In function `realloc': : multiple definition of `realloc' ./lib/malloc/libmalloc.a(malloc.o)(.text+0xa60):/mnt/kernel/usr/src/bash-2.05a/lib/malloc/malloc.c:1065: first defined here /usr/bin/ld: Warning: size of symbol `realloc' changed from 25 in ./lib/malloc/libmalloc.a(malloc.o) to 531 in /usr/lib/gcc/i386-redhat-linux/3.4.2/../../../libc.a(malloc.o) collect2: ld returned 1 exit status make: *** [bash] Error 1 ___ Too much spam in your inbox? Yahoo! Mail gives you the best spam protection for FREE! http://in.mail.yahoo.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Problems during compilation of binutils ...
Hello, I've a problem during compilation of pass 2 of the binutils. Up to this point I followed the instructions of the lfs-book (6.0) page by page and everything worked fine. But now, the compilation process stops with following message: [...] file=../../../binutils-2.15.91.0.2/bfd/po/`echo fr | sed 's,.*/,,'`.gmo \ rm -f $file PATH=../src:$PATH no -o $file ../../../binutils-2.15.91.0.2/bfd/po/fr.po /bin/sh: line 1: no: command not found make[3]: *** [fr.gmo] Error 127 make[3]: Leaving directory [...] What kind of command is no? What went wrong? Can somebody give me a hint? Thanks, Reimar -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problems during compilation of binutils ...
R.Grasbon wrote: rm -f $file PATH=../src:$PATH no -o $file Looks to me to be a typo here -- Shane Shields Registered LFS Compiler: 7582 To drink the WINE of success you must first seek the sayings of source Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problems during compilation of binutils ...
Shane Shields schrieb: R.Grasbon wrote: rm -f $file PATH=../src:$PATH no -o $file Looks to me to be a typo here I think not, but I'm not 100% sure because I transfered the error-message by hand. But the principal problem remains in force. Reimar -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problems during compilation of binutils ...
R.Grasbon wrote: Shane Shields schrieb: R.Grasbon wrote: rm -f $file PATH=../src:$PATH no -o $file Looks to me to be a typo here I think not, but I'm not 100% sure because I transfered the error-message by hand. But the principal problem remains in force. Reimar What I meant by typo is there is no program by the name of no that I know of. Which leads me to believe that somewhere in your toolchain compile you made a typo. Are you cut'n'pasting or typing out by hand? If cut'n'pasting maybe you selected less or more than you thought. If typing then you may have missed a character or two in a sed or something. Did you keep logs of what you did so you can review them? Are you sure that you did not miss any steps that may have slid past your eyes? Maybe the toolchain adjustments? It is easy to do (been there done that many times). Did you do the sanity check? -- Shane Shields Registered LFS Compiler: 7582 To drink the WINE of success you must first seek the sayings of source Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problems during compilation of binutils ...
On 7/4/05, Shane Shields [EMAIL PROTECTED] wrote: R.Grasbon wrote: rm -f $file PATH=../src:$PATH no -o $file Looks to me to be a typo here The configure script for binutils has replaced a missing gettext command with the value no. Either your host has an incomplete gettext installation, or it's broken. You can either install gettext on your host distribution, or use --disable-nls on the configure command line for binutils if you don't need language support. -- - Steve Crosby -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problems during compilation of binutils ...
Shane Shields schrieb: R.Grasbon wrote: What I meant by typo is there is no program by the name of no that I know of. Which leads me to believe that somewhere in your toolchain compile you made a typo. Are you cut'n'pasting or typing out by hand? If cut'n'pasting maybe you selected less or more than you thought. If typing then you may have missed a character or two in a sed or something. Did you keep logs of what you did so you can review them? Are you sure that you did not miss any steps that may have slid past your eyes? Maybe the toolchain adjustments? It is easy to do (been there done that many times). Did you do the sanity check? Ok, I didn't stare on the screen all the time while compiling. So I re-compiled the glibc to see, if there was the problem but thst didn't change anything. Reimar I am afraid that all I can suggest is to start again and be very careful about your commands. One thing you didn't state is your host distro's details as that may help other heads better than mine. Yes. I'm sorry about that and will be given this information tomorrow. At the moment I can say, that my host system ist a debian sarge with kernel 2.6. Reimar -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Problem fresh LFS + Intel Pro/1000 MT Dual Port
Hello out there, I searched the internet the last two days to get my Intel Pro/1000 MT Dual Port Server Adapter running. I created my LFS with SVN Version 20050630 and had no major problems with building it. I now compiled a nice fresh 2.6.12.2 Kernel with hotplug and module support which runs fine, also with the ck3s-patch. Because the network card is not support by the kernel itself I downloaded the driver at Intel's. Compiling into the Kernel ist not possible you have to compile a module. The problem now is that I do not get eth0 (rather eth1 for the second port)! I added the module e1000 to /etc/sysconfig/modules and it is loaded at boot time (can be proofed by lsmod, e1000 is the only module in my system as I prefer compiling things into kernel). But still when the system boots: Bringing up the eth0 interface... Interface eth0 doesn't exist. [WARN] Also I have to say that in Chapter 7.12 I already defined an ip-address for eth0. Btw: Quoting from the system exactly is a bit complicated because of the missing network ability. But cat /proc/pci shows 2 pci devices (I think one for each port of the dual port card) so the card really exists. So how to get eth0 (and eth1) to work?? Thanks for any help! Best regards, - Ricky Blankenaufulland -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Problems during compilation of binutils ...
On Mon, 4 Jul 2005, R.Grasbon wrote: Yes. I'm sorry about that and will be given this information tomorrow. At the moment I can say, that my host system ist a debian sarge with kernel 2.6. Knowing debian's tendency to keep using (and patching) old versions of software, maybe it's version of gettext is too old (or identified as too old by the configure scripts). What does 'xgettext --version' show ? Personally, I think you should be ok with --disable-nls until you've installed a gettext in /tools. All you tell a package with --disable-nls (_if_ it obeys that flag, which should be true for /tools) is to not install the message catalogues. For a temporary system, that really doesn't matter. By the time you get to chroot you want everything in place to install documentation in the new system, which is why we install gettext and texinfo during chapter 5. Ken -- 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
Re: Problem fresh LFS + Intel Pro/1000 MT Dual Port
Recently, Somebody Somewhere wrote these words Hello out there, I searched the internet the last two days to get my Intel Pro/1000 MT Dual Port Server Adapter running. I created my LFS with SVN Version 20050630 and had no major problems with building it. I now compiled a nice fresh 2.6.12.2 Kernel with hotplug and module support which runs fine, also with the ck3s-patch. Because the network card is not support by the kernel itself I downloaded the driver at Intel's. Compiling into the Kernel ist not possible you have to compile a module. The problem now is that I do not get eth0 (rather eth1 for the second port)! I added the module e1000 to /etc/sysconfig/modules and it is loaded at boot time (can be proofed by lsmod, e1000 is the only module in my system as I prefer compiling things into kernel). But still when the system boots: Bringing up the eth0 interface... Interface eth0 doesn't exist. [WARN] Also I have to say that in Chapter 7.12 I already defined an ip-address for eth0. Btw: Quoting from the system exactly is a bit complicated because of the missing network ability. But cat /proc/pci shows 2 pci devices (I think one for each port of the dual port card) so the card really exists. So how to get eth0 (and eth1) to work?? Thanks for any help! I would compile a kernel with all the nic drivers as modules, and play around in a console as root. You can then bring up down interfaces, stick drivers in out. If hotplug starts outpacing you , stop it temporarily. Google for references on dual port cards. Have you ethernet bridging enabled in the kernel (says he, not knowing too much about this). BTW, have you read Documentation/networking/e1000.txt in the kernel source? -- With best Regards, Declan Moriarty. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
dynamically linked binutils and GCC in LFS 6.1
I have question... Why, in new version LFS, are We dynamically linking bintuitls and GCC in Chapter 5, Pass 1??? In LFS 6.0 it was statically linked. Thanx a lot -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: dynamically linked binutils and GCC in LFS 6.1
Kapier wrote: I have question... Why, in new version LFS, are We dynamically linking bintuitls and GCC in Chapter 5, Pass 1??? In LFS 6.0 it was statically linked. Thanx a lot From the Changelog... April 16, 2005 [matt]: Removed references to statically linking the pass 1 toolchain which should have gone as part of bug 1061 (Andrew Benton) March 13, 2005 [matt]: Dynamically link the pass1 toolchain to workaround bug 1061 and remove all related explanatory text Check out the details here - http://bugs.linuxfromscratch.org/show_bug.cgi?id=1061 -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Can't build/compile Xorg-6.8.2. Need help please
rblythe wrote: Thanks in advance for the help. I am really not sure about this part of the build. I couldn't find a specific BLFS Mailing list so I hope this is the right place for this post. If not, could someone please tell me (gently) where blfs support mailing list is. blfs-support@linuxfromscratch.org http://www.linuxfromscratch.org/mail.html -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Problems building libglademm or libgnomecanvasmm (undefined reference in libgtkmm-2.4)
Hi People, thanks to all again. uprading my pkg-config v0.17 to v0.18 solved the problem. ciao ulf -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: glibc and the dreaded: no libm-err-tab.pl $pwd/.. libm-err-tmp
On Mon, 4 Jul 2005, Ahmed El-Daly wrote: I swear by all things holy that perl is in the PATH. After chrooting, if I type perl -v from anywhere in the file structure, I get: This is perl, v5.8.5 built for x86_64-linux [...] Still in config.make I have this line: PERL = no What does perl -V show (capital V) ? It ought to show _rather_more_ than just Larry's version and copyright stuff, particularly the contents of @INC which is often where the problems occur. And out of interest, is this a multilib build, or just 64-bit stuff in /lib ? Ken -- 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
BASH: no [enter] key
Hello, I've just finished LFS CVS (2005.06.30), and ecstatically booted into my new shiny system. Everything seems to be fine so far - apart from the fact that one I supply my account name (root) and password, I... cannot press Enter. Same happens if I boot into my home system and then chroot into LFS. I use a Polish keyboard and keymap pl compiled into LFS kernel; I also used to have KEYMAP=pl in /etc/sysconfig/console - but even after I commented this one out, I still don't get to have [Enter] recognised... What could have I done wrong? Best regards, David Ciecierski -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: sed problem (Ch.6, LFS Dev 2005.06.30)
I'm now encountering strange responses from sed prior to compiling GCC in Chapter 6. I'm supposed to run sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in ..but I get the following: sed: -e expression #1, char 32: unknown option to `s' In case anyone using user package management system is having the same problem: you simply run this as user root and the problem disappears... Regards, David Ciecierski -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: glibc and the dreaded: no libm-err-tab.pl $pwd/.. libm-err-tmp
On 7/4/05, Ken Moffat [EMAIL PROTECTED] wrote: On Mon, 4 Jul 2005, Ahmed El-Daly wrote: I swear by all things holy that perl is in the PATH. After chrooting, if I type perl -v from anywhere in the file structure, I get: This is perl, v5.8.5 built for x86_64-linux [...] Still in config.make I have this line: PERL = no What does perl -V show (capital V) ? It ought to show _rather_more_ than just Larry's version and copyright stuff, particularly the contents of @INC which is often where the problems occur. And out of interest, is this a multilib build, or just 64-bit stuff in /lib ? Ken -- das eine Mal als Tragödie, das andere Mal als Farce perl -V showed @INC pointing to all sorts of lib64 directories in all different places. You are correct (how the heck did you know :0) ?) I am building a pure-64 system and doing away with the lib64 thing. I figure if I ever do need 32-bit programs, I will make a 32-bit toolchain and put it in /lib32. So now that I know what the problem is, I tried recompiling perl, and for some reason I am gettting this: cc -L/usr/local/lib -o miniperl \ miniperlmain.o opmini.o libperl.a libperl.a(pp.o)(.text+0x2803): In function `Perl_pp_pow': : undefined reference to `pow' libperl.a(pp.o)(.text+0x357d): In function `Perl_pp_modulo': : undefined reference to `floor' [... some more undefined references to math functions...] collect2: ld returned 1 exit status make: *** [miniperl] Error 1 I know that there is a patch out there (from Chris Lingard) that would fix this, but this was made to change perl from looking for /lib to /lib64, I have everything in /lib anyways. Oh well, more digging. Just can't figure out why it worked before (unless I went ahead and wrote over a change I made earlier :( ! ) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
