Jakub Jelinek is going to release glibc-2.6.1 soon and says he will
also release 2.5.1 if there's demand.
http://sources.redhat.com/ml/libc-alpha/2007-07/msg00045.html
I've just committed a new patch from upstream's 2.5 branch that I'll
push into the book.
Jon Fullmer wrote:
When putting this system for a non-x86 (PowerPC, to be specific), I
noticed that this setup is actually wrong.
You may want to check out http://trac.cross-lfs.org/ for the PowerPC.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ:
Gentlemen,
Forgive a novice to this list. I couldn't find any mention of this,
so if it's already been talked about, I'm sorry.
Step 5.7 of the recent development book shows this step currently to
generate the specs file:
gcc -dumpspecs | sed '[EMAIL PROTECTED]/lib/ld-linux.so.2@/tools@g' \
Randy McMurchy wrote:
Hi all,
This is mostly to DJ, but FYI to everyone else, with comments welcome.
I'd like to propose that we ditch 3 of the JDK patches and use seds
instead.
Additionally, I modified the GCC4 patch to do the following:
1. Remove the fix to the assembly as it is now
I don't understand. I'm aware of CLFS (and even for the PowerPC).
This is assuming I want to build a system on a platform other than
its destined platform. I'm actually building it on a PowerPC box
running LFS-6.2. That's not the point.
The reason I mentioned that I was doing this on
Jon Fullmer wrote:
I don't understand.
Jon, LFS is targeted at x86 and therefore the instructions are only tested
there and not guaranteed to work on other arches. I've done ppc builds
myself and can confirm that specs files do indeed differ per arch and GCC
version. Of course, even the *name*
On Jul 12, 2007, at 9:06 PM, Greg Schafer wrote:
I've done ppc builds
myself and can confirm that specs files do indeed differ per arch
and GCC
version. Of course, even the *name* of the dynamic linker is
different for
ppc.
THAT'S what I wanted to know. Yes, I know that x86 uses
On Jul 12, 2007, at 8:46 PM, Jon Fullmer wrote:
Gentlemen,
Forgive a novice to this list. I couldn't find any mention of this,
so if it's already been talked about, I'm sorry.
Step 5.7 of the recent development book shows this step currently to
generate the specs file:
gcc -dumpspecs |
