Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-02-26
Date: Mon, 27 Feb 2017 21:20:49 +0100	[thread overview]
Message-ID: <20170227212049.035b8d71@free-electrons.com> (raw)
In-Reply-To: <CA+-urNQUEmsQy2_8UcL5FQqq10O-nQjNUY_nxwcD8mHxCtW2tw@mail.gmail.com>

Hello,

On Mon, 27 Feb 2017 11:54:19 -0500, Frank Hunleth wrote:

> >>         i686 |              rabbitmq-c-v0.8.0 | NOK | http://autobuild.buildroot.net/results/92f9a6b804072a521ad0b25086a0a5ed33eaf53e
> >>          arc |              rabbitmq-c-v0.8.0 | NOK | http://autobuild.buildroot.net/results/a04ba24c6cd61bf6f2128a0e869f679cb3f2eac3  
> >
> > Static linking issues, with a CMake based package. Frank, Samuel, could
> > you have a look?
> >  
> 
> I took a quick look. The issue is due to a transitive dependency on
> zlib not being added to the linker invocation. The rabbitmq utilities
> make calls to libcrypto.a which has calls to zlib. I don't use cmake
> enough to know how this is normally fixed with that tool. If there's
> another example somewhere that I can copy, I don't mind submitting a
> fix.

The proper solution for this is to use pkg-config to discover the
libraries. pkg-config has the relevant information about transitive
dependencies that are needed for static linking to work properly.

It is worth noting that the problem does not occur only with
openssl->zlib, but also with libintl.

> p.s. Fwiw, rabbitmq-c is actually maintained by Joris Lijssens, so I'm
> adding him to the cc list in case he has run into this. My rabbitmq
> package is rabbitmq-server, but my project with rabbit also uses
> rabbitmq-c.

Ah, yes, indeed, my bad. Thanks for adding Joris in the loop then. He
should anyway have received notifications of the build failures.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-02-27 20:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-26 Thomas Petazzoni
2017-02-27 13:28 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-27 15:54   ` Yann E. MORIN
2017-02-27 15:57     ` Thomas Petazzoni
2017-02-27 16:54   ` Frank Hunleth
2017-02-27 20:20     ` Thomas Petazzoni [this message]
2017-02-27 22:38   ` [Buildroot] Analysis of build results for 2017-02-26: libsidplay issue on PowerPC64 Thomas Petazzoni
2017-02-28  0:41     ` Sam Bobroff
2017-02-27 22:38   ` [Buildroot] Analysis of build results for 2017-02-26: classpath issue Thomas Petazzoni
2017-02-27 23:01   ` [Buildroot] Analysis of build results for 2017-02-26: librsvg failure Thomas Petazzoni
2017-02-28  9:00     ` Peter Korsgaard
2017-02-28  9:05       ` Thomas Petazzoni
2017-02-28 14:16         ` Thomas Petazzoni
2017-02-28 14:48         ` Peter Korsgaard
2017-02-28 15:37           ` Thomas Petazzoni
2017-02-28 16:10             ` Peter Korsgaard
2017-02-28 15:34   ` [Buildroot] Analysis of build results for 2017-02-26 Vlad Zakharov
2017-02-28 16:02     ` 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=20170227212049.035b8d71@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