On Wed, Oct 10, 2007 at 10:58:16PM +0100, Ken Moffat wrote:
> On Mon, Oct 08, 2007 at 12:23:29AM +0100, Ken Moffat wrote:
> > On Sat, Oct 06, 2007 at 08:14:46PM -0600, Jeremy Huntwork wrote:
> > > On Sat, Oct 06, 2007 at 08:09:45PM -0600, [EMAIL PROTECTED] wrote:
> > > > Log:
> > > > Made book buildable by powerpc.
> [...]
> > > Ken, care to make a test run?
> > > 
> >  OK, I'll pencil a build in for this week,
> 
>  At the risk of severely upsetting anyone who doesn't think ppc
> belongs in LFS ...  I'm _dubious_ about using patch-2.5.4 on ppc
> without -D_GNU_SOURCE.  However, preliminary testing (use my local
> "LFS-6.3-on-ppc" system, build 2.5.4 there, see if all the patches
> I know I will be using up to the first parts of my desktop, plus a
> big gcc-svn gnu diff, *claim* to apply) has not found a problem, so
> I'll start the build tomorrow.
> 
>  The original bugzilla entry is preserved as
> http://wiki.linuxfromscratch.org/lfs/ticket/242  but sadly without
> any details of exactly how it breaks.  On clfs we've been able to
> drop it because the alpha version of patch used there does the
> define in the configure script if it isn't already defined.  I see
> no reason to use an alpha version of patch in LFS, but it's possible
> that building patch on ppc without reinstating this define may break
> something.
> 
 Just to close this, even if ppc doesn't make it back into the book:
My build against 2.6.23 headers is now complete, including a whole
load of vaguely AV stuff I never used to bother with (cdrdao with
all the gnome bits, gstreamer, ffmpeg, flac, kdemultimedia, k3b) and
might yet discard after I've had time to test them.  There were zero
issues with patch-2.5.4.  I'm guessing the old problem(s) was/were
either with some obscure patch format, or else -DGNU_SOURCE is now
being defined anyway, perhaps in glibc.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to