From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External Toolchain: Calculation of SYSROOT_DIR in toolchain/toolchain-external/ext-tool.mk wrong?
Date: Wed, 1 Feb 2012 14:01:55 +0100 [thread overview]
Message-ID: <20120201140155.67edc41c@skate> (raw)
In-Reply-To: <4666169C600DD24C84F509DC90790D5007629FD4B9@DEMCHP99E75MSX.ww902.siemens.net>
Le Wed, 1 Feb 2012 13:30:01 +0100,
"Warlich, Christof" <christof.warlich@siemens.com> a ?crit :
> I fully agree with you, but when I talked about the amount of effort, I
> was referring to the effort that it would take me to convince management
> to give away that code. I know from earlier experience how much (useless)
> energy that may take.
Ok. Do your management realize that a toolchain is mostly composed of
gcc, binutils, uClibc and gdb, that all of these are distributed under
GPL or LGPL licenses, and therefore you have to keep the source code
open for those components in order to comply with their licenses?
> Considering the hard and good work that you guys are offering for free,
> all I can do for now is to sincerely apologize. I would however certainly
> be willing to discuss and test any more generic patch if you are still
> Interested to put further work into the issue despite the unpleasent
> circunstances.
>
> Again, sorry for not being as helpful as I would like to be,
Can you try:
sed -r -e 's:(usr/)?lib/libc\.a::'
This will make the usr/ part at the beginning optional. It seems to do
the job here:
thomas at skate:~$ echo "foo/bar/test/lib/libc.a" | sed -r -e 's:(usr/)?lib/libc\.a::'
foo/bar/test/
thomas at skate:~$ echo "foo/bar/test/usr/lib/libc.a" | sed -r -e 's:(usr/)?lib/libc\.a::'
foo/bar/test/
If you just make that change, does all the rest of the external
toolchain logic works for you?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-02-01 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 8:35 [Buildroot] External Toolchain: Calculation of SYSROOT_DIR in toolchain/toolchain-external/ext-tool.mk wrong? Warlich, Christof
2012-02-01 9:38 ` Thomas Petazzoni
2012-02-01 11:20 ` Warlich, Christof
2012-02-01 11:34 ` Thomas Petazzoni
2012-02-01 12:30 ` Warlich, Christof
2012-02-01 13:01 ` Thomas Petazzoni [this message]
2012-02-01 15:15 ` Grant Edwards
2012-02-01 15:48 ` Warlich, Christof
2012-02-01 15:25 ` Warlich, Christof
2012-02-01 16:16 ` Michael S. Zick
2012-02-01 15:05 ` Thomas De Schampheleire
2012-02-01 15:41 ` Warlich, Christof
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=20120201140155.67edc41c@skate \
--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