Date: Sat, 21 Dec 2013 00:07:02 +0100 From: John Marino <freebsd.contact@marino.st> To: Koop Mast <kwm@rainbow-runner.nl> Cc: bsam@freebsd.org, freebsd-ports@freebsd.org Subject: Re: x11/fbpanel: pkg fallout at 10.x Message-ID: <52B4CD96.4070504@marino.st> In-Reply-To: <52B4B49D.1070808@rainbow-runner.nl> References: <52B3E6DE.8060300@passap.ru> <20131220065824.GE11355@ithaqua.etoilebsd.net> <52B44C2C.4060001@passap.ru> <52B44D7B.7060407@marino.st> <52B4B49D.1070808@rainbow-runner.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------060803070302010707070109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 12/20/2013 22:20, Koop Mast wrote: > 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. Hmm, I fixed it differently. I waited until now until the partial bulk build completed, which confirmed the fix worked. The attached "Makefile.DragonFly" has been present for months, but the diff to the Makefile is what was missing which caused a bad .pc file generation. After adding the one line to the makefile and in addition to the changes in Makefile.DragonFly, all the broken ports built. John --------------060803070302010707070109 Content-Type: text/plain; charset=windows-1252; name="Makefile.diff.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Makefile.diff.txt" LS0tIE1ha2VmaWxlLm9yaWcJMjAxMy0xMi0yMCAxNjoyOToyNS45MTA0NjkwMDAgKzAwMDAK KysrIE1ha2VmaWxlCkBAIC02MSw2ICs2MSw3IEBAIHBvc3QtcGF0Y2g6CiAJQCR7RklORH0g JHtXUktTUkN9IC1uYW1lICJNYWtlZmlsZS5pbiIgfCAke1hBUkdTfSAke0dSRVB9IC1sIGxn bW9kdWxlIHwgXAogCQkke1hBUkdTfSAke1JFSU5QTEFDRV9DTUR9IC1lICdzfC1sZ21vZHVs ZXxAR01PRFVMRV9MSUJTQHxnJwogCUAke1JFSU5QTEFDRV9DTUR9IC1lICdzfFt7XWxpYmRp clt9XS9sb2NhbGV8e2RhdGFkaXJ9L2xvY2FsZXxnJyBcCisJCS1lICdzfEdUS19QQUNLQUdF UyBwYW5nb2Z0MnxHVEtfUEFDS0FHRVMgeDExIHBhbmdvZnQyfCcgXAogCQkke1dSS1NSQ30v Y29uZmlndXJlCiAJQCR7UkVJTlBMQUNFX0NNRH0gLWUgJ3N8QExOX1NAfCR7TE59IC1zZnwn ICR7V1JLU1JDfS9ndGsvTWFrZWZpbGUuaW4KIAlAJHtSRUlOUExBQ0VfQ01EfSAtZSAnc3xm aWxlLGN1cHN8ZmlsZSxjdXBzLGxwcnwnIFwK --------------060803070302010707070109 Content-Type: text/plain; charset=windows-1252; name="Makefile.DragonFly.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Makefile.DragonFly.txt" VVNFX1hPUkcrPQlwaXhtYW4KCkxJQl9ERVBFTkRTKz0JcG5nMTU6JHtQT1JUU0RJUn0vZ3Jh cGhpY3MvcG5nCkxJQl9ERVBFTkRTKz0JZnJlZXR5cGUuOToke1BPUlRTRElSfS9wcmludC9m cmVldHlwZTIKTElCX0RFUEVORFMrPQlmb250Y29uZmlnOiR7UE9SVFNESVJ9L3gxMS1mb250 cy9mb250Y29uZmlnCkxJQl9ERVBFTkRTKz0JY2Fpcm86JHtQT1JUU0RJUn0vZ3JhcGhpY3Mv Y2Fpcm8KTElCX0RFUEVORFMrPQlleHBhdDoke1BPUlRTRElSfS90ZXh0cHJvYy9leHBhdDIK --------------060803070302010707070109--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52B4CD96.4070504>