On Friday 01 April 2005 05:45, Sean Dague wrote: > I'm noticing that mklibs had hardcoded lib64 preappends for all situations, > and am curious why this is there. It completely breaks ppc64, which builds > 32bit by default.
It completely breaks more than ppc64. It's an attempt to get x86_64bit versions to link right, but the result on a 64 bit build is that you end up getting the version from the build host distro instead of the version built from the si source tarballs. There are a number of places where this happens with the 32-bit libraries as well (e.g. e2fsprogs shared libraries are imported from build host instead of si build). Folks have gotten a bit careless with regard to noticing where libraries are coming from. Maybe mklibs works too well? A build on a debian box will work because there's good version match between the debian versions and the si versions of needed libraries, but things are very broken when you try to build on other distros. This is just one of many problems that have kept me from posting "official" 3.4.x binary rpms. It would probably be a good idea to revisit the entire build procedure with an eye toward making it look more like a stand-alone build. > > I introduce another variable, USERSPACE64 that I am trying to figure out > when to set it. Any comments from whoever put that in would be good so I > don't end up breaking you by not turning this on for your environment. > This also seems a natural candidate for the autoconf stuff :) > > -Sean ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
