Re: Odd linker errors

From: Kris Kennaway <kris_at_obsecurity.org>
Date: Sun, 4 Jul 2004 04:48:55 -0700
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;
> >
> 
> 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
> >
> 
> 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.

Kris

Received on Sun Jul 04 2004 - 09:48:59 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:00 UTC