Gianfranco <costamagnagianfra...@yahoo.it> added the comment:
My first attempt was instead of
*gcc*
to just check for
*gcc
this avoids when "icc" is the last part of the string, I admit this is not too
strong.
Another approach is to use basename with cut -d " " -
Gianfranco <costamagnagianfra...@yahoo.it> added the comment:
This was the patch I wanted to add, but I picked up a wrong one (a vbox one)
In any case, duplicate of issue28584
--
keywords: +patch
resolution: -> duplicate
Added file: https://bugs.python.org/file47596/icc-f
Gianfranco <costamagnagianfra...@yahoo.it> added the comment:
I'm attaching the patch that works also for parameters, e.g. when CC contains
--sysroot=/home/icc or similar.
we can mark https://bugs.python.org/issue33341 duplicate to this one I think
--
nosy: +locutusofborg
ve
Gianfranco <costamagnagianfra...@yahoo.it> added the comment:
I signed the contributor agreement, even if such patches shouldn't need any
kind of license
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from Gianfranco <costamagnagianfra...@yahoo.it>:
Hello, as said, in yocto we pass in $CC environment, also the --sysroot keyword.
If --sysroot contains the "*icc*" or "*gcc*" in path, the build fails because
of wrong autoconf checks.
checking in a c
New submission from Gianfranco gianz...@tin.it:
When parsing a UTF-16 little-endian encoded XML file containing some japanese
characters, the xml.sax.parse function raises a SAXParseException exception
saying no element found. Problem arises with/on:
Python 2.5.2/Windows XP Pro SP3 32 bit
