Solaris 8/x86: Build problems
Mats Wichmann
xyzmats at laplaza.org
Wed Jun 20 10:58:18 EDT 2001
On 17 Jun 2001 13:29:34 +0200, Martin von Loewis
<loewis at informatik.hu-berlin.de> wrote:
>xyzmats at laplaza.org (Mats Wichmann) writes:
>
>> I'll go back and extricate that soon. Up until you get to
distutils,
>> all the compile steps spit out for easy capture, but once you get
the
>> the module building phase, it not longer automatically tells you
what
>> each step is doing.
>
>It sure does. To re-run all compilation steps, you have to either
make
>clean, or remove the "build" directory tree. distutils will then
>report any compiler invocation it issues.
And so it does.
And when I redid it this way to see what was wrong, nothing was wrong
any longer, everything built okay.
I do know what the difference was: the earlier time through, the build
was done with an environment variable "CC=gcc", the second time, where
it worked, that was not set.
Curious (but no more than that, since I now have a working Python 2.1)
why that makes a difference? I had the "CC=gcc" set while I was doing
"configure" on a whole bunch of packages, Python happened to be just
one of them.
Mats Wichmann
(Anti-spam stuff: to reply remove the "xyz" from the
address xyzmats at laplaza.org. Not that it helps much...)
More information about the Python-list
mailing list