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

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 unset

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 unset

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

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

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 of these

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: snip I understand that with fsfs this sequence of actions may be suboptimal. With fsfs, that's as easy as editing

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 to fix

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