Home Original page

Fwd: Fwd: Python freeze fails with warning: the use of `tempnam' is dangerous, better use `mkstemp'

Alexander N. Moibenko moibenko at fnal.gov
Thu Sep 8 13:27:54 EDT 2016 
On 09/08/2016 12:19 PM, Chris Angelico wrote:
> On Fri, Sep 9, 2016 at 2:50 AM, Alexander N. Moibenko <moibenko at fnal.gov> wrote:
>> The output is long so, I am replying to you only:
> Not too long, fortunately. Replying back to the list with a trimmed version.
>
>> make[1]: Entering directory `/opt/enstore/src/ENCPBIN_TEMP'
> (Curious path name.)
>
>> /opt/enstore/Python/Python-2.7.9/Modules/timemodule.o: In function
>> `_PyTime_DoubleToTimet':
>> /opt/python/python-enstore-2.7.9/Python-2.7.9/./Modules/timemodule.c:108:
>> multiple definition of `_PyTime_DoubleToTimet'
>> /opt/enstore/Python/Python-2.7.9/Modules/timemodule.o:/opt/python/python-enstore-2.7.9/Python-2.7.9/./Modules/timemodule.c:108:
>> first defined here
>> /opt/enstore/Python/Python-2.7.9/Modules/timemodule.o: In function
>> `inittime':
>> /opt/python/python-enstore-2.7.9/Python-2.7.9/./Modules/timemodule.c:851:
>> multiple definition of `inittime'
>> /opt/enstore/Python/Python-2.7.9/Modules/timemodule.o:/opt/python/python-enstore-2.7.9/Python-2.7.9/./Modules/timemodule.c:851:
>> first defined here
>> /opt/enstore/Python/Python-2.7.9/Modules/timemodule.o: In function
>> `_PyTime_FloatTime':
>> /opt/python/python-enstore-2.7.9/Python-2.7.9/./Modules/timemodule.c:1062:
>> multiple definition of `_PyTime_FloatTime'
>> /opt/enstore/Python/Python-2.7.9/Modules/timemodule.o:/opt/python/python-enstore-2.7.9/Python-2.7.9/./Modules/timemodule.c:1062:
>> first defined here
> This is.... interesting. Very interesting. Firstly, I thought you were
> trying to compile 2.7.12. Do you possibly have multiple versions of
> the source, and they're treading on each other's toes?
I tried 2.7.9 and 2.7.12. I do have multiple versions, but they do not 
mix up because I set environment appropriately.
On this particular machine I have only my own 2.7.9
>
> Do you still get these errors if you create a brand new empty
> directory, extract the 2.7.12 sources to it, and run a clean build?
This is what I usually do, in this case too.
> Particularly notable if you get 2.7.9 paths when you try to build
> 2.7.12, but still of interest if you're getting these
> multiple-definition errors on a clean build.
This is not the case.
>
> ChrisA
More information about the Python-list mailing list