All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
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 11:05:38 +0200	[thread overview]
Message-ID: <55A62262.1090304@mind.be> (raw)
In-Reply-To: <20150715105950.42ac4b53@free-electrons.com>

On 07/15/15 10:59, Thomas Petazzoni wrote:
> 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.

 Just to be clear: for me this is a bikeshedding discussion. Neither is right,
so just go for one.

 BTW, yesterday I did ask everyone in Toulouse if it would be OK have add to the
gcc-final hook from toolchain-buildroot.mk, and nobody really opposed (though I
don't think you really said anything, ThomasP).

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-07-15  9:05 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
2015-07-15  9:05       ` Arnout Vandecappelle [this message]
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=55A62262.1090304@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 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.