cross sparc64 chapter 5 glibc tls required error
cross sparc64 chapter 5 glibc tls error Following the Version 7.0-cross-lfs-20050928-Sparc64 book I stumble on the following error while building glibc: From configure: (...nothing suspicious before...) checking for long double... no checking size of long double... 0 running configure fragment for sysdeps/sparc/sparc64/elf checking for sparc64 TLS support... no checking for sparc64 ld WDISP22 handling... ok running configure fragment for libidn/sysdeps/unix running configure fragment for nptl/sysdeps/unix/sysv/linux running configure fragment for nptl/sysdeps/pthread checking for forced unwind support... (cached) yes checking for C cleanup handling... (cached) yes running configure fragment for sysdeps/pthread (...nothing suspicious here neither...) Then make aborts with In file included from include/tls.h:6, from stdin:1: nptl/sysdeps/sparc/tls.h:59:3: error: #error TLS support is required. make[1]: *** [/mnt/LFS-6/build/glibc-build/Versions.v.i] Error 1 make[1]: Leaving directory `/mnt/LFS-6/build/glibc-20050926' make: *** [all] Error 2 The reason seems to be that the crt1.o file is not found by the linker while running the test fragment. I can work around this by forcing tls support in the config.cache file: libc_cv_sparc64_tls=yes Then configure goes like this: (...) running configure fragment for sysdeps/sparc/sparc64/elf checking for sparc64 TLS support... (cached) yes checking for sparc64 ld WDISP22 handling... ok (...) And then the build completes without error. Is this the way to go ? Frans ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Current udev/hotplug setup is broken
Hello, while testing the utf8-newmake CD, I found that it (unlike utf8-r0 CD) won't load usb-storage and sd-mod modules if I plug in my USB MP3 player. The reason is that udev no longer runs programs in /etc/hotplug.d (in particular, usb.agent and scsi.agent). This has also been noticed twice in BLFS: once due to ALSA volume restoration, and the second time due to HAL/D-BUS thingy. Please build the compatibility helper, run_directory: make EXTRAS=extras/run_directory/ and add the following rule: RUN+=/sbin/udev_run_hotplugd I know this is a legacy setup, but the proper pure-udev setup that breaks nothing in BLFS requires linux-2.6.14, patched libusb and mandatory initramfs (and thus cpio-2.6 in LFS) which is IMHO too early to implement. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Cross-LFS questions
Two questions: (i) Is there still a public rendering of this book ? I went to the website to check if I'd borked something in my editing but couldn't find any mention of Cross-LFS. Perhaps it's part of the restructuring. (/me suppresses a thought that editors on non-projects have a tendency to become non-persons :) (ii) For anybody who has built a pure64 system without chrooting using the if you are going to boot route, should we _really_ be installing e2fsprogs into /tools/lib64 ? This sounds broken, but maybe I'm overlooking something. Ken -- das eine Mal als Trag?die, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Undeliverable Mail
No message body: [EMAIL PROTECTED] Original message follows. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Current udev/hotplug setup is broken
Tushar Teredesai wrote: On 9/30/05, Alexander E. Patrakov [EMAIL PROTECTED] wrote: I know this is a legacy setup, but the proper pure-udev setup that breaks nothing in BLFS requires linux-2.6.14, patched libusb and mandatory initramfs (and thus cpio-2.6 in LFS) which is IMHO too early to implement. How about a hint then? Later. One hint is alerady pending (printing from windows to CUPS). -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Current udev/hotplug setup is broken
Alexander E. Patrakov wrote: Hello, while testing the utf8-newmake CD, I found that it (unlike utf8-r0 CD) won't load usb-storage and sd-mod modules if I plug in my USB MP3 player. The reason is that udev no longer runs programs in /etc/hotplug.d (in particular, usb.agent and scsi.agent). This has also been noticed twice in BLFS: once due to ALSA volume restoration, and the second time due to HAL/D-BUS thingy. Please build the compatibility helper, run_directory: make EXTRAS=extras/run_directory/ and add the following rule: RUN+=/sbin/udev_run_hotplugd Spoke too soon. Corrected instructions: make EXTRAS=extras/run_directory/ make EXTRAS=extras/run_directory/ install # Udev-070 Makefile has a bug here: wrong program is instaled install -m755 extras/run_directory/udev_run_hotplugd /sbin cp ../udev-config-3.rules /etc/udev/rules.d/25-lfs.rules echo 'RUN+=/sbin/udev_run_hotplugd' /etc/udev/rules.d/25-lfs.rules echo 'RUN+=/sbin/udev_run_devd' /etc/udev/rules.d/25-lfs.rules install -m644 -D docs/writing_udev_rules/index.html \ /usr/share/doc/udev-070/index.html Confirmed working on the utf8-newmake CD. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: cross sparc64 chapter 5 glibc tls required error
Use the 20050930 version of the book, it has all the necessary fixes in it. -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Cross LFS Status
I haven't done one of these in a few weeks, been tied up at work. I would like to thank Matt Darcy, Joe Ciccone, Manuel Canales, and Ken Moffat for their fine addtitions to the book over the past few weeks. I really appreciate it. We are currently trying to stablize the Cross-LFS book. Here are the current status of issues. All Architectures now - NPTL GCC 4.0.2 added Using Glibc Snapshot - Needed for NPTL support and GCC 4.x.x fixes MIPS64 is Pure 64 capable and is working Alpha fully working x86 fully working MIPS fully working MIPS64 fully working Outstanding Issues PPC Yaboot Pure64 Builds Bootloaders, what to do, suggestions welcomed, Biggest concerns Silo and Grub lack of ability to be compiled as 64 Bit. -- Programmers welcome!! MIPS/MIPS64 Adding arcboot to the book for other MIPS based machines Book Update the earilier chapters of the book to reflect cross-compiling Add all missing configuration lines -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Current udev/hotplug setup is broken
Alexander E. Patrakov wrote: Tushar Teredesai wrote: How about a hint then? Later. Please don't worry about this, Alexander. I'm working on a hint (though not in formal LFS-hint format) now, and hope to have something done by end of play tonight. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Cross LFS Status
On Fri, 30 Sep 2005, Jim Gifford wrote: We are currently trying to stablize the Cross-LFS book. Any thoughts on a package freeze for existing packages, particularly glibc ? (That is, freeze versions unless it becomes clear that a different version will solve problems). I'm preparing to start some fresh builds (x86, x86_64-64, x86_64 on the same machine), hopefully tomorrow, but if we upgrade glibc each week my test results will be worthless by the time I have them ;) Outstanding Issues PPC Yaboot The only issue I've noticed is the errors in the list of files to install into /boot (/me admits to still not getting around to correcting this). Anything else ? Pure64 Builds Bootloaders, what to do, suggestions welcomed, Biggest concerns Silo and Grub lack of ability to be compiled as 64 Bit. -- Programmers welcome!! For x86_64-64 lilo compiles and works now, or at least it did last time I checked. Book Update the earilier chapters of the book to reflect cross-compiling Add all missing configuration lines Any thoughts on what to do about space/time measurements ? I'm not a big fan of SBUs, but (at least on non-cross) they have some element of repeatability if people don't get too finicky with how precisely they measure them. I think Manuel had a suggestion about what to use as an approximate SBU when building the final system if this was a true cross-build. Maybe we could have SBUs for the first part, and NBUs (native build units) for the temp tools and final system. I'm fairly sure that the space used in the first part of the build will depend on both the host and the target (e.g. ppc32 instructions are all 32 bits, and building glibc back in the days of LFS-5.0 took a lot more space on ppc than on x86). Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Cross LFS Status
Ken Moffat wrote: On Fri, 30 Sep 2005, Jim Gifford wrote: Any thoughts on a package freeze for existing packages, particularly glibc ? (That is, freeze versions unless it becomes clear that a different version will solve problems). I'm preparing to start some fresh builds (x86, x86_64-64, x86_64 on the same machine), hopefully tomorrow, but if we upgrade glibc each week my test results will be worthless by the time I have them ;) As far as I'm concerned 20050926 is the last version we will use, it's stable on all platforms. Pure64 Builds Bootloaders, what to do, suggestions welcomed, Biggest concerns Silo and Grub lack of ability to be compiled as 64 Bit. -- Programmers welcome!! For x86_64-64 lilo compiles and works now, or at least it did last time I checked. That's a possibility but it means adding some packages back. Right now we have people looking at solving both issues by gettting Grub 2 working. Book Update the earilier chapters of the book to reflect cross-compiling Add all missing configuration lines Any thoughts on what to do about space/time measurements ? I'm not a big fan of SBUs, but (at least on non-cross) they have some element of repeatability if people don't get too finicky with how precisely they measure them. I think Manuel had a suggestion about what to use as an approximate SBU when building the final system if this was a true cross-build. Maybe we could have SBUs for the first part, and NBUs (native build units) for the temp tools and final system. I'm fairly sure that the space used in the first part of the build will depend on both the host and the target (e.g. ppc32 instructions are all 32 bits, and building glibc back in the days of LFS-5.0 took a lot more space on ppc than on x86). SBU's will not be valid in this book, since every platform will be different, I don't think we have the time to recalculate everytime a package changes. Honestly most people don't even look at them as evident from some of the discussions on lfs-support on irc. -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
