Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 2006 10:23:49 +0200
From:      Pav Lucistnik <pav@oook.cz>
To:        Jim Prettyman <jimprettyman@gmail.com>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: Running i386 binaries on amd64
Message-ID:  <1147422229.41363.3.camel@pav.hide.vol.cz>
In-Reply-To: <af7830470605112347p69b2857cy5c647c722f22e516@mail.gmail.com>
References:  <af7830470605112305i29d5bf39o15098c39835ba943@mail.gmail.com> <84dead720605112313h51ffd83dm82b895623f4c6e27@mail.gmail.com> <af7830470605112347p69b2857cy5c647c722f22e516@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Jim Prettyman p=ED=B9e v p=E1 12. 05. 2006 v 16:47 +1000:
> On 5/12/06, Joseph Koshy <joseph.koshy@gmail.com> wrote:
> > > I have just installed FreeBSD-6.1-R on an athlon64 box, which is my
> > > first ever experience with amd. I was under the impression that the
> > > amd64 machines could run binaries built for the i386, but I'm not
> > > having much luck with the system as it is now.
> >
> > What are the symptoms you see?
>=20
> My initial test was with bash from my i386 box. It failed to run with
> 'Shared object "linintl.so.6" not found'. That lib exists in
> /usr/local/lib, but is presumably the wrong type for the i386 binary
> to use.

Why do you want to run i386 bash? You can't compile a native amd64 one?

Static binaries run out of the box, dynamic binaries need relevant
libraries placed in /usr/local/lib32/compat, or wherever else you run
ldconfig -32 over them.

--=20
Pav Lucistnik <pav@oook.cz>
              <pav@FreeBSD.org>

Co vime o lasce? Laska je jako hruska. Hruska je sladka a ma urcity tvar.
Zkuste presne definovat tvar hrusky.
  -- Marigold: Pul stoleti poezie



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1147422229.41363.3.camel>