Message: previous - next
Month: February 2014

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

From: "Darrell Anderson" <darrella@...>
Date: Mon, 10 Feb 2014 12:17:01 -0600
>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 

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.