9 Mar
2012
9 Mar
'12
7:49 p.m.
On 03/09/2012 01:04 PM, Darrell Anderson wrote:
Yes, I understand that gcc is becoming more
persnickety with each release. All I am questioning is why the failure with ksnapshot? No
previous build used Xext to build ksnapshot. I see the "-lXext" reference in my
build log for kuickshow but not with ksnapshot. Seems gcc is overextending itself and
linking things that previously were not linked.
Darrell
Hmm...,
You got me there. As far as gcc goes "mine is not to question why, only to
[feed that SOB what it needs]" :)
I think looking through ksnapshot/ConfigureChecks.cmake, there is an explicit
check include for the shape.h header and another referenced to $(XGETTEXT) in
Makefile.am. I don't know if that is what is driving the libXext linker
dependency, but that was as far as I questioned it -- then I just fed it to gcc :)
--
David C. Rankin, J.D.,P.E.