Re: gcc4 - proposed changes to glibc check
Ken Moffat wrote: Thanks, I'm only really concerned about chapter 6 at the moment. I seem to remember somebody (Alexander, perhaps) suggesting that the correct method is to install the required locales, which for me equates to the minimal locales. I'll go with all locales if that turns out to be the official recommendation. I did recommend installing only wanted locales, but that's a workaround for BLFS bug. The bug is that GDM chooses (not well supported) UTF-8 locales in preference to non-UTF-8 ones if one selects a non-default language on the login screen. Since there will be a branch that adds some patches to address UTF-8 problems, this will become a non-issue for that branch. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: gcc4 - proposed changes to glibc check
On Tue, 6 Sep 2005, Alexander E. Patrakov wrote: Ken Moffat wrote: Thanks, I'm only really concerned about chapter 6 at the moment. I seem to remember somebody (Alexander, perhaps) suggesting that the correct method is to install the required locales, which for me equates to the minimal locales. I'll go with all locales if that turns out to be the official recommendation. I did recommend installing only wanted locales, but that's a workaround for BLFS bug. The bug is that GDM chooses (not well supported) UTF-8 locales in preference to non-UTF-8 ones if one selects a non-default language on the login screen. Since there will be a branch that adds some patches to address UTF-8 problems, this will become a non-issue for that branch. Thanks for the clarification. I'll build with all locales. 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
Commit 6803 contains invalid char on commit log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi dev's, 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 encodings before issuing a svn commit. That said, the commit 6803 on the LFS repository broke the script that generates log messages for the website, because of an non-Unicode char on its commit message. You can reproduce the problem with this command: svn log -r6803 --verbose --xml svn://svn.linuxfromscratch.org/LFS Notice that the XML header says the content is in utf-8, but the content itself contains the ü char (the uuml; HTML entity). That confuses the XML::Parser module used on the script. As a workaround, I had to force the script to always interpret its input as ISO-8859-1. Thanks, - -- Anderson Lizardo [EMAIL PROTECTED] http://www.linuxfromscratch.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFDHk7TkzNmn+NRHHoRAl1YAJ964R3wK53ZBVUIgvhgvXUAUG60nACdEd48 Q6KDGJM/tnX+BMULUmfPuR0= =cCHF -END PGP SIGNATURE- ___ Yahoo! Messenger com voz: PROMOÇÃO VOCÊ PODE LEVAR UMA VIAGEM NA CONVERSA. Participe! www.yahoo.com.br/messenger/promocao -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
