From owner-freebsd-current@FreeBSD.ORG Sun Jul 4 11:48:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C38DA16A4CE for ; Sun, 4 Jul 2004 11:48:59 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 851A043D49 for ; Sun, 4 Jul 2004 11:48:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35])i64BmtCZ026256; Sun, 4 Jul 2004 07:48:55 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2E401521DF; Sun, 4 Jul 2004 04:48:56 -0700 (PDT) Date: Sun, 4 Jul 2004 04:48:55 -0700 From: Kris Kennaway To: Scott Long Message-ID: <20040704114855.GA83199@xor.obsecurity.org> References: <20040704023714.GA73697@xor.obsecurity.org> <40E7B878.3070203@samsco.org> <20040704091011.GA81143@xor.obsecurity.org> <40E7CC71.50008@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <40E7CC71.50008@samsco.org> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Kris Kennaway Subject: Re: Odd linker errors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 11:48:59 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 04, 2004 at 03:22:57AM -0600, Scott Long wrote: > >Ah, okay..I was checking 4.x's malloc(3), which says: > > > >char * malloc_options; > > >=20 > Would it make sense to revert HEAD back to 'malloc_options'? It looks > like it was changed in rev 1.43 of stdlib.h with a rather vague commit > message. Odd, I wonder why this hasn't come up before. I guess not many applications use malloc_options. > >>>>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. > > > >Kris > > >=20 > Are le32toh and similar functions supposed to be visible to userland? I= =20 > thought that they were only visible to the kernel. Either way,=20 > 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. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA5+6nWry0BWjoQKURAqgEAKCXFO3JKz4rmU6LO2v4UQNAApX7LwCgnIgh OxtIp86zaW0XFZyc254s2+U= =aq9B -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--