Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Dec 2013 22:20:29 +0100
From:      Koop Mast <kwm@rainbow-runner.nl>
To:        marino@freebsd.org, freebsd-ports@freebsd.org, bsam@freebsd.org
Subject:   Re: x11/fbpanel: pkg fallout at 10.x
Message-ID:  <52B4B49D.1070808@rainbow-runner.nl>
In-Reply-To: <52B44D7B.7060407@marino.st>
References:  <52B3E6DE.8060300@passap.ru> <20131220065824.GE11355@ithaqua.etoilebsd.net> <52B44C2C.4060001@passap.ru> <52B44D7B.7060407@marino.st>

next in thread | previous in thread | raw e-mail | index | archive | help
On 20-12-2013 15:00, John Marino wrote:
> On 12/20/2013 14:54, Boris Samorodov wrote:
>> 20.12.2013 10:58, Baptiste Daroussin пишет:
>>> On Fri, Dec 20, 2013 at 10:42:38AM +0400, Boris Samorodov wrote:
>>> gtk2 pkgconfig file is not adding -lX11 to LDFLAGS anymore.
>>> In general: on FreeBSD 10+, the ld(1) behaviour has been changed so that it does
>>> not recursively get the DT_NEEDED from libraries it linked binaries to.
>>> Meaning in that case something exposes a X function to fbpanel, but does not
>>> tell it is needs to link to X11
>>>> /usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition
>>>> //usr/local/lib/libX11.so.6: could not read symbols: Bad value
>>> LDFLAGS+= -lX11 should solve this.
>> I've seen some similar commit at the portstree. The problem is: I can't
>> reproduce the errors (hence can't test a fix).
> I've recently seen dozens of similar, new errors on dports/dragonfly.
> It's definitely a pkgconf issue and it just appeared.
> I haven't tracked it done yet, but adding LDFLAGS+= to every broken port
> is not ideal.  It's better to figure out which .pc file is broken and
> fix that.
>
> John

Should be fixed now, I restored the "old" behaviour.

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52B4B49D.1070808>