From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] 'ld' gives "unrecognised emulation mode" - ARM toolchain unbuildable ??
Date: Tue, 21 Nov 2006 19:19:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20061121T200844-447@post.gmane.org> (raw)
In-Reply-To: loom.20061102T152239-949@post.gmane.org
MikeW <mw_phil@...> writes:
>
> MikeW <mw_phil <at> ...> writes:
>
> > During building libgcc, I get the message
> > ->>
> > /home/fred/buildroot/build_arm_nofpu/staging_dir/
> > arm-linux-uclibcgnueabi/b in/ld: unrecognised emulation mode: armelf_linux
> > Supported emulations: armelf_linux_eabi
> > collect2: ld returned 1 exit status
> > make[3]: *** [libgcc/./_udivsi3.oS] Error 1
> > -<<
>
> Fixed by setting GNU target suffix to 'elf-linux' instead.
>
> Regards,
> MikeW
>
Except that objects created by the toolchain have EABI version = 0 !!
I need EABI version = 4 for compatibility :(
So that suggests that I need a target suffix containing '-eabi'.
Any ideas ?
I mean, where is this stuff documented - I've trawled through gcc docs
and not found anything that explains these problems.
I'm presumably not the only person to encounter this issue !
Mike
next prev parent reply other threads:[~2006-11-21 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 14:14 [Buildroot] 'ld' gives "unrecognised emulation mode" during make; gcc-3.4.3 MikeW
2006-11-02 12:09 ` [Buildroot] 'ld' gives "unrecognised emulation mode" - ARM toolchain unbuildable ?? MikeW
2006-11-02 18:01 ` [Buildroot] 'ld' gives MikeW
2006-11-21 19:19 ` MikeW [this message]
2006-11-21 20:08 ` [Buildroot] 'ld' gives "unrecognised emulation mode" - ARM toolchain unbuildable ?? Michael K. Edwards
2006-11-22 9:34 ` MikeW
2006-11-22 17:08 ` Michael K. Edwards
2006-11-29 14:58 ` MikeW
2006-11-29 15:06 ` [Buildroot] 'ld' gives MikeW
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20061121T200844-447@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.