From: SourceForge.net <no...@so...> - 2007-03-07 22:39:52
|
Bugs item #1676049, was opened at 2007-03-07 20:05 Message generated for change (Comment added) made by wsfulton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1676049&group_id=1645 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: preprocessor Group: None Status: Closed Resolution: Wont Fix Priority: 5 Private: No Submitted By: John Nagle (nagle) Assigned to: Nobody/Anonymous (nobody) Summary: Preprocessor doesn't define target arch. ( __i386__) Initial Comment: SWIG's preprocessor, unlike the one in GCC, does not define the target architecture symbols, like "__i386__". This causes includes of files which use those symbols to fail. This breaks builds involving "openssl", particularly M2Crypto, Python's interface to OpenSSL. (Related post by Guido von Rossum, suggesting that SWIG be dumped from Python builds: http://www.artima.com/weblogs/viewpost.jsp?thread=95863) ---------------------------------------------------------------------- >Comment By: William Fulton (wsfulton) Date: 2007-03-07 22:39 Message: Logged In: YES user_id=242951 Originator: NO The overriding goal of SWIG is to generate platform neutral code. If it were to secretly define platform specific macros this would not be possible. Besides since when is __386__ in any known standard? How is SWIG meant ever going to be aware of every known system's preprocessor definitions for all known compilers? Many of these are turned on with compiler specific commandline options, some undocumented. I'm afraid SWIG is doing the right thing here and it is up to the programmer to go out of his/her way to make SWIG generate platform specific code. ---------------------------------------------------------------------- Comment By: John Nagle (nagle) Date: 2007-03-07 22:25 Message: Logged In: YES user_id=5571 Originator: YES Status: "Developer in denial". As SWIG undertakes to emulate CPP, it should do so correctly. ---------------------------------------------------------------------- Comment By: David M. Beazley (beazley) Date: 2007-03-07 21:15 Message: Logged In: YES user_id=7557 Originator: NO Run SWIG with swig -D__i386__ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1676049&group_id=1645 |