Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Passing arguments to the linker when external toolchain is used.
Date: Mon, 26 Nov 2012 23:33:19 +0100	[thread overview]
Message-ID: <50B3EE2F.2020901@mind.be> (raw)
In-Reply-To: <CAMJ=MEcN43B=aMbLGcG4dwMGXf5dq0Reu-qBe_UEhuDi3O13Rw@mail.gmail.com>

On 26/11/12 21:45, Ronny Meeus wrote:
>> >    I don't think we have any other architecture currently in buildroot that
>> >  requires something to be passed to ld. If this wrapper construction is
>> >  added to buildroot, it would be good if we would also have an internal
>> >  use case.
>> >
> I do not really understand. On one hand you say it is a valid use-case
> and on the other hand you say that an internal use-case is needed.

  If ld requires some architecture specific flag to work, then it's a valid
use case to add this in the wrapper. (However, I now realize that this
would only work for external toolchains...  For internal and crosstool-NG
toolchains, we don't have a wrapper and it's not needed because those
things are hard-coded at compile time. So how would you deal with that for
this ld case?)

  But it would improve acceptance if there were also a use case inside
buildroot. I tried to find a package that would also require the additional
LD flag, but it seems that most packages that do partial linking use
$(CC) -nostdlib.

> Shall I put some more effort in generalising the C code of the
> wrapper?
> Is there any chance that it gets accepted by the community?

  If you can show a .config that fails to build without it: certainly.
Otherwise, it depends on how hard you push it :-)

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-11-26 22:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 13:04 [Buildroot] Passing arguments to the linker when external toolchain is used Ronny Meeus
2012-11-24 23:33 ` Arnout Vandecappelle
2012-11-25 17:23   ` Ronny Meeus
2012-11-25 20:44     ` Arnout Vandecappelle
2012-11-25 20:56       ` Ronny Meeus
2012-11-25 22:25         ` Arnout Vandecappelle
2012-11-26 20:45           ` Ronny Meeus
2012-11-26 22:33             ` Arnout Vandecappelle [this message]
2012-11-28 19:38               ` Ronny Meeus

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=50B3EE2F.2020901@mind.be \
    --to=arnout@mind.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox