10 Feb
2014
10 Feb
'14
6:17 p.m.
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
10 Feb
10 Feb
6:37 p.m.
New subject: [trinity-devel] undefined symbols in all builds
Dne po 10. února 2014 Darrell Anderson napsal(a):
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.
--
Slavek
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
4015
days inactive
4015
days old
1 comments
2 participants
participants (2)
-
Darrell Anderson -
Slávek Banko