From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 13 20:52:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D126E16A4CE for ; Wed, 13 Apr 2005 20:52:54 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6F0943D1F for ; Wed, 13 Apr 2005 20:52:54 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j3DKqrD3066986; Wed, 13 Apr 2005 13:52:53 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j3DKqr6B066985; Wed, 13 Apr 2005 13:52:53 -0700 (PDT) (envelope-from sgk) Date: Wed, 13 Apr 2005 13:52:53 -0700 From: Steve Kargl To: Chuck Robey Message-ID: <20050413205253.GA66862@troutmask.apl.washington.edu> References: <425D7BBC.5030603@chuckr.org> <1113423334.51283.6.camel@server.mcneil.com> <425D8341.6020909@chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425D8341.6020909@chuckr.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: amd64 port of transcode broke X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 20:52:54 -0000 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