trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: January 2014

Re: [trinity-devel] tdebase FTBFS (unpatched) undefined reference to `kdemain'

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 19 Jan 2014 06:05:17 -0600
On 01/19/2014 05:45 AM, Darrell Anderson wrote:
>>> I don't know what needs to be fixed, but obviously if Darrel is 
>> building
>>> with GCC_VISIBILITY=ON and with gcc 4.8.2-7 that is causing 
>> failure, then
>>> we need to figure out what the root of the problem is and then 
>> fix it with
>>> preprocessor conditional or fix the code. I don't understand the
>>> GCC_VISIBILITY implications entirely, but depending on the 
>> setting build
>>> failures are occurring.
>>
>> On Debian Jessie is gcc 4.8.2, tdebase is built 
>> with -DWITH_GCC_VISIBILITY="ON" and the problem does not occur.
> 
> Slackware 14.1 uses 4.8.2 and the last I tried a few weeks ago 
> everything built.
> 
> I have no idea whether glib main loop makes a difference, but I 
> always build TQt3 with -glibmainloop.
> 
> The only packages I enable gcc visibility are arts, tdelibs, 
> tdebase. If I recall correctly, visibility support never was 
> finished on non-core packages.
> 
> Darrell
> 
> 

I don't claim to understand this one, but it was the culprit. Now of course the
build fails another 9 minutes later in kicker because it can't fine
lib-dbus-tqt-1, but that looks like a cmake issue because all the files are
there, the build is just failing to include -L/opt/trinity/lib as a lib search
path.. Gremlins...


-- 
David C. Rankin, J.D.,P.E.