From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] acpica: new package
Date: Mon, 4 Jul 2016 15:52:38 +0200 [thread overview]
Message-ID: <c220f54e-db54-8929-b341-b2341385ef51@gmail.com> (raw)
In-Reply-To: <CAK4VdL0dXyheLx2LJusbfdJRD+3yYuEi7-E-cGruvB1178tKVg@mail.gmail.com>
Hi Erico,
Le 04/07/2016 ? 15:45, Erico Nunes a ?crit :
> Hello,
>
> On Sun, Jul 3, 2016 at 3:45 PM, Romain Naour <romain.naour@gmail.com> wrote:
>> Thanks to TARGET_CONFIGURE_OPTS, CC="$(TARGET_CC) should be removed...
>> But indeed if we do that it will use host compiler.
>>
>> To fix that we need to patch generate/unix/Makefile.config
>> -CC = gcc
>> +CC ?= gcc
>
> Thanks for re-reviewing!
> Yes indeed as the package resets CC in the Makefile, setting it in the
> environment via TARGET_CONFIGURE_OPTS won't be enough (I tried to
> explain that in the changelog after the commit message).
> In my opinion (agreeing with Arnout), in this case it is less bloaty
> to just pass it again in the arguments, rather than patching the
> package.
Ok, I haven't a strong opinion on this, you can keep it as is :)
Reviewed-by: Romain Naour <romain.naour@gmail.com>
Best regards,
Romain
>
> On Mon, Jul 4, 2016 at 3:33 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>> On Sun, 2016-07-03 at 12:45 +0200, Erico Nunes wrote:
>>> The ACPI Component Architecture (ACPICA) project provides an operating
>>> system (OS)-independent reference implementation of the Advanced
>>> Configuration and Power Interface Specification (ACPI).
>>>
>>> It contains tools such as acpidump, iasl, acpixtract, etc.
>>
>> Thank you for doing this!
>> Though in our case we need this as a host tool. Can you add support into
>> next version of the patch?
>
> Hi Andy.
>
> Thank you for the feedback!
> I think, though, that we would need to have some other target
> Buildroot target package depending on a host version of this one, in
> order to have it accepted with a host version. Otherwise it is an
> orphan host package. Or do we have a strong reason to have it enabled
> as a host package of its own (maybe adding a Config.in.host in this
> case)?
>
> Erico
>
next prev parent reply other threads:[~2016-07-04 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 10:45 [Buildroot] [PATCH v2 1/1] acpica: new package Erico Nunes
2016-07-03 13:45 ` Romain Naour
2016-07-04 7:33 ` Arnout Vandecappelle
2016-07-04 13:45 ` Erico Nunes
2016-07-04 13:52 ` Romain Naour [this message]
2016-07-04 14:04 ` Andy Shevchenko
2016-07-04 13:33 ` Andy Shevchenko
2016-07-04 13:41 ` Erico Nunes
2016-07-05 8:16 ` Thomas Petazzoni
2016-07-05 17:15 ` Thomas Petazzoni
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=c220f54e-db54-8929-b341-b2341385ef51@gmail.com \
--to=romain.naour@gmail.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 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.