trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] undefined symbols in all builds

From: "Darrell Anderson" <darrella@...>
Date: Mon, 10 Feb 2014 13:01:38 -0600
>You can be sure that I patch tested several times.
>
>Initial patch from Fran├žois caused FTBFS (as you can find earlier 
>in the 
>mailing-list http://trinity-devel.pearsoncomputing.net/?0::11678 
>). So I 
>worked on the patch longer time and tested on various versions of 
>Debian / Ubuntu distributions. Patch to solve the problem of 
>hidden-visibility was published on 20 January (see 
>http://bugs.pearsoncomputing.net/show_bug.cgi?id=1560#c111 ). In 
>testing I 
>tested building tdelibs, tdebase and tdevelop (which is the only 
>one who 
>used tqassistant). After all the testing I pushed patches on 2 
>Feb.

I'm sure you tested. You almost always do. All I'm saying is none 
of us were invited to test. If I had run the patches a week ago I 
would have discovered the messages immediately. The messages snuck 
past me for the past few days because I'm knee deep in working on 
the help handbooks and I'm not building fresh package sets as often.

In the bug report you mention hidden visibility and shared versus 
static.

In my tqt3 build script configuration I am using "-shared" and I 
have used that option from the beginning. I don't have any 
configuration option about visibility like other build script 
configurations. When I run configure --help I don't see any options 
related to visibility. Should I? My build log is filled with "-
fvisibility=hidden -fvisibility-inlines-hidden."

I am running multiple builds of tqt3 so you will be able to see how 
each build run results in a different 'undefined symbol' message.

Darrell