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: add a harmless link when sysroot detection is not accurate
Date: Fri, 22 Jan 2016 14:15:47 +0100	[thread overview]
Message-ID: <20160122141547.6fe95d7d@free-electrons.com> (raw)
In-Reply-To: <1453464862-33174-1-git-send-email-Vincent.Riera@imgtec.com>

Dear Vicente Olivert Riera,

On Fri, 22 Jan 2016 12:14:22 +0000, Vicente Olivert Riera wrote:
> Sometimes is not possible to detect if the sysroots are nested or side
> by side. For instance this happens for MIPS big endian, where the
> sysroot and the arch-sysroot directories are the same.
> 
> For those cases where the sysroot detection is not accurate we add a
> harmless symlink necessary for certain toolchains.
> 
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

Gaah, even more magic in this code.

Can you update the comment above the function, and also in the commit
log explain which toolchain is affected, and give outputs of
-print-file-name that explain the problem ?

It is really important to document all those things, because we
progressively adjust this sorcery to accommodate all toolchains, but
when we'll want to refactor this stuff, it will be very useful to have
some explanation as to why each case was handled this way.

The more I look at this external toolchain mess, the more I think we
should have less magic, and simply for each toolchain have some
explicit code in BR that says "this toolchain is organized this way".
Yes, it means that we will no longer automagically accommodate to
custom external toolchains...

Best regards,

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

      reply	other threads:[~2016-01-22 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 12:14 [Buildroot] [PATCH] toolchain: add a harmless link when sysroot detection is not accurate Vicente Olivert Riera
2016-01-22 13:15 ` 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=20160122141547.6fe95d7d@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