Date: Wed, 14 May 2008 05:00:57 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Bakul Shah <bakul@bitblocks.com> Cc: stable@freebsd.org, Pete French <petefrench@ticketswitch.com> Subject: Re: Changing an installed system from i386 to amd64 Message-ID: <20080513190057.GH64804@server.vk2pj.dyndns.org> In-Reply-To: <20080513153303.35BFA5B55@mail.bitblocks.com> References: <E1JvvKu-00051a-8q@dilbert.ticketswitch.com> <20080513153303.35BFA5B55@mail.bitblocks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-May-13 08:33:03 -0700, Bakul Shah <bakul@bitblocks.com> wrote: >Most all old 32 bit ports should work but upgrading them can >mess things up. All the new compiles will generate 64 bit >binaries but any port dependencies on a shared library will >be wrong. It's actually somewhat worse than this: When compiling a new port with dependencies, the internal foo_DEPENDS logic will detect the i386 .so but the port's own configuration tools or build process will normally die in interesting ways when they can't actually use that .so. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgp5WkACgkQ/opHv/APuIczYgCgqDl1NlLLXi1qwflknOQGeqxW 4vAAoJYFAEk3/MFsdM1lrbeXHT9kd9oA =tUZW -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080513190057.GH64804>