Date: Sun, 14 May 2006 07:31:06 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Jim Prettyman <jimprettyman@gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: Running i386 binaries on amd64 Message-ID: <20060513213106.GH714@turion.vk2pj.dyndns.org> In-Reply-To: <af7830470605122306x5e37bda7n8e2e93685ab3a57f@mail.gmail.com> References: <af7830470605112305i29d5bf39o15098c39835ba943@mail.gmail.com> <84dead720605112313h51ffd83dm82b895623f4c6e27@mail.gmail.com> <af7830470605112347p69b2857cy5c647c722f22e516@mail.gmail.com> <1147422229.41363.3.camel@pav.hide.vol.cz> <af7830470605122306x5e37bda7n8e2e93685ab3a57f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2006-May-13 16:06:35 +1000, Jim Prettyman wrote: >Can you help me a bit more here? Should I create a >/usr/local/lib32/compat directory and copy the libraries from >/usr/local/lib on my i386 box to there? That's a start. Lots of ports include their own shared libraries in private directories: java, mozilla, perl, OpenOffice, python, ruby, zsh off the top of my head. These paths need to be handled as well. java, OpenOffice and mozilla also use a chain of shellscripts to appropriately configure their environment before starting - these would probably also need tweaking. >This leads me to my real question: assuming I get this to work and I >am able to run my i386 bash successfully, can I expect the same >process to give me a working version of openoffice (since it's marked >as i386 only in the ports)? OOo is far more complex than bash. You will need to play with /usr/local/OpenOffice.org1.1.5/program/soffice as well. Let us know how you get on. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060513213106.GH714>