On 05/03/2012 16:42, Bernt Hansson wrote: > > Thank you for the pointer. I do find it a bit overkill to setup jails > and such, just to build a few ports. I was thinking more along the line of; > > cd /usr/ports/"random port" > > make "it for i386 even if we are building it on amd64, ooh by the way > build it as a package, and all dependencies as packages as well" > > Oh man, man ports. But I do not find the flag > -build-for-another-system-cpu-whatever > > Can the ports system be (ab)used in that way?
In general, no. There may be some ports that you could cross-compile,
but that depends on the upstream software having support for cross
compilation (basically allowing "--target foo" into the compilation
flags.) Even if you fix that you're going to run into difficulties as
soon as you try and compile a port that depends on shared libraries from
another port. I don't think there's any mechanism for installing 32-bit
shlibs into ${LOCALBASE}/lib32 from packages.
Oh, and making packages is potentially a mine field, as you need to
install the port in order to package it.
About the only way to cross-build ports is to set up a 32-bit jail on a
64-bit host. I believe that is do-able, but I could be delusional.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
