Trying to install Crystax from script

221 views
Skip to first unread message

David Creelman

unread,
Nov 8, 2016, 4:50:43 AM11/8/16
to crystax-ndk
Hi,
I've downloaded ndk-crystax-r10-build.sh and tried running it...
However, I get the following error :-

Building linux-x86_64 toolchain for arm architecture: arm-linux-androideabi-4.9
ERROR: Could not build arm-linux-androideabi-4.9-linux-x86_64!
ERROR: Could not build host prebuilts in 64-bit!
ERROR: Can't build  binaries.

I'm not running as root, do I need  to?
Any other clues as to what might be going on here?
Thanks,
David

Dmitry Moskalchuk

unread,
Nov 8, 2016, 6:13:01 AM11/8/16
to cryst...@googlegroups.com
Hi David,

Most likely it happens because you haven't installed some package needed for build (like texinfo or others). To be more specific, I'd like to see end of build log. You can find it in /tmp/ndk-$USER/build.log - please cut last several tens lines from it and post here.

-- 
Dmitry Moskalchuk
--
You received this message because you are subscribed to the Google Groups "crystax-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystax-ndk...@googlegroups.com.
To post to this group, send email to cryst...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystax-ndk.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystax-ndk/03376232-4048-49a3-bad7-d90ccdb0f917%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Creelman

unread,
Nov 8, 2016, 8:42:22 PM11/8/16
to crystax-ndk
Hi Dmitry,
Here is my log...

/tmp/crystax-ndk-sources-root/platform/ndk/../prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/bin/x86_64-linux-g++ -DHAVE_CONF
IG_H -I. -I/tmp/crystax-ndk-sources-root/toolchain/build/../binutils/binutils-2.25/gold  -I/tmp/crystax-ndk-sources-root/toolchain/bui
ld/../binutils/binutils-2.25/gold -I/tmp/crystax-ndk-sources-root/toolchain/build/../binutils/binutils-2.25/gold/../include -I/tmp/cry
stax-ndk-sources-root/toolchain/build/../binutils/binutils-2.25/gold/../elfcpp -DLOCALEDIR="\"/tmp/ndk-root/build/toolchain/prefix/sha
re/locale\"" -DBINDIR="\"/tmp/ndk-root/build/toolchain/prefix/bin\"" -DTOOLBINDIR="\"/tmp/ndk-root/build/toolchain/prefix/arm-linux-an
droideabi/bin\"" -DTOOLLIBDIR="\"/tmp/ndk-root/build/toolchain/prefix/arm-linux-androideabi/lib\""   -W -Wall    -D_LARGEFILE_SOURCE -
D_FILE_OFFSET_BITS=64 -frandom-seed=output.o -g -O2 -MT output.o -MD -MP -MF .deps/output.Tpo -c -o output.o /tmp/crystax-ndk-sources-
root/toolchain/build/../binutils/binutils-2.25/gold/output.cc
x86_64-linux-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Makefile:842: recipe for target 'object.o' failed
make[5]: *** [object.o] Error 4
make[5]: *** Waiting for unfinished jobs....
mv -f .deps/output.Tpo .deps/output.Po
make[5]: Leaving directory '/tmp/ndk-root/build/toolchain/binutils-2.25/gold'
Makefile:865: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/tmp/ndk-root/build/toolchain/binutils-2.25/gold'
Makefile:616: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/tmp/ndk-root/build/toolchain/binutils-2.25/gold'
Makefile:6072: recipe for target 'all-gold' failed
make[2]: *** [all-gold] Error 2
make[2]: Leaving directory '/tmp/ndk-root/build/toolchain/binutils-2.25'
Makefile:832: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/tmp/ndk-root/build/toolchain/binutils-2.25'
Makefile:342: recipe for target 'stmp-build-target-binutils' failed
make: *** [stmp-build-target-binutils] Error 2
Error while building toolchain. See /tmp/ndk-root/build.log
ERROR: Could not build arm-linux-androideabi-5-linux-x86_64!
ERROR: Could not build host prebuilts in 64-bit!
ERROR: Can't build  binaries.

Hmm, looks like the compiler fell over?
Regards,
David

Dmitry Moskalchuk

unread,
Nov 9, 2016, 6:35:41 AM11/9/16
to cryst...@googlegroups.com
Hi David,

Hmm, this is bug in host compiler (one located at /tmp/crystax-ndk-sources-root/platform/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/bin/x86_64-linux-g++). This is strange though, since we're using the same compiler for daily builds of CrystaX NDK, and haven't observing any problems with it. As a temporary workaround I'd suggest to remove whole folder /tmp/crystax-ndk-sources-root/platform/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8 and edit ndk-crystax-r10-build.sh to prevent it fetching this repository again. Then just run build script as usual - it will detect that there is no own prebuilt gcc on a machine and will use system one (of course, you have to install x86_64 gcc to system first).

Also, I'd like to figure out what's wrong in your case, that causing such bug, whereas everything works fine in our build environment. Could you please share more details on what you're doing exactly, on what operating system, etc? I'd like to be able to reproduce the problem to get it fixed.

-- 
Dmitry Moskalchuk

David Creelman

unread,
Nov 10, 2016, 6:21:24 AM11/10/16
to cryst...@googlegroups.com
Hi Dmitry,
I've in fact decided to simply download the prebuilt tools for 64 bit. I was a bit surprised that the compiler crashed too.

I'm on a Hyper-V Linux Devuan, 64bit with 2G memory, 200Gb HD. If I get time I'll try following what you suggested, but I'm under a bit of a time deadline at the moment. Thanks for getting back to me.

Regards,
David

Dmitry Moskalchuk

unread,
Nov 10, 2016, 6:29:47 AM11/10/16
to cryst...@googlegroups.com
Hi David,

I guess this happened because of small amount of RAM (yes, 2G of memory might not be enough for compiler nowadays!). However, I'm not sure. This is only my guess.

Our build machines have 16G of RAM, and we don't experience any problems with builds. I'll try later to build everything on virtual machine with 2G of RAM, but can't guarantee that will be soon.

Practically - yes, the best solution would be to just download prebuilt tools instead of trying to build everything on your own.

-- 
Dmitry Moskalchuk
Reply all
Reply to author
Forward
0 new messages