From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] musl with kernel headers
Date: Sun, 6 Nov 2016 02:25:08 +0100 [thread overview]
Message-ID: <1ee19442-01c1-9500-01c5-c0b056ee85a3@mind.be> (raw)
In-Reply-To: <20161105224934.gwj7wzqawxnovgzs@tarshish>
On 05-11-16 23:49, Baruch Siach wrote:
> Hi Thomas,
>
> On Fri, Nov 04, 2016 at 09:16:39AM +0100, Thomas Petazzoni wrote:
>> 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 :-)
>
> Of course.
>
>> However, you could have it as post-install staging hook of the
>> toolchain virtual package I guess.
>
> I experimented with TOOLCHAIN_POST_INSTALL_STAGING_HOOKS, but these hooks
> never run. TOOLCHAIN_EXTERNAL_POST_INSTALL_STAGING_HOOKS work as expected, but
> it's limited to external toolchains. What would be the right approach?
The toolchain virtual package doesn't install to staging. Just add
TOOLCHAIN_INSTALL_STAGING = YES
Regards,
Arnout
>
> baruch
>
--
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
prev parent reply other threads:[~2016-11-06 1:25 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
2016-11-05 22:49 ` Baruch Siach
2016-11-06 1:25 ` Arnout Vandecappelle [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=1ee19442-01c1-9500-01c5-c0b056ee85a3@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.