Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/acpitool: needs threads, shared; unavailable for bfin
Date: Wed, 28 Sep 2016 18:37:28 +0200	[thread overview]
Message-ID: <20160928163728.GB3622@free.fr> (raw)
In-Reply-To: <87pono1sm8.fsf@dell.be.48ers.dk>

Peter, All,

On 2016-09-28 07:49 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> 
>  > acpitool requires threads.
>  > However, it does not check fo threads in its configure script, so
>  > forgets to link with -pthreads, so fails to build in static-only
>  > scenarii.
> 
>  > However, upstream has been dead for the past 7+ years now, so there is
>  > not much point trying to fix this. Besides, a system with ACPI is most
>  > probably a biggish system, so shared libs will probably be enabled, so
>  > we just require shared libs.
> 
>  > As for bfin, the cryptic configure failure:
>  >     configure: error: C++ compiler cannot create executables
> 
>  > is due to the order in which AC_PROG_CXX and AC_PROG_CC are called.
>  > Calling AC_PROG_CC first fixes this error message.
> 
> Didn't we conclude this was a toolchain issue?

I never said otherwise. I just said that doing so in acpitool's
configure.in would fix the C++ check.

>  > Since there's not many chances that a bfin board has ACPI, we just
>  > disable acpitool for bfin.
> 
> Agreed.
> 
>  > ---
>  > Changes v1 -> v2:
>  >   - add dependencies on threads and !static
> 
> You seem to have forgotten to actually do so?

No I did not. I just did forget to add the file before git --amend.

Damned... :-(

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-09-28 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 22:05 [Buildroot] [PATCH] package/acpitool: needs threads, shared; unavailable for bfin Yann E. MORIN
2016-09-28  5:49 ` Peter Korsgaard
2016-09-28 16:37   ` Yann E. MORIN [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-28 16:42 Yann E. MORIN
2016-09-28 20:13 ` Peter Korsgaard

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=20160928163728.GB3622@free.fr \
    --to=yann.morin.1998@free.fr \
    --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