> One way would be to set up local package descriptions which build as > 32-bit rather than 64-bit, e.g. via flags given to the compilers, and > have them install in a private directory.
hmmmm... this sounds like the way to go. BUT how to set up like this? > $ dpkg -L libpng15-32bit-shlibs yeilds: Package `libpng15-32bit-shlibs' is not installed. Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. m On Mon, Mar 4, 2013 at 3:38 PM, Alexander Hansen <[email protected]> wrote: > On 3/4/13 1:10 PM, me.grimm wrote: >> Hello, >> >> The other day I was trying to think of the best way to do this. My dev >> system is 10.7 so all my fink builds/libs/etc are 64-bit. But what if >> I wanted to build something (dyn libs,etc) for 32 bit systems. >> >> 1) Could I run a second installation of Fink for 10.5 next to my 10.7 >> installation? /sw2 for example? >> 2) Run a full 10.5 osx system with virtual box on top of 10.7 >> >> what would be the best and cleanest way to do this? >> >> unless one can just rebuild each lib as universal that is needed in >> the installation I have already. Although I don't know how to do this. >> >> Thanks for info ahead of time! >> m >> > > One way would be to set up local package descriptions which build as > 32-bit rather than 64-bit, e.g. via flags given to the compilers, and > have them install in a private directory. > > For example, see the existing 32bit packages for 10.7-10.8: > > $ dpkg -L libpng15-32bit-shlibs > /. > /sw > /sw/lib > /sw/lib/i386 > /sw/lib/i386/libpng15.15.dylib > /sw/share > /sw/share/doc > /sw/share/doc/libpng15-32bit-shlibs > /sw/share/doc/libpng15-32bit-shlibs/ANNOUNCE > /sw/share/doc/libpng15-32bit-shlibs/CHANGES > /sw/share/doc/libpng15-32bit-shlibs/INSTALL > /sw/share/doc/libpng15-32bit-shlibs/LICENSE > /sw/share/doc/libpng15-32bit-shlibs/README > /sw/share/doc/libpng15-32bit-shlibs/TODO > > where the library gets installed in /sw/lib/i386 to avoid collisions > with the regular libpng15. One nice thing about this method is that it > should work the same way on anybody's 10.7 or 10.8 system, so help with > details will be easy to get. > > > Doing a 32bit Fink on 10.5 or 10.6 in VirtualBox has a couple of pitfalls: > > 1) Even getting your 10.5 or 10.6 to work. > 2) Speculative: some libraries may not actually be forward compatible. > > but that's more or less like having an additional system where Fink will > do 32-bit builds. > > > To build universal binaries would require extensive hacking of the Fink > build process. > > -- > Alexander Hansen, Ph.D. > Fink User Liaison > My package updates: http://finkakh.wordpress.com/ -- ____________________ m.e.grimm | m.f.a | ed.m. [email protected] _________________________________ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
