Package: check
Version: 0.9.2-3
Severity: minor

Hello,

thanks for packaging check.

Problem is this: some code that I had and used to work, suddendly stopped
linking, most probably after an update in the last two weeks.

This is the error:

cc -g -Wall -O2 -Wall -o .libs/check_crex check_crex.o  -lcheck 
../crex/.libs/libcrex.so
check_crex.o(.text+0x1daa): In function `main':
/home/enrico/lavori/arpa/libcrex/tests/check_crex.c:344: undefined reference to 
`suite_free'

And indeed the suite_free symbol in the library is now local:

$ objdump -t /usr/lib/libcheck.a|grep suite
00000040 l     F .text  00000066 suite_free
00000000 g     F .text  0000003f suite_create
00000210 g     F .text  00000022 suite_add_tcase
000005f0 g     F .text  00000011 srunner_add_suite
00000160 g     F .text  00000025 log_suite_start
00000190 g     F .text  00000025 log_suite_end
000000b0 l     F .text  000000ae srunner_iterate_suites
00000000         *UND*  00000000 log_suite_start
00000000         *UND*  00000000 log_suite_end


I found a mention about this in the NEWS file:

Mon, May 17, 2004: Released Check 0.9.0

Run fixture teardowns in reverse order to setup
Plugged some memory leaks.
Added test name to log outputs.
Applied patch (802160) for distcheck bug (579604).
Fixed log printouts for nofork mode.
Updated documentation and converted to DocBook.

Added a new print mode, CK_ENV, that gets the print mode from the
environment variable CK_VERBOSITY.

Made tcase_free and suite_free static. This may break existing test
programs. Everything is now freed when srunner_free is called.


I'm suggesting you put a notice about this source incompatibility in 
README.Debian or NEWS.Debian, as it could be useful to people upgrading and it
is a possible cause of FTBFS bugs.


Ciao,

Enrico

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to