All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Hunleth <fhunleth@troodon-software.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-05
Date: Sun, 7 Aug 2016 10:33:06 -0400	[thread overview]
Message-ID: <CA+-urNTtANeREZCA=Axuub2BHOyeov3_FMMroHt9MuMrk7U5GA@mail.gmail.com> (raw)
In-Reply-To: <20160807112654.7b520594@free-electrons.com>

Hi Thomas,

On Sun, Aug 7, 2016 at 5:26 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>>          arm |                    fwup-v0.8.0 | NOK | http://autobuild.buildroot.net/results/802b6d77e1b77b7c8fcb8f3b394cdabfd406de7a/
>
> libconfuse issue. I know Frank was working on this, we discussed it on
> IRC, but I can't recall the details. Frank?
>

Sorry for being quiet on this issue. I've been so busy at work that I
didn't make much progress after our IRC discussion.

I didn't look hard at the failure above, but it did look similar to
the others. The common thread in the previous failures was static
linking, libintl, and pthreads. There are two issues:

The first was that fwup wasn't using the pkgconfig information so when
libconfuse has a transitive dependency on libintl, libintl wasn't
being linked in and the autoconf test for libconfuse would fail.
That's fixed in fwup 0.8.1, so all that needs to be done is for the
version bump to be pulled into Buildroot. I haven't sent a patch
because of the second issue.

The second issue is that both libintl and libarchive depend on
pthreads, but don't list that dependency in their pkgconfig data.
libintl doesn't even have a .pc file. The pthreads dependency is a
little silly, since both libraries only use mutexes, but it causes
linker errors nonetheless. This is where I timed out. Is the answer to
make fwup depend on pthreads, fix libarchive, or fix libintl? I was
also surprised that other programs hadn't run into this issue as well,
so maybe there's another option out there. Any help on this would be
appreciated.

Frank

  parent reply	other threads:[~2016-08-07 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-05 Thomas Petazzoni
2016-08-07  9:26 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-07 11:46   ` Waldemar Brodkorb
2016-08-09 10:03     ` Thomas Petazzoni
2016-08-07 14:33   ` Frank Hunleth [this message]
2016-08-07 15:48   ` Samuel Martin
2016-08-09 14:15     ` Ben Boeckel
2016-08-17 21:18       ` Samuel Martin
2016-08-08 15:56   ` Vlad Zakharov
2016-08-08 20:34     ` Thomas Petazzoni
2016-08-11 10:43       ` Vlad Zakharov
2016-08-09 13:27   ` gwenhael.goavec
2016-08-09 13:41     ` 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='CA+-urNTtANeREZCA=Axuub2BHOyeov3_FMMroHt9MuMrk7U5GA@mail.gmail.com' \
    --to=fhunleth@troodon-software.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.