Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Use the correct target name
Date: Sun, 18 Jan 2015 17:27:37 +0100	[thread overview]
Message-ID: <20150118172737.46ef9c70@free-electrons.com> (raw)
In-Reply-To: <54BBAAD7.3040207@dawncrow.de>

Dear Andr? Hentschel,

On Sun, 18 Jan 2015 13:45:11 +0100, Andr? Hentschel wrote:

> This was based on the irc discussion (14.01.2015):
> (20:49:23) kos_tom: Andre_H: well, I'm not happy with the BR2_TOOLCHAIN_BUILDROOT dependency
> (20:49:40) kos_tom: Andre_H: we normally don't accept packages that would not build with external toolchains.
> (20:55:05) Andre_H: kos_tom: we either need symbolic links for the external toolchain, so that the name fits the tupel, or we need to pass the external tupel. i guess the first strategy is more foolproof. what do you think about it?
> (20:56:13) kos_tom: nope, we want the second strategy: a way to pass the prefix of the toolchain.
> 
> I guess you missed my suggestion (16.01.2015):
> (19:55:51) Andre_H: kos_tom: hi, what about redoing my wine makefile and doing it as a generic package with special configure rules?
> (22:19:17) kos_tom: Andre_H: which special configure rules would solve the problem?
> (22:19:50) kos_tom: iamb: you can do whatever sort of target filesystem changes in a post-build script.
> (23:07:31) Andre_H: kos_tom: e.g. passing BR2_TOOLCHAIN_EXTERNAL_PREFIX instead of GNU_TARGET_NAME if possible

I indeed missed your suggestion, sorry about that. And your patch is
doing it globally for all packages.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-01-18 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 22:48 [Buildroot] [PATCH] toolchain: Use the correct target name André Hentschel
2015-01-16  8:29 ` Thomas Petazzoni
2015-01-18 12:45   ` André Hentschel
2015-01-18 16:27     ` Thomas Petazzoni [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=20150118172737.46ef9c70@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox