All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] czmq: unbreak static linking
Date: Tue, 12 May 2015 21:30:31 +0200	[thread overview]
Message-ID: <87a8x9h9uw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150512210011.4ed7af1d@free-electrons.com> (Thomas Petazzoni's message of "Tue, 12 May 2015 21:00:11 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 > I continue to remain unhappy with such changes. There are two options
 > here:

I agree that it would be better if we could get this kind of fixes
upstream. I don't know how receptive upstream will be as this doesn't
affect "normal people" though.

 >  * Either using gcc to link with a C++ library is incorrect, and czmq
 >    should be fixed to use g++.

That is arguable correct, but things are a bit more complicated as:

- libzerozmq is written in C++ and uses libstdc++ but exposes a C api
- czmq is a higher level wrapper also written in C
- Test program (czmq_selftest) is a C program linking against libczmq
  (and in term libzeromq)

 >  * Or using gcc to link with a C++ library is correct, and in this
 >    case, libzmq.pc should be fixed to include -lstdc++ in Libs.private.

While this is correct, it is not directly related to this. Czmq doesn't
use its own .pc file to know how to link the selftest program.

Alternatively we can simply mark czmq !BR2_STATIC_LIBS.

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2015-05-12 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 18:43 [Buildroot] [git commit] czmq: unbreak static linking Peter Korsgaard
2015-05-12 19:00 ` Thomas Petazzoni
2015-05-12 19:30   ` Peter Korsgaard [this message]
2015-05-12 20:34     ` Thomas Petazzoni
2015-05-12 22:02       ` Peter Korsgaard
2015-05-13  5:44         ` Lionel Orry
2015-05-13  7:19           ` Peter Korsgaard
2015-05-13  7:23             ` Thomas Petazzoni
2015-05-13  7:57               ` 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=87a8x9h9uw.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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.