Re: CVS commit: pkgsrc/devel/glib2

[Jörn Clausen <joernc%googlemail.com@localhost>]

On Fri, Jul 13, 2012 at 10:14 AM, David Holland
<dholland-pkgchanges%netbsd.org@localhost> wrote:
> On Thu, Jul 12, 2012 at 08:59:01AM +0200, J?rn Clausen wrote:
>  > See pkg/46478 and a bunch of complaints by me on this list.
>  > devel/libelf is simply not an option on Solaris.
>
> I remain unconvinced about this.

I can't prove it, I just take the word of a colleague (who happens to
be the port maintainer of GCC for Solaris and so I expect him to know
a little bit about the internals of Solaris, compilers, libelf and
neighboring stuff). As a result of my conversation with him about this
problem, he has filed a bug report with Oracle (that the assembler
produces empty object files without error), but it seems the bug
database is not publicly available.

> The problem described in the PR is
> that the system assembler decides to use pkgsrc libelf because it's
> linked incorrectly.

??? The assembler searches the user provided library path for libelf,
which is probably a bad idea. And the fact that assembler and linker
behave differently might be another cause.

> Did you ever figure out what was causing as to find the wrong libelf?
>
> There should be nothing that would prompt as to look in /usr/pkg/lib
> and pick up pkgsrc libelf - it is not linked with anything from
> pkgsrc, should not have an rpath pointing into /usr/pkg, /usr/pkg/lib
> should not be on the default shared library search path, and
> LD_LIBRARY_PATH should not be set.  If LD_LIBRARY_PATH is being set by
> the glib2 (or curl) build, it is wrong and the package should be
> fixed. If you've added /usr/pkg/lib to the default shared library
> search path or set LD_LIBRARY_PATH yourself, don't...

Of course I don't set LD_LIBRARY_PATH myself!

It is possible, that LD_LIBRARY_PATH is set while building curl, and
that that's the reason only this package fails. And it's probably a
bug of the system assembler to honor LD_LIBRARY_PATH when searching
for libelf instead of sticking to the native one. But even given all
that, pkgsrc's libelf IMHO simply has no purpose on Solaris, as the
only binary actually using it (glib's gresource) does not work but
segfaults. So, yes, someone could fix curl, Oracle could fix the
system assembler, but devel/libelf would still be broken on Solaris.

-- 
Joern Clausen
http://thebloeg.blogspot.com/
http://www.oe-files.de/photography/