[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tinycc-devel] [PATCH] Re: Symbol collision for function error

From: Mitchell N Charity
Subject: [Tinycc-devel] [PATCH] Re: Symbol collision for function error
Date: Fri, 17 Jul 2009 13:30:53 -0400
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

The symbol collision problem is fixed in mob branch.
error() wasn't alone - libtcc was dumping  80+ symbols
into the global namespace without prefixes.

error() is now exported as _tcc_error, not as tcc_error as was
suggested, because it seems to be a private function, not part
of the libtcc public api.  Eg, it's not in libtcc.h (which has
a tcc_set_error_func instead).


commit 156219349ab8a43b319cec17739a43d5c74669f7
Author: Mitchell N Charity <address@hidden>
Date:   Fri Jul 10 15:47:12 2009 -0400

     Fix the script for generating tcc.h symbol prefix #defines.
     It no longer incorrectly adds a _tcc_ prefix to symbols which
already have it.

commit 3276b44a4cb209592fa651c8c51f8bd48c153368
Author: Mitchell N Charity <address@hidden>
Date:   Fri Jul 10 15:19:02 2009 -0400

     Fix libtcc symbol namespace pollution and user conflicts.
     All defined global symbols now have either a tcc_ (public api) or
_tcc_ prefix.
     (There had been 80+ unprefixed global symbols defined in libtcc).
     This should resolve the reported link failures due to "error()"

commit 64f5aea32511c642e5e3a78fc9714b25f01d1c24
Author: Mitchell N Charity <address@hidden>
Date:   Fri Jul 10 13:34:52 2009 -0400

     Check getcwd() return value for error.  Thus silencing a gcc warning.

commit 8b7288cec7597fc8c092cdd77fa56b33ba2ff562
Author: Mitchell N Charity <address@hidden>
Date:   Fri Jul 10 12:40:22 2009 -0400

     Avoid gcc warning about printf %*s precision type.
     gcc 4.3.3 x86_64-linux-gnu warns:
       libtcc.c: In function 'tcc_open':
       libtcc.c:1186: warning: field width should have type 'int', but
argument 3 has type 'long int'
     This patch eliminates the warning by casting to int.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]