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 1/1] toolchain: create symlink to 'lib' from ARCH_LIB_DIR iso fixed lib32/lib64
Date: Wed, 15 Jul 2015 10:59:50 +0200	[thread overview]
Message-ID: <20150715105950.42ac4b53@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LXzu+j-xV7nPx200Tj8NAt6x_yrOoOjiEJpZGrCUmkB9g@mail.gmail.com>

Hello,

On Wed, 15 Jul 2015 10:57:52 +0200, Thomas De Schampheleire wrote:

> Well that is part of the discussion: conceptually I believe that the
> symlink creation is part of the toolchain as a whole. It needs to be
> done before libc, but actually all remaining toolchain components will
> probably rely on it, and also the packages.
> By placing it in gcc-initial I believe it is pretty hidden.

It is also pretty hidden to put the hook for a given package outside of
this package .mk file.

> Moreover, suppose we add support for the llvm/clang compiler. For such
> toolchains, we'd also need the symbolic links, so that code would have
> to be duplicated...

I don't think trying to take llvm/clang into account really makes sense
here. It's probably going to be so much different than what we have
today that lots of things would have to be reworked anyway.

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

  reply	other threads:[~2015-07-15  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  8:39 [Buildroot] [PATCH 1/1] toolchain: create symlink to 'lib' from ARCH_LIB_DIR iso fixed lib32/lib64 Thomas De Schampheleire
2015-07-15  8:40 ` Thomas De Schampheleire
2015-07-15  8:55 ` Thomas Petazzoni
2015-07-15  8:57   ` Thomas De Schampheleire
2015-07-15  8:59     ` Thomas Petazzoni [this message]
2015-07-15  9:05       ` Arnout Vandecappelle
2015-07-15 10:08         ` Thomas De Schampheleire
2015-07-15 12:43           ` Arnout Vandecappelle
2015-07-15  8:59   ` Arnout Vandecappelle

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=20150715105950.42ac4b53@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