Ken wrote:
as one of the proponents of pure64, I regard it as easier ;)
[reams advice snipped]
Ken, many thx for tons of advice w/ examples! You mentioned several
of the kind of probs I anticipated plus a few surprises. It is rapidly
becoming clear to me that the transition to 64-bit clean software
still has a way to go before it stabilizes. As I feared, I guess I'm
going to have to try them both... But I guess it looks like pure64 is the
place to start.
Certainly, you won't find binaries for pure64. AFAIK for clfs this
mostly only affects browser plugins (flash, java, realplayer, ...) and
perhaps some proprietary codecs (if you had other proprietary apps,
they probably wouldn't work on anything except a specific version of
RH).
FWSC it was Skype I had in mind. Dunno about RH but it works for me
on two different Ubuntu releases (until I get as far as building X).
Yes, the target determines which version of the book, all you
change is the CLFS_HOST variable. I've no experience of non-native
builds for i{4,5}86, but I think somebody had issues a month or two
back building for i586, it's probably in the archives with the fix.
I suppose it's this one you refer to?
http://thread.gmane.org/gmane.linux.lfs.cross-lfs/1483/focus=1483
Looks like the problems there come from experimental and not-well-
understood deviations from the book, so I won't worry too much 'bout that.
If anyone else has any opinion on doing i686 -> i586 as Clfs
vs. doing it as vanilla LFS with -march, I'm listening....
Cheers,
Brandon
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
