cross sparc64 chapter 5 glibc tls required error with 20050930 version of book

2005-10-01 Thread Frans Verstegen
I'm afraid I'm overlooking something obvious, I still get the same error following the "Version 7.0-cross-lfs-20050930-Sparc64" book. >From configure: (...nothing suspicious before...) checking for long double... no checking size of long double... 0 running configure fragment for sysdeps/s

Re: cross sparc64 chapter 5 glibc tls required error with 20050930 version of book

2005-10-01 Thread Bryan Kadzban
I'll preface this with a comment that I know very little about the cross-lfs book, or cross building in general. However: Frans Verstegen wrote: > Then make aborts with > In file included from include/tls.h:6, >from :1: > nptl/sysdeps/sparc/tls.h:59:3: error: #error "TLS s

Re: cross sparc64 chapter 5 glibc tls required error with 20050930 version of book

2005-10-01 Thread Jim Gifford
Looks like you forgot the Sparc TLS patch for glibc. -- -- [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 sparc64 chapter 5 glibc tls required error

2005-10-01 Thread Frans Verstegen
"Jim Gifford" <[EMAIL PROTECTED]> a écrit dans le message de news: > Looks like you forgot the Sparc TLS patch for glibc. Pretty sure not (though never sure), below the script I'm using with it's output: $ more *11.sh export PATH=/cross-tools/bin:/bin:/usr/bin export LC_ALL=POSIX unset CFLAGS uns

Re: cross sparc64 chapter 5 glibc tls required error with 20050930 version of book

2005-10-01 Thread Frans Verstegen
"Jim Gifford" <[EMAIL PROTECTED]> a écrit dans le message de news: > Looks like you forgot the Sparc TLS patch for glibc. Pretty sure not (though never sure), below the script I'm using with it's output: $ more *11.sh export PATH=/cross-tools/bin:/bin:/usr/bin export LC_ALL=POSIX unset CFLAGS uns

Re: cross sparc64 chapter 5 glibc tls required error with 20050930 version of book

2005-10-01 Thread Jim Gifford
Hmm, This is wierd, in you have patched your binutils and glibc for tls sparc you shouldn't be having this issue. What is your host distro? -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev F

Cross LFS

2005-10-01 Thread Jim Gifford
Manuel and LFS-dev, I have been thinking about this for a few days. Cross-LFS has two different options in it, boot and chroot. Boot is a complete reboot and chroot is like the standard LFS book. Talking with various people, an idea popped into my mind. Having two separate books, Cross-LFS

Re: Cross-LFS for MIPS64

2005-10-01 Thread Jim Gifford
Pete, Are you doing a multilib or a Pure 64 build. I'm finishing testing on a RaQ2 Pure 64 updating the book as I go. -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfr

Re: Cross LFS

2005-10-01 Thread Ken Moffat
On Sat, 1 Oct 2005, Jim Gifford wrote: Manuel and LFS-dev, I have been thinking about this for a few days. Cross-LFS has two different options in it, boot and chroot. Boot is a complete reboot and chroot is like the standard LFS book. Talking with various people, an idea popped into my min

Re: [OT] Re: Commit 6803 contains invalid char on commit log

2005-10-01 Thread Anderson Lizardo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander E. Patrakov wrote: > Anderson Lizardo wrote: >> FIY, the Subversion commit messages need always to be written either >> in Unicode or plain ASCII, so "svn log --xml" can output valid XML >> data. So please, setup your favorite editor to one o

[ANNOUNCE] LFS LiveCD x86-6.1-3 Released

2005-10-01 Thread Justin R. Knierim
Hello everyone! The LFS LiveCD Team is proud to announce the release of the version 6.1-3 of the LFS LiveCD. This version includes bug fixes for the 2 most common reported problems with the previous version. The list of fixes includes: * SCSI CDROM's are now correctly detected while bo

Re: [OT] Re: Commit 6803 contains invalid char on commit log

2005-10-01 Thread Alexander E. Patrakov
Anderson Lizardo wrote: I understand, but in this case "svn log --xml" should have output "ü" as some strange character (maybe not even a valid UTF-8 sequence) and not just keep it in "plain" ISO-8859-1 (which is what happens), right? Almost correct. "svn log --xml" should output \xc3 \xbc in

Re: [OT] Re: Commit 6803 contains invalid char on commit log

2005-10-01 Thread Alexander E. Patrakov
Alexander E. Patrakov wrote: I suggest dumping and restoring. With my toy repository at file:///home/patrakov/svn-test, the sequence of actions is: I understand that with fsfs this sequence of actions may be suboptimal. With fsfs, that's as easy as editing /home/svn/repositories/LFS/db/r

Re: [OT] Re: Commit 6803 contains invalid char on commit log

2005-10-01 Thread Anderson Lizardo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander E. Patrakov wrote: > > With fsfs, that's as easy as editing > /home/svn/repositories/LFS/db/revprops/6803 on belgarath. Don't forget > to change "V 160" to "V 161". BTW it looks like I have enough > permissions to do that :) Do you want me t

Re: [OT] Re: Commit 6803 contains invalid char on commit log

2005-10-01 Thread Alexander E. Patrakov
Anderson Lizardo wrote: Alexander E. Patrakov wrote: With fsfs, that's as easy as editing /home/svn/repositories/LFS/db/revprops/6803 on belgarath. Don't forget to change "V 160" to "V 161". BTW it looks like I have enough permissions to do that :) Do you want me to fix the log or prefer doing