Message: previous - next
Month: February 2014

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

From: Slávek Banko <slavek.banko@...>
Date: Mon, 10 Feb 2014 19:37:38 +0100
Dne po 10. �nora 2014 Darrell Anderson napsal(a):
> >I know I get caught with the real-world taking a day or two of
> >time away from
> >getting RC1 ready to freeze, but we really should be allowing at
> >least that long
> >for testing before pushing at this point.
> >
> >Like the .la -> .so push, great move forward, but we should get a
> >sign-off from
> >each of the active builders before pushing, or at least send a "I
> >am about to
> >push X that might break Y, please test.."
> I won't be surprised if others have the 'undefined symbol' errors
> too because the packages all build for me. None fail to build. If
> build without failure is the only barometer then nobody pays
> attention to the build logs. Yet my build logs are filled with the
> errors.
> My master build script options looks for a whole slew of build
> related errors and warnings and that is how I see these things all
> the time. Building without failure is only half the battle.
> Darrell

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 ). 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 ). 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.