[Pythonmac-SIG] Problem building PyXML v0.8 in Python v2.2

[W.T. Bridgman]

Jack,

Got it!! :^)

The alternate user didn't work, nor did the single command line, but 
the single command line commenting out the last -flat_namespace does!

In the setup.py in PyXML, there's a line:

if sys.platform[:6] == "darwin": # Mac OS X
     LDFLAGS.append('-flat_namespace')

I commented out the LDFLAGS line and that seemed to clear the 
problem.  I suspect this was added at one time for PyXML but then was 
later incorporated into the rest of the distutils package?

Looks like the rest of the build process worked as well.

Thanks for the pointer.  How does one report this so it is fixed in 
the next release?

Tom

>On Monday, September 2, 2002, at 08:53 , W.T. Bridgman wrote:
>
>>Jack,
>>
>>There is the 'cc -bundle' part as though it thinks it's a library. 
>>About the only environment variables I've changed are CVSROOT.  I'm 
>>running a straight default build.
>>
>>This is what has me wondering about the spaces in the file paths. 
>>The line parser for cc could be interpreting the entire line in 
>>very strange ways.  I know it drove me up a wall for several weeks 
>>trying to solve an earlier problem before I hit on that.
>>
>>Just where does this system get the 'darwin-5.5-Power 
>>Macintosh-2.2' string in the path?  I've looked in the setup.py 
>>file with no luck.
>
>The spaces aren't a problem. At least, they aren't for anyone 
>else:-)  Distutils creates everything under the "build" directory, 
>and the lib and temp directory names are created using the 
>architecture, OS and OS Version strings, so you can build for 
>multiple architectures in one source directory.
>
>Did you build your Python from source, yourself? Because the strange 
>thing is that this exact identical command line has been used to 
>link all of the dynamic extension modules...
>
>If you're sure you don't have any funny environment variables set (I 
>would double check, if I were you, by creating a new user and trying 
>the install as that user (without copying your login settings and 
>such, of course:-), and I would also check setup.py and/or distutils 
>for putenv() calls) then maybe could there be a funny cc somewhere 
>on your path?
>
>Hmm, another thing you could try: run the given command line 
>manually (don't forget to quote the filenames because of the spaces) 
>and see what happens? Maybe setup isn't executing the same command 
>line as it's printing? (Although I wouldn't know why...)
>--
>- Jack Jansen        <Jack.Jansen@oratrix.com>       
>http://www.cwi.nl/~jack -
>- If I can't dance I don't want to be part of your revolution -- 
>Emma Goldman -
>
>
>_______________________________________________
>Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
>http://mail.python.org/mailman/listinfo/pythonmac-sig