From: Markos Chandras <markos.chandras@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: Set default emulation for MIPS64/MIPS64el n64
Date: Sat, 18 May 2013 18:58:51 +0100 [thread overview]
Message-ID: <5197C15B.6000601@gmail.com> (raw)
In-Reply-To: <20130518193129.47c18aba@skate>
On 05/18/2013 06:31 PM, Thomas Petazzoni wrote:
> Dear Markos Chandras,
>
> On Fri, 17 May 2013 20:42:40 +0100, Markos Chandras wrote:
>> From: Markos Chandras <markos.chandras@imgtec.com>
>>
>> binutils set the default emulation for MIPS64/MIPS64el to
>> elf32btsmipn32 and elf32ltsmipn3 respectively. This breaks
>> linking for programs calling the linker directly without passing
>> the appropriate emulation parameter (-m). Unfortunately,
>> binutils do not provide a way to set the default emulation when
>> building the linker therefore we export the LDEMULATION variable
>> to set the preferred emulation ourselves. This fixes
>>
>> http://autobuild.buildroot.net/results/0f2a760b94069ac915d856cd1ae1998e5483807a/
>>
>> and possibly other build failures as well.
>
> I am not sure this is the right fix for the problem. I believe the
> problem is that the external toolchain wrapper should also wrap "ld" in
> order to pass the right arguments to select the correct emulation, just
> like we have a wrapper for "gcc" to select the correct architecture,
> ABI and so on.
>
> No?
>
> Thomas
>
Hi Thomas,
I am not sure what you mean by "external toolchain" here since this is a
problem with the buildroot toolchain as well. I probably don't
understand the solution you propose. This is a "quick and dirty" fix.
The ideal solution to this problem would be to fix the build systems to
use "gcc" instead of "ld" for linking.
--
Regards,
Markos Chandras
prev parent reply other threads:[~2013-05-18 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 19:42 [Buildroot] [PATCH] Makefile: Set default emulation for MIPS64/MIPS64el n64 Markos Chandras
2013-05-18 17:31 ` Thomas Petazzoni
2013-05-18 17:58 ` Markos Chandras [this message]
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=5197C15B.6000601@gmail.com \
--to=markos.chandras@gmail.com \
--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.