Exit Status 1 Build Error - Windows8 - Python 2.7
I'm running Python 2.7 - 64 bit on Win8. I''m trying to build the C libraries using the following commands, but am running in to an error.
python setup.py clean --all python setup.py build_ext --inplace --compiler=mingw32
The compiler is recognized properly and the build seems to be moving along. Then I hit this issue:
Found executable C:\MinGW\bin\g++.exe
C:\Python27\libs/libpython27.a(dmmes00976.o):(.idata$7+0x0): undefined
reference
to _head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00253.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a'
C:\Python27\libs/libpython27.a(dmmes00245.o):(.idata$7+0x0): undefined
reference
to _head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01033.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a'
C:\Python27\libs/libpython27.a(dmmes01035.o):(.idata$7+0x0): undefined
reference
to _head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01026.o):(.idata$7+0x0): more undefined refe rences to
_head_C__build27_cpython_PCBuild_libpython27_a' follow
collect2.exe: error: ld returned 1 exit status
error: Command "g++ -shared
build\temp.win32-2.7\Release\sfepy\discrete\fem\extm
ods\_fmfield.o -LC:\Python27\libs -LC:\Python27\PCbuild
-Lbuild\temp.win32-2.7 -
lsfepy_common -lpython27 -lmsvcr90 -o
sfepy\discrete\fem\extmods\_fmfield.pyd" f
ailed with exit status 1
When I run tests, I get 103/114 fails.
I followed the instructions for Windows installation here: http://sfepy.org/doc-devel/installation.html
Hi Andy,
thanks for the report(s).
What version of sfepy and other software do you have? Are you using anaconda, or other python distro for windows?
The test failures below mean that the C extension modules were not built correctly.
r.
On 07/02/2015 06:40 PM, Andy MacKrell wrote:
I'm running Python 2.7 - 64 bit on Win8. I''m trying to build the C libraries using the following commands, but am running in to an error.
python setup.py clean --all python setup.py build_ext --inplace --compiler=mingw32
The compiler is recognized properly and the build seems to be moving along. Then I hit this issue:
Found executable C:\MinGW\bin\g++.exe C:\Python27\libs/libpython27.a(dmmes00976.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00253.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00245.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01033.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01035.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01026.o):(.idata$7+0x0): more undefined refe rences to
_head_C__build27_cpython_PCBuild_libpython27_a' follow collect2.exe: error: ld returned 1 exit status error: Command "g++ -shared build\temp.win32-2.7\Release\sfepy\discrete\fem\extm ods\_fmfield.o -LC:\Python27\libs -LC:\Python27\PCbuild -Lbuild\temp.win32-2.7 - lsfepy_common -lpython27 -lmsvcr90 -o sfepy\discrete\fem\extmods\_fmfield.pyd" f ailed with exit status 1When I run tests, I get 103/114 fails.
I followed the instructions for Windows installation here: http://sfepy.org/doc-devel/installation.html
Hi Robert.
I'm using the latest sfepy clone from github. I'm running python(x,y) 2.7.10 With Python 2.7 32bit Compiler MingGW32bit c++ v4.81
Any thoughts on how to troubleshoot are appreciated.
Andy
On Thursday, July 2, 2015 at 3:16:16 PM UTC-5, Robert Cimrman wrote:
Hi Andy,
thanks for the report(s).
What version of sfepy and other software do you have? Are you using anaconda, or other python distro for windows?
The test failures below mean that the C extension modules were not built correctly.
r.
On 07/02/2015 06:40 PM, Andy MacKrell wrote:
I'm running Python 2.7 - 64 bit on Win8. I''m trying to build the C libraries using the following commands, but am running in to an error.
python setup.py clean --all python setup.py build_ext --inplace --compiler=mingw32
The compiler is recognized properly and the build seems to be moving along. Then I hit this issue:
Found executable C:\MinGW\bin\g++.exe C:\Python27\libs/libpython27.a(dmmes00976.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00253.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00245.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01033.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01035.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01026.o):(.idata$7+0x0): more undefined refe rences to
_head_C__build27_cpython_PCBuild_libpython27_a' follow collect2.exe: error: ld returned 1 exit status error: Command "g++ -shared build\temp.win32-2.7\Release\sfepy\discrete\fem\extm ods\_fmfield.o -LC:\Python27\libs -LC:\Python27\PCbuild -Lbuild\temp.win32-2.7 - lsfepy_common -lpython27 -lmsvcr90 -o sfepy\discrete\fem\extmods\_fmfield.pyd" f ailed with exit status 1When I run tests, I get 103/114 fails.
I followed the instructions for Windows installation here: http://sfepy.org/doc-devel/installation.html
Here's full bash output if you would like a look.
On Thursday, July 2, 2015 at 5:20:37 PM UTC-5, Andy MacKrell wrote:
Hi Robert.
I'm using the latest sfepy clone from github. I'm running python(x,y) 2.7.10 With Python 2.7 32bit Compiler MingGW32bit c++ v4.81
Any thoughts on how to troubleshoot are appreciated.
Andy
On Thursday, July 2, 2015 at 3:16:16 PM UTC-5, Robert Cimrman wrote:
Hi Andy,
thanks for the report(s).
What version of sfepy and other software do you have? Are you using anaconda, or other python distro for windows?
The test failures below mean that the C extension modules were not built correctly.
r.
On 07/02/2015 06:40 PM, Andy MacKrell wrote:
I'm running Python 2.7 - 64 bit on Win8. I''m trying to build the C libraries using the following commands, but am running in to an error.
python setup.py clean --all python setup.py build_ext --inplace --compiler=mingw32
The compiler is recognized properly and the build seems to be moving along. Then I hit this issue:
Found executable C:\MinGW\bin\g++.exe C:\Python27\libs/libpython27.a(dmmes00976.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00253.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00245.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01033.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01035.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01026.o):(.idata$7+0x0): more undefined refe rences to
_head_C__build27_cpython_PCBuild_libpython27_a' follow collect2.exe: error: ld returned 1 exit status error: Command "g++ -shared build\temp.win32-2.7\Release\sfepy\discrete\fem\extm ods\_fmfield.o -LC:\Python27\libs -LC:\Python27\PCbuild -Lbuild\temp.win32-2.7 - lsfepy_common -lpython27 -lmsvcr90 -o sfepy\discrete\fem\extmods\_fmfield.pyd" f ailed with exit status 1When I run tests, I get 103/114 fails.
I followed the instructions for Windows installation here: http://sfepy.org/doc-devel/installation.html
Just fyi - I deleted the sfepy folder with the failed builds and started on a new one, and the build worked. .
I guess "python setup.py clean --all" might not get rid of everything?
On Thursday, July 2, 2015 at 6:08:23 PM UTC-5, Andy MacKrell wrote:
Here's full bash output if you would like a look.
On Thursday, July 2, 2015 at 5:20:37 PM UTC-5, Andy MacKrell wrote:
Hi Robert.
I'm using the latest sfepy clone from github. I'm running python(x,y) 2.7.10 With Python 2.7 32bit Compiler MingGW32bit c++ v4.81
Any thoughts on how to troubleshoot are appreciated.
Andy
On Thursday, July 2, 2015 at 3:16:16 PM UTC-5, Robert Cimrman wrote:
Hi Andy,
thanks for the report(s).
What version of sfepy and other software do you have? Are you using anaconda, or other python distro for windows?
The test failures below mean that the C extension modules were not built correctly.
r.
On 07/02/2015 06:40 PM, Andy MacKrell wrote:
I'm running Python 2.7 - 64 bit on Win8. I''m trying to build the C libraries using the following commands, but am running in to an error.
python setup.py clean --all python setup.py build_ext --inplace --compiler=mingw32
The compiler is recognized properly and the build seems to be moving along. Then I hit this issue:
Found executable C:\MinGW\bin\g++.exe C:\Python27\libs/libpython27.a(dmmes00976.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00253.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes00245.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01033.o):(.idata$7+0x0): undefined reference to
_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01035.o):(.idata$7+0x0): undefined reference to_head_C__build27_cpython_PCBuild_libpython27_a' C:\Python27\libs/libpython27.a(dmmes01026.o):(.idata$7+0x0): more undefined refe rences to
_head_C__build27_cpython_PCBuild_libpython27_a' follow collect2.exe: error: ld returned 1 exit status error: Command "g++ -shared build\temp.win32-2.7\Release\sfepy\discrete\fem\extm ods\_fmfield.o -LC:\Python27\libs -LC:\Python27\PCbuild -Lbuild\temp.win32-2.7 - lsfepy_common -lpython27 -lmsvcr90 -o sfepy\discrete\fem\extmods\_fmfield.pyd" f ailed with exit status 1When I run tests, I get 103/114 fails.
I followed the instructions for Windows installation here: http://sfepy.org/doc-devel/installation.html
On 07/03/2015 01:53 AM, Andy MacKrell wrote:
Just fyi - I deleted the sfepy folder with the failed builds and started on a new one, and the build worked. .
Great, so you solved the problem :)
I guess "python setup.py clean --all" might not get rid of everything?
That should work. Could you try "python setup.py clean" and compare the sfepy directory contents with a fresh clone? I wonder what was left over.
Thanks, r.
I ran a comparison between a new folder and a "cleaned" folder. There are quite a few differences, but they look trivial. I attached the full list incase you are interested.
However, when I re-ran the build on the "cleaned" folder, it built correctly. so perhaps I had corrupted my original unworking folder in some other way.
On Friday, July 3, 2015 at 3:02:01 AM UTC-5, Robert Cimrman wrote:
On 07/03/2015 01:53 AM, Andy MacKrell wrote:
Just fyi - I deleted the sfepy folder with the failed builds and started on a new one, and the build worked. .
Great, so you solved the problem :)
I guess "python setup.py clean --all" might not get rid of everything?
That should work. Could you try "python setup.py clean" and compare the sfepy directory contents with a fresh clone? I wonder what was left over.
Thanks, r.
On 07/05/2015 03:27 PM, Andy MacKrell wrote:
I ran a comparison between a new folder and a "cleaned" folder. There are quite a few differences, but they look trivial. I attached the full list incase you are interested.
Thanks! Actually, the *.pyd files need to be removed - those are the compiled dynamic libraries (analogous to .so on posix systems). The commit [1] should fix that - could you try it?
[1] https://github.com/rc/sfepy/commit/97db013d8cb14476ae4fce4af41596797efa5ec3
However, when I re-ran the build on the "cleaned" folder, it built correctly. so perhaps I had corrupted my original unworking folder in some other way.
IMHO the cause were the .pyd files and the change of compiler. But whatever, it works now :)
r.
On Friday, July 3, 2015 at 3:02:01 AM UTC-5, Robert Cimrman wrote:
On 07/03/2015 01:53 AM, Andy MacKrell wrote:
Just fyi - I deleted the sfepy folder with the failed builds and started on a new one, and the build worked. .
Great, so you solved the problem :)
I guess "python setup.py clean --all" might not get rid of everything?
That should work. Could you try "python setup.py clean" and compare the sfepy directory contents with a fresh clone? I wonder what was left over.
Thanks, r.
participants (2)
-
Andy MacKrell
-
Robert Cimrman