Hi, I got the same warning by Debian's tool Lintian:
X: libaacs0: shlib-calls-exit usr/lib/libaacs.so.0.1.0 N: N: The listed shared library calls the C library exit() or _exit() N: functions. N: N: In the case of an error, the library should instead return an N: appropriate error code to the calling program which can then determine N: how to handle the error, including performing any required clean-up. N: N: In most cases, removing the call should be discussed with upstream, N: particularly as it may produce an ABI change. And yes, one may redefine the macro YY_FATAL_ERROR to print some warnings and then cleaning-up and stop there. However, IMHO the question is still open upstream and it had better to return an error code, hence let the caller decide what's the best for him rather than printing a message out and exit. Since this would clearly mean an ABI break, I'd like to discuss this with you rather than patching libaacs in Debian. Thank you guys for any reply, and keep up the great work! Cheers, -- Alessio Treglia | www.alessiotreglia.com Debian Developer | [email protected] Ubuntu Core Developer | [email protected] 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 _______________________________________________ libaacs-devel mailing list [email protected] http://mailman.videolan.org/listinfo/libaacs-devel
