[ELDK] Building ELDK 4.2 for MIPS
Gianni
nasus.maximos at gmail.com
Thu Mar 12 00:29:10 CET 2009
Dear Wolfgang,
On Wednesday 11 March 2009 17:27:16 Wolfgang Denk wrote:
> You know - it's a wiki - you could fix all these deficiencies
> yourself...
OK, I'll fix what I from now on. I just don't want to do anything before I am
sure what I am doing.
> > I also had to add an extra option in
> > eldk-4.2/build/cross_rpms/crosstool/SPECS/crosstool.spec at line 332:
> >
> > BINUTILS_EXTRA_CONFIG="--disable-werror"
> > export BINUTILS_EXTRA_CONFIG
> >
> > because I was getting a gcc warning that caused the build to fail. Maybe
> > this is because I had the 'wrong' distribution/gcc?
>
> Probably.
No luck. I repeated the process and got the same errors. I had to edit the
crosstool.spec file again to add the option mentioned above, and then after
restarting I got the same error:
checking for assembler global-symbol directive... .globl
checking for .set assembler directive... no
checking for assembler .type directive prefix... @
checking for .symver assembler directive... yes
checking for ld --version-script... no
*** WARNING: You should not compile GNU libc without versioning. Not using
*** versioning will introduce incompatibilities so that old binaries
*** will not run anymore.
*** For versioning you need recent binutils (binutils-2.8.1.0.23 or newer).
checking for .previous assembler directive... yes
checking for .protected and .hidden assembler directive... yes
checking whether __attribute__((visibility())) is supported... yes
checking for broken __attribute__((visibility()))... no
checking for broken __attribute__((alias()))... no
checking whether to put _rtld_local into .sdata section... yes
checking for .preinit_array/.init_array/.fini_array support... no
configure: error: Need linker with .init_array/.fini_array support.
error: Bad exit status from
/opt/eldk-4.2/build/mips-2009-03-11/work/var/tmp/rpm-tmp.31526 (%build)
I've uploaded the whole log file to:
http://64.22.74.205/build_crosstool.log.gz
in case it helps. It seems that the error is produced by the 'ld' that was
built by ELDK itself.
Any ideas?
Thanks.
More information about the eldk
mailing list