On Thursday 12 May 2005 08:38, Sean Dague wrote: > Also, please ensure this boots on i386 in the next day. I don't think you > fully understand the ramifications of pulling out mklibs, and while it will > compile, nothing will actually run in the boel-binaries tarball.
Actually, I do understand the ramifications of mklibs. I didn't pull it out of the build. I made it actually use the libraries we really build instead of sneaking out into the host distro to get "better ones". If we're going to prefer the build host libraries and include files to what's in the SI source, then why the heck do we even bother downloading and building source tarballs for e2fsprogs, xfsprogs, lvm, openssh, etc? On every x86 distro upon which I tried to build 3.4.1, *lots* of stuff from the distro was being linked into the tarball INSTEAD of what we were building from source. I'll bet that the same thing is happening on ppc. Scan the log of one of your builds and just check and see where libuuid is really coming from, for example. I'd bet a dollar that it's not coming from the source we compile. Ditto that for the uuid/uuid.h file. > > If it boots, I stand corrected, if it doesn't, I think reverting would be a > good thing. > The kernel and initrd.img boot (just tested that) but they shell out pretty quick because something is looking for the /proc filesystem and it isn't there. ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
