Date: Wed, 7 Jul 2004 00:46:19 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@freebsd.org Subject: Re: Odd linker errors Message-ID: <20040707074619.GC28368@dragon.nuxi.com> In-Reply-To: <20040704114855.GA83199@xor.obsecurity.org> References: <20040704023714.GA73697@xor.obsecurity.org> <40E7B878.3070203@samsco.org> <20040704091011.GA81143@xor.obsecurity.org> <40E7CC71.50008@samsco.org> <20040704114855.GA83199@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 04, 2004 at 04:48:55AM -0700, Kris Kennaway wrote: > > >>>>file.o(.text+0x623): In function `GetAOutFileInfo': > > >>>>: undefined reference to `le32toh' > > >>>>file.o(.text+0x63b): In function `GetAOutFileInfo': > > >>>>: undefined reference to `le32toh' > > >>> > > >>I can't reproduce this here. However, netbooting a VAX probably isn't > > >>a terribly common occurrance these days. > > > > > >I couldn't even find where it was calling le32toh. > > > > Are le32toh and similar functions supposed to be visible to userland? I > > thought that they were only visible to the kernel. Either way, > > something isn't right with your environment. > > That's the weird thing, this is a clean world built a few days ago, > and the port hasn't changed in 8 months. This may be related to my sys/sys/imgact_aout.h or include/a.out.h commits. I'll take a look after I'm done chasing Binutils issues. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040707074619.GC28368>