Build fail on ARM TS-7260 (Debian "Sarge" 3.1)

[TooTallNate]

Hello, I am trying to compile V8 standalone on a Technologic TS-7260
single board computer. I've opened up this same message in V8's
Issue's section from Google Code (http://code.google.com/p/v8/issues/
detail?id=740), but I think a lot more eyes see the mailing list, so I
thought I'd try and post it here as well, since I hope to get this
working ASAP since it's for work and my boss is breathing down my neck
on this now...

So the TS-7260 is running a pretty old version of Debian ("Sarge",
3.1) with the 2.4 kernel.

When I check out V8's source, and run 'scons' without any arguments,
it compiles a few source files without any errors/warnings, but fails
after a few with an error message like this:

g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
scons: *** [obj/release/arm/codegen-arm.o] Error 1
scons: building terminated because of errors.


Needless to say I can't get any further than this. Here's the output
of some hopefully helpful info regarding my linux setup:

cat /etc/debian_version
3.1 Sarge

uname -a
Linux ts7260 2.4.26-ts11 #3 Fri Apr 23 18:53:38 PDT 2010 armv4l
GNU/Linux

scons --version
SCons by Steven Knight et al.:
script: v2.0.0.final.0.r5023, 2010/06/14 22:05:46, by scons on
scons-dev
engine: v2.0.0.final.0.r5023, 2010/06/14 22:05:46, by scons on
scons-dev

gcc -v
Using built-in specs.
Target: arm-linux
Configured with: ../src/configure -v --enable-languages=c,c++ --
prefix=/usr --enable-shared --enable-__cxa_atexit --with-system-zlib --
enable-nls --without-included-gettext --enable-clocale=gnu --enable-
debug --program-suffix=-4.0.4 arm-linux
Thread model: posix
gcc version 4.0.4

g++ -v
Using built-in specs.
Target: arm-linux
Configured with: ../src/configure -v --enable-languages=c,c++ --
prefix=/usr --enable-shared --enable-__cxa_atexit --with-system-zlib --
enable-nls --without-included-gettext --enable-clocale=gnu --enable-
debug --program-suffix=-4.0.4 arm-linux
Thread model: posix
gcc version 4.0.4

Thanks for anything in advance!

[Stephan Beal]

On Thu, Jun 17, 2010 at 9:08 PM, TooTallNate <nat...@tootallnate.net> wrote:

   g++: Internal error: Killed (program cc1plus)
   Please submit a full bug report.
   See <URL:http://gcc.gnu.org/bugs.html> for instructions.
   scons: *** [obj/release/arm/codegen-arm.o] Error 1
   scons: building terminated because of errors.

Just out of curiosity: were you building in debug mode? There were several versions of gcc 4.0.x which could throw an internal error when certain code was compiled in debug mode. i remember having the problem when comping the SpiderMonkey JS engine some years back (2005, i think), and had to explicitly disable debug mode for 4.0.x compilers to get around it. Something to try, anyway.

--
----- stephan beal
http://wanderinghorse.net/home/stephan/

[Vyacheslav Egorov]

Nathan, 

How much RAM does Technologic TS-7260 have onboard? 64 MB? This is not enough for g++ compiler. You should try cross-compiling V8 instead. 

There is also a slight possibility that V8 source is just triggering a bug in g++. In this case you should report it directly to GCC folks.

--
Vyacheslav Egorov

On Thu, Jun 17, 2010 at 9:08 PM, TooTallNate <nat...@tootallnate.net> wrote:

--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users

[TooTallNate]

Shoot, I'm starting to feel that the machine might indeed be running
out of memory. First I tried building GCC 4.5.0 (the latest as of
now). And it gave me a similar error while compiling V8:

g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

So I thought 4.5.0 might be too new. Then I tried 4.3.3 (just because
it was the version with all my Ubuntu installs, so I knew it would be
able to compile V8 at least). Unfortunately, I got the same error
after about an hour. So then it was 1am and I was tired and just
wanted some success in the day, so I reverted back to compiling 4.0.4,
which I had done successfully earlier.

So the 4.0.4 'make' step just finished successfully or so it seems.
I'm taking an image of the SD card before doing a 'make install'
possibly to also try and do a checkinstall to make a reusable .deb out
of this. Now my final hope is that this 4.0.4 build will be able to
build something higher (possibly 4.3.3) and finally build V8.

However I'm also starting to fear that there might be a memory issue
as stated earlier. Any ideas why 4.0.4 was able to build if that's the
case? Just because it's a smaller release?

Also, if it does turn out to be a memory issue, then my only other
option would be to cross-compile it from another computer right? Any
good articles about how to do that for V8? Thanks guys!