[ python-Bugs-1158005 ] unixccompiler.py should deal with env in
linker
SourceForge.net
noreply at sourceforge.net
Thu Mar 10 00:03:52 CET 2005
Bugs item #1158005, was opened at 2005-03-07 01:42
Message generated for change (Comment added) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1158005&group_id=5470
Category: Distutils
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Edward Moy (edwardmoy)
Assigned to: Nobody/Anonymous (nobody)
Summary: unixccompiler.py should deal with env in linker
Initial Comment:
When the linker command begins with env, plus some environment
settings, and when the target is c++, the modified linker command
should place the c++ command in the proper place, which is not the
first element of the linker array.
The following seems to be fix the problem:
--- unixccompiler.py.orig 2004-08-29 09:45:13.000000000 -0700
+++ unixccompiler.py 2005-03-06 16:36:05.000000000 -0800
@@ -172,7 +172,12 @@
else:
linker = self.linker_so[:]
if target_lang == "c++" and self.compiler_cxx:
- linker[0] = self.compiler_cxx[0]
+ i = 0
+ if os.path.basename(linker[0]) == "env":
+ i = 1
+ while '=' in linker[i]:
+ i = i + 1
+ linker[i] = self.compiler_cxx[0]
self.spawn(linker + ld_args)
except DistutilsExecError, msg:
raise LinkError, msg
----------------------------------------------------------------------
>Comment By: Martin v. Löwis (loewis)
Date: 2005-03-10 00:03
Message:
Logged In: YES
user_id=21627
Hmm. Where does the "env MACOSX_DEPLOYMENT_TARGET" come
from? I cannot find it in the Python build process or
distutils. So if it is in the wxPython setup.py, it sure
must be a bug in that setup.py, no?
----------------------------------------------------------------------
Comment By: Edward Moy (edwardmoy)
Date: 2005-03-09 22:42
Message:
Logged In: YES
user_id=1233904
I was trying to build wxPython on Mac OS X. Without the change, it would
compile all .c files, then when it tried to link, it would execute a command that
looked like:
g++ MACOSX_DEPLOYMENT_TARGET=10.3 c++ ...
and fail. This is because it overwrote "env" with "g++". It needs to skip the
env and its arguments, and replace (in this case) the c++.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2005-03-08 16:08
Message:
Logged In: YES
user_id=21627
Can you please give a specific example of what you did, what
you expected to happen, and what happened instead (precise
error messages, etc)?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1158005&group_id=5470
More information about the Python-bugs-list
mailing list