r1373 - / trunk/BOOK trunk/BOOK/cross-tools trunk/BOOK/cross-tools/64 trunk/BOOK/cross-tools/common trunk/BOOK/cross-tools/mips trunk/BOOK/cross-tools/mips64 trunk/BOOK/cross-tools/mips64-64 trunk/BOOK/cross-tools/multilib trunk/BOOK/cross-tools/ppc trunk/BOOK/cross-tools/sparc64 trunk/BOOK/cross-tools/sparc64-64 trunk/BOOK/final-system/mips trunk/BOOK/final-system/mips64 trunk/BOOK/final-system/sparc64-64 trunk/BOOK/final-system/x86_64-64

Jeremy Huntwork jhuntwork at linuxfromscratch.org
Thu Apr 13 19:04:29 PDT 2006

Justin R. Knierim wrote:
> I'm not so sure about the "then when there *is* something pertaining to 
> development asked, it goes ignored" as I haven't seen this.  Looking 
> through the archives, I see most emails answered.  Although the spam and 
> virus emails which almost outnumber the real emails nowadays might have 
> hidden something.

I've counted 9 emails that, in the last 2 weeks or so got no response at 

> As for the change to the new glibc and gcc, it has been in Trac as a bug 
> sent to the cross-lfs list over a month ago.  It is not like LFS where 
> tickets go to lfs-book where they are somewhat hidden, on cross-lfs it 
> is all there.  Jim, Ryan, Joe and Chris all commented on the tickets, so 
> I don't know what else there is to discuss.  It is just my opinion, but 
> emailing the list to say "I'm adding glibc-2.4 to the book" is redundant 
> when there is the open ticket.  If jim had problems (which judging by 

I wasn't disputing the adding of glibc-2.4. All I wanted to know is why 
cross-tools/glibc.xml was removed for sparc64. This has been answered, 
so that's that.


More information about the cross-lfs mailing list