Ken Moffat wrote:
On Fri, 30 Dec 2005, Jon wrote:
Whew... O.k... Guess I should have browsed your site more before
starting this project. I hate to do this to ya, but can I pick your
brain for just a sec? If your not in the mood, don't sweat it.
I'm usually in the mood to offer opinions, but at this time of year
they are often wrong!
I'm assuming my current toolchain should still be O.K... I was only
interested in the ppc arch anyway. I used CFLAGS="-mcpu=750 -O2
-fsigned-char" CXXFLAGS="${CFLAGS}" for everything up to this point
and will do the same for the rest of the system. I read somewhere
that you HAVE to add -fsigned-char on ppc. Took it with a grain of
salt but everything seems to be going great so far (entire toolchain).
http://linuxreviews.org/howtos/compiling/safe-cflags/
That's the only thing I could find on the web concerning CFLAGS for
PPC. What do you think of the other CFLAGS on that site for the G3?
I haven't had a G3 for a couple of years, but I'd be wary of
-fsigned-char, I seem to remember that something in BLFS (maybe X)
broke when I tried that on a G4, but that was at least a year ago.
Nowadays, I don't mess with CFLAGS if I don't need to, but I did build
everything with -mcpu=7450 -O2 on my G4 iBook.
I noticed you ditched the prefix variable on the patch program for
ppc. Is this something that is going to be removed from the LFS book?
Not sure why CPPFLAGS=-D_GNU_SOURCE is no longer needed in CLFS.
Should I use it for my final 'patch' or no? Any other diff
(figuratively and literally) I should be aware of?
You mean -D_GNU_SOURCE ? There was a report some months ago that it
was no longer necessary on ppc - certainly, we used to need it in
LFS-5.1 otherwise patch built but didn't work. In CLFS we're using an
alpha version of patch and it defines this in 'configure' so there is
no point in overriding it. For the LFS book I can't point at why this
define is now unnecessary. If you are worried, build it in /tools
without the define, then test it to see if it works!
I'm a little confused now on which book I should be following. I
still haven't started yet. I do have a single arch toolchain waiting
tho from LFS so that's what I'm going to use.
For an "easy" arch like ppc (that is, in fairly common use, a
reasonable expectation that it won't need a lot of extra patches,
32-bit), and where you are able to chroot to the new system, I think
following LFS-svn should be fine! (modulo any breakage introduced
during development, but the same applies to CLFS ).
My preference is to *always* use the same toolchain from the
beginning - CLFS is using glibc snapshots so that we can build nptl on
all the platforms we support, so since you have already built the
toolchain I recommend you to follow the LFS book except for powermac
specifics (an old G3 isn't going to be the fastest of machines to
build on). OTOH, if anybody is starting from the beginning, CLFS is
where any non-x86 stuff will be tested, but like all books in active
development it will sometimes break.
Ken
Cool. Thanks for the input. Think I'll omit -fsigned-char then and stick
to using the LFS book. I did notice the ppc specific packages in CLFS
tho. I already had mac-fdisk, hfsutils, yaboot and pmac-utils lined up
for the base install.
Thanks again Ken and Happy New Year. I'm getting old and don't dig the
party scene anymore so I'll probably be working on LFS new years eve... :-)
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
