Re: undefined functions and lazy dlopen()

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Sat, Jan 25, 2014 at 09:23:43AM -0500, Michael wrote:
> Hello,
> 
> On Sat, 25 Jan 2014 13:14:14 +0100
> Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
> 
> > On Fri, Jan 24, 2014 at 03:42:45PM -0500, Michael wrote:
> > > On Fri, 24 Jan 2014 13:39:52 +0100
> > > Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
> > > 
> > > > On Thu, Jan 23, 2014 at 09:22:40PM -0500, Michael wrote:
> > > > > I've seen this too, got around it by telling xorg to unconditionally 
> > > > > load the respective modules ( I think Load statements in the Server 
> > > > > section did the trick ).
> > > > 
> > > > Yes, that would work around the issue. But as I mentionned later, it
> > > > turns out it's a gcc bug which was fixed upstream, and for which I have
> > > > a patch.
> > > 
> > > And I've been poking around in our dynamic linker, obviously without 
> > > success,
> > > I thought it's a problem in there since I've seen this bug only on 
> > > Loongson, but not on sgimips.
> > 
> > It's a bug affecting only N32/N64, but not O32.
> 
> I meant N32 on sgimips. Before the latest messup it was almost usable, 
> including X, but unfortunately not gcc.

So it's probably your were lucky :)
The bug affetcs only some symbols, in some specific cases.
That's why the loader doesn't complain about all lasy symbols but only one ...

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--