test_zlib failed on python runner.py #24
Comments
|
It looks like it isn't succeeding to build the project. Can you try to build it normally (do ./configure and make in a copy of the zlib directory)? |
|
en, yes, I can build it successfully on the command line . But It'll fail on executing in the scirpt. running the ammo.js/build.py is similar: =====================
Stage 1: Build Bullet
=====================
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... /opt/src/emscripten/tools/emmaken.py
checking whether the C compiler works... no
configure: error: in `/opt/src/ammo.js/bullet/build':
configure: error: C compiler cannot create executables
See `config.log' for more details
make: *** No targets specified and no makefile found. Stop.
=============
Stage 2: Link
=============directly run in command is ok: /opt/src/ammo.js/$ cd bullet\build
/opt/src/ammo.js/bullet/build$ RANLIB=/opt/src/emscripten/tools/emmaken.py AR=/opt/src/emscripten/tools/emmaken.py CXX=/opt/src/emscripten/tools/emmaken.py CC=/opt/src/emscripten/tools/emmaken.py ../configure --disable-demos --disable-dependency-tracking |
|
Can you paste the config.log file it mentions there? That will have more details. Also, please find the lines in tests/runner.py beginning with and add "print" before them (without "s), so it prints as it tries to compile. That will give some more output for zlib. |
|
OK, I got the reason of test_zlib failed. the configure needs the CFLAGS to specify the includes path. export CFLAGS='-I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu'
export CPPFLAGS='-I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu'the only problem is the bullet left. |
|
Looks like a linking error, the glu32 and opengl32 libs are not present? They are just needed for the configure tests. Might be a way to hack configure so it ignores them. |
|
run "configure" on command line passed. Failed only on running build.py or runner.py: It stops on the configure stage for testing the compiler on conftest.c: configure:3569: checking whether /opt/src/emscripten/tools/emmaken.py accepts -g
configure:3589: /opt/src/emscripten/tools/emmaken.py -c -g -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu conftest.c >&5
emmaken.py: /opt/src/emscripten/tools/emmaken.py -c -g -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu conftest.c
Running: /opt/src/llvm-gcc-4.2-2.9/bin/llvm-gcc -c -g -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu conftest.c -m32 -U__i386__ -U__x86_64__ -U__SSE__ -UX87_DOUBLE_ROUNDING -UHAVE_GCC_ASM_FOR_X87
configure:3589: $? = 0
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "bullet"
| #define PACKAGE_TARNAME "bullet"
| #define PACKAGE_VERSION "2.78"
| #define PACKAGE_STRING "bullet 2.78"
| #define PACKAGE_BUGREPORT "bullet@erwincoumans.com"
| #define PACKAGE_URL ""
| #define PACKAGE "bullet"
| #define VERSION "2.78"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| } |
|
What happens when you run that command (right after emmaken.py: in that output) on the file it mentions? |
|
The above is the error information in the config.log. here is the command line output, the configure failed, no Makefile generated: :/opt/src/ammo.js$ ./build.py
=====================
Stage 1: Build Bullet
=====================
../configure --disable-demos --disable-dependency-tracking
CONF:CFLAGS= -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu
CONF:CFLAGS= -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... /opt/src/emscripten/tools/emmaken.py
checking whether the C compiler works... no
configure: error: in `/opt/src/ammo.js/bullet/build':
configure: error: C compiler cannot create executables
See `config.log' for more details
(None, None)
make: *** No targets specified and no makefile found. Stop.
=============
Stage 2: Link
=============
/opt/src/llvm-2.9/bin/llvm-link src/.libs/libBulletCollision.a src/.libs/libBulletDynamics.a src/.libs/libLinearMath.a -o libbullet.bc
/opt/src/llvm-2.9/bin/llvm-link: src/.libs/libBulletCollision.a: Could not open input file: No such file or directory
/opt/src/llvm-2.9/bin/llvm-link: error loading file 'src/.libs/libBulletCollision.a'
Traceback (most recent call last):
File "./b.py", line 82, in <module>
assert os.path.exists('libbullet.bc'), 'Failed to create client'
AssertionError: Failed to create clientAll r ok if I run this on the bash cmd line directly: /opt/src/ammo.js/bullet/build$ CFLAGS='-I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu' \
> CPPFLAGS='-I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu' \
> RANLIB=/opt/src/emscripten/tools/emmaken.py \
> AR=/opt/src/emscripten/tools/emmaken.py \
> CXX=/opt/src/emscripten/tools/emmaken.py \
> CC=/opt/src/emscripten/tools/emmaken.py \
> ../configure --disable-demos --disable-dependency-tracking
CONF:CFLAGS= -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu
CONF:CFLAGS= -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... /opt/src/emscripten/tools/emmaken.py
checking whether the C compiler works... yes
....
configure:
Please type 'make' to build Bullet |
|
I meant, what happens when you run
on this file: That is failing for some reason in the configure. Let's find out why. |
|
I trunk the build.py and try it. It's a clang bug for ubuntu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629861). emmaken.py: /opt/src/emscripten/tools/emmaken.py -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu -I/usr/include/i386-linux-gnu -I/usr/include/c$
['/opt/src/emscripten/tools/emmaken.py', '-I/usr/include/i386-linux-gnu', '-I/usr/include/c++/4.5/i686-linux-gnu', '-I/usr/include/i386-linux-gnu', '-I/usr/include/$
Running: /opt/src/llvm-2.9/bin/clang -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-linux-gnu -I/usr/include/i386-linux-gnu -I/usr/include/c++/4.5/i686-l$
/usr/bin/ld.bfd.real: cannot find crt1.o: No such file or directory
/usr/bin/ld.bfd.real: cannot find crti.o: No such file or directory
/usr/bin/ld.bfd.real: cannot find crtbegin.o: No such file or directory
/usr/bin/ld.bfd.real: cannot find -lgcc
/usr/bin/ld.bfd.real: cannot find -lgcc_s
clang: error: linker command failed with exit code 1 (use -v to see invocation)
configure:3324: $? = 1
configure:3362: result: no |
|
Interesting. You might need to get upstream clang and build it then. (Or, just use llvm-gcc and not clang.) |
|
this issue has not been fixed in trunk. so only llvm-gcc instead. :( |
tlively
pushed a commit
to tlively/emscripten
that referenced
this issue
Mar 23, 2022
Cleaned SQLite test code
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
emscripten latest git version
The text was updated successfully, but these errors were encountered: