On 28/02/12 00:38, Ron wrote:
I haven't had success with compiling the native compiler with trunk
4.6 or 4.1.2Release1. Starting with a Mint9(10.04) home empty of
gccsdk I am doing

#!/bin/bash cd ~/ sudo apt-get -y install subversion m4 libtool bison
autogen texinfo help2man \ automake1.7 cvs dpkg-dev libglib2.0-dev
liborbit2-dev rman autoconf2.13 \ gperf gettext intltool libpopt-dev
policykit realpath doxygen svn co
svn://svn.riscos.info/gccsdk/branches/release_4_1_2 gccsdk/gcc4 cd
gccsdk/gcc4 ./build-world ./build-world make ronative
./create-gcckit

And copying the kit to a Moonfish mount for the ,xxx translations
rather that zipping, which requires autobuilder and doesn't seem to
improve things any.

It is possible to check out autobuilder separately alongside GCC 4.1.2
if you with to use that version of GCC. From the parent directory of
gcc4, use:

svn co svn://svn.riscos.info/gccsdk/trunk/autobuilder

Alternatively, if you already have autobuilder set up somewhere else and
have built native-zip there, you can copy the binary
"gcc4/../env/bin/zip" from one GCCSDK to another.

I reboot after moving out my old !SharedLibs from Boot:Resources, and
Click on the new !SharedLibs and the new Sharedulib module that is
part of the new kit.

Set Dir to Examples.C and the result from gcc helloworld.c

is

/tmp/cco1Zetb.s: Assembler messages: /tmp/cco1Zetb.s:31: Fatal error: can't 
write /tmp/ccEefv84.o: Value too large for defined data type
/ADFS::HardDisc4.$/gcc412/gccsdk-gcc-core-bin-4.1.2-Rel1dev/!GCC/bin/as:
BFD (GCCSDK GCC 4.1.2 Release 1 Development) 2.21 assertion fail
/home/ron/gccsdk/gcc4/srcdir/binutils/bfd/elf.c:2495
/tmp/cco1Zetb.s:31: Fatal error: can't close /tmp/ccEefv84.o: Value too large 
for defined data type *

Yes, this is a minor bug in UnixLib - it was fixed in trunk, but slipped
through the net for 4.1.2. I've just committed a fix for it, so it
should work now.

I think I have done everything to ensure a standard clean build
here. My earlier (download) of GCC4.1.2 Testing and Libs/modules
works OK.

HTH,
Lee.

_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Reply via email to