From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] musl with kernel headers (was: [PATCH] bridge-utils: fix build with musl)
Date: Fri, 4 Nov 2016 09:16:39 +0100 [thread overview]
Message-ID: <20161104091639.1a0285c4@free-electrons.com> (raw)
In-Reply-To: <20161104052244.c2qswgkglbwcod3a@tarshish>
Hello,
On Fri, 4 Nov 2016 07:22:44 +0200, Baruch Siach wrote:
> > Yes, we probably need to do something like that. I'm sick of all the
> > patches we need to fix this structure redefinition mess, so if we have
> > a global solution, it would be nice. I guess it needs to be applied in
> > both the linux-headers package and the toolchain-external package.
>
> I was thinking if a sed call in TOOLCHAIN_TARGET_FINALIZE_HOOKS to simplify
> the hack. Would that work?
No, because FINALIZE_HOOKS, like their name suggests, are called at the
very end of the build, after all packages have been built, and right
before we create the filesystem images.
So to fix something that helps in building packages, it's a little bit
too late :-)
However, you could have it as post-install staging hook of the
toolchain virtual package I guess.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-04 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 5:53 [Buildroot] [PATCH] bridge-utils: fix build with musl Baruch Siach
2016-11-03 21:46 ` Thomas Petazzoni
2016-11-04 5:22 ` [Buildroot] musl with kernel headers (was: [PATCH] bridge-utils: fix build with musl) Baruch Siach
2016-11-04 8:16 ` Thomas Petazzoni [this message]
2016-11-05 22:49 ` Baruch Siach
2016-11-06 1:25 ` [Buildroot] musl with kernel headers 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=20161104091639.1a0285c4@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