Date: Wed, 13 Apr 2005 13:52:53 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Chuck Robey <chuckr@chuckr.org> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 port of transcode broke Message-ID: <20050413205253.GA66862@troutmask.apl.washington.edu> In-Reply-To: <425D8341.6020909@chuckr.org> References: <425D7BBC.5030603@chuckr.org> <1113423334.51283.6.camel@server.mcneil.com> <425D8341.6020909@chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 13, 2005 at 08:38:25PM +0000, Chuck Robey wrote: > Sean McNeil wrote: > >On Wed, 2005-04-13 at 20:06 +0000, Chuck Robey wrote: > > > > Well, yes and no. > > You got it right, I had some funny business, and a bad link to > libXaw.so.8, so I went into /usr/X11R6/lib and fixed it up, then > reinit'ed ldconfig, and checked it with ldconfig -r, it's all right now. > There IS a libXaw.a. Unfortunately, you don't get a prize for being > right, because after that, I cleaned it up to start from scratch, and > the EXACT same error pops up. > Search the amd64 mailing list archive with "R_X86_64_32". I asked about its meaning several months agao, and someone (whose name escapes me) explained it to me. If you want to avoid the problem and move on with life CFLAG+=-static -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050413205253.GA66862>