Quoting Paul Smith :
My case may be unusual but even in a
more formal cross-compilation environment it's not good to
add /usr/include/..., or base such a decision on the behavior of the
_build_ system.
The offical procedure to cover "unusual" cases is to edit Modules/Setup.
If you are not hap
In article <137129.4119.53.camel@homebase>,
Paul Smith wrote:
> It seems to me (keeping with the theme of this mailing list) that the
> add_multiarch_paths() function in setup.py is not right. [...]
If you think there is a problem, please open an issue for it on the
Python bug tracker: htt
On Fri, 2013-05-31 at 01:21 -0700, Ned Deily wrote:
> In article <1369986770.4119.43.camel@homebase>,
> Paul Smith wrote:
>
> > Hi all. I'm trying to build Python 2.7.5 on a GNU/Linux (Linux Mint 14)
> > system, but using a different sysroot (that is, a separate
> > /usr/include, /usr/lib, etc.
In article <1369986770.4119.43.camel@homebase>,
Paul Smith wrote:
> Hi all. I'm trying to build Python 2.7.5 on a GNU/Linux (Linux Mint 14)
> system, but using a different sysroot (that is, a separate
> /usr/include, /usr/lib, etc., not the real one for my system).
This list is for the develop
Hi all. I'm trying to build Python 2.7.5 on a GNU/Linux (Linux Mint 14)
system, but using a different sysroot (that is, a separate
/usr/include, /usr/lib, etc., not the real one for my system).
I have shell script wrappers around GCC and its various tools that
invoke it with the right paths to fo
