On 2007-Jun-27 01:55:25 -0700, Bakul Shah <bakul_at_bitblocks.com> wrote: >All the 32 bit ports that I tried so far (all except cvsup) >seem to work fine but they still pick up shared libs from >/usr/local/lib which will cause problems if I now add 64bit >ports. I really don't want to have to recompile and retest >any 32bit port in 64bit mode if it already works well enough. >It would be nice if 32bit ports and 64bit ports can co-exist. >Is this possible? I agree it would be nice but it's not possible at present. The ports infrastructure has no provision for handling the same port installed for different architectures so all your ports need to be either i386 or amd64 for the dependency handling to work. >Is any special set up needed in the 64bit world to >cross-compile for a i386 target? Files such as ><machine/signal.h> are specific to amd64 so one would need to >keep a copy of /usr/include from a 32bit world somewhere. Currently there's no supported way to build i386 executables on amd64. http://lists.freebsd.org/pipermail/freebsd-amd64/2007-April/009812.html contains a list of problems I found when I last tried investigating this. -- Peter Jeremy
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:13 UTC