zinonet / naclports

Automatically exported from code.google.com/p/naclports
0 stars 0 forks source link

Build of naclport on linux 64-bit - Update to Readme file to avoid #129

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Note: Issue discovered while working with [kestert@google.com] during the SciPy 
2014 sprint

You will find enclosed a patch to apply to the Readme file

What steps will reproduce the problem?
1. Build naclport on Linux 64bit

// -----
NACL_SDK_ROOT=/home/jchris/Projects/nacl_sdk/pepper_canary/ NACL_ARCH=pnacl 
TOOLCHAIN=pnacl make python-host
// -----

What is the expected output? 

// -----
bin/naclports install python-ppapi 
Building 'glibc-compat' [pnacl/newlib/release]
Build complete 'glibc-compat' [pnacl/newlib/release] [took 1s]
Installing 'glibc-compat' [pnacl/newlib/release]
Building 'ncurses' [pnacl/newlib/release]
Build complete 'ncurses' [pnacl/newlib/release] [took 2m]
Installing 'ncurses' [pnacl/newlib/release]
Building 'readline' [pnacl/newlib/release]
Build complete 'readline' [pnacl/newlib/release] [took 37s]
Installing 'readline' [pnacl/newlib/release]
Building 'zlib' [pnacl/newlib/release]
Build complete 'zlib' [pnacl/newlib/release] [took 19s]
Installing 'zlib' [pnacl/newlib/release]
Building 'python' [pnacl/newlib/release]
Build complete 'python' [pnacl/newlib/release] [took 6m]
Installing 'python' [pnacl/newlib/release]
Building 'libtar' [pnacl/newlib/release]
Build complete 'libtar' [pnacl/newlib/release] [took 16s]
Installing 'libtar' [pnacl/newlib/release]
Building 'nacl-spawn' [pnacl/newlib/release]
Build complete 'nacl-spawn' [pnacl/newlib/release] [took 2s]
Installing 'nacl-spawn' [pnacl/newlib/release]
Building 'python-ppapi' [pnacl/newlib/release]
[...]
// -----

What do you see instead?

// -------------------------------------------------------
######################################################################
Building glibc-compat
######################################################################
chdir /path/to/naclports-read-only/src/out/build/glibc-compat/glibc-compat-0.1
make -j8
make[1]: Entering directory 
`/path/to/naclports-read-only/src/out/build/glibc-compat/glibc-compat-0.1'
 CC out/getprotobyname_r.o
 CC out/getservbyname_r.o
 CC out/herrno.o
 CC out/in6_addr.o
 CC out/inet_addr.o
 CC out/inet_pton.o
 CC out/ns_name.o
 CC out/ns_netint.o
/path/to/nacl_sdk/pepper_canary/toolchain/linux_pnacl/host_x86_32/bin/clang: 
error while loading shared libraries: libstdc++.so.6: cannot open shared object 
file: No such file or directory
/path/to/nacl_sdk/pepper_canary/toolchain/linux_pnacl/host_x86_32/bin/clang: 
error while loading shared libraries: libstdc++.so.6: cannot open shared object 
file: No such file or directory
/path/to/nacl_sdk/pepper_canary/toolchain/linux_pnacl/host_x86_32/bin/clang: 
error while loading shared libraries: libstdc++.so.6: cannot open shared object 
file: No such file or directory
/path/to/nacl_sdk/pepper_canary/toolchain/linux_pnacl/host_x86_32/bin/clang: 
error while loading shared libraries: libstdc++.so.6: cannot open shared object 
file: No such file or directory
/path/to/nacl_sdk/pepper_canary/toolchain/linux_pnacl/host_x86_32/bin/clang: 
error while loading shared libraries: libstdc++.so.6: cannot open shared object 
file: No such file or directory
/path/to/nacl_sdk/pepper_canary/toolchain/linux_pnacl/host_x86_32/bin/clang: 
error while loading shared libraries: libstdc++.so.6: cannot open shared object 
file: No such file or directory
make[1]: *** [out/in6_addr.o] Error 127
make[1]: *** Waiting for unfinished jobs....
[...]
// -------------------------------------------------------

What version of the product are you using? On what operating system?

pepper_canary
naclport @ r1426

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 13.10
Release:    13.10
Codename:   saucy

Original issue reported on code.google.com by jchris.f...@kitware.com on 11 Jul 2014 at 9:49

Attachments:

GoogleCodeExporter commented 9 years ago
The pnacl toolchain now uses its own internal version of libc++ so this should 
no longer be and issue.  

Original comment by sbc@google.com on 30 Sep 2014 at 7:18