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] [PATCH v2 1/1] package/sispmctl: fix static linking
Date: Sun, 5 Oct 2014 23:36:51 +0200	[thread overview]
Message-ID: <20141005233651.6320c514@free-electrons.com> (raw)
In-Reply-To: <1409008353-20940-1-git-send-email-romain.naour@openwide.fr>

Dear Romain Naour,

On Tue, 26 Aug 2014 01:12:33 +0200, Romain Naour wrote:
> The static linking doesn't works with libusb-compat when using libusb-config.
> Also the CFLAGS initialization with libusb-config --cflags is comented out.
> 
> Based on libftdi's patch, add the support for pkg-config to link sispmctl
> correctly.
> 
> This allow to add correct include directory to CFLAGS
> (Add -I$(STAGING_DIR)/usr/include and -I$(STAGING_DIR)/usr/include/libusb-1.0)
> Also add needed libraries during static linking (-lusb -lusb-1.0 and -pthread)
> 
> Since configure.ac is modified, the configure script needs to be regenerated
> with autoreconf.
> 
> Fixes:
> http://autobuild.buildroot.net/results/647/6473088e751d3ab3a5227e9d7876966934e66378/build-end.log
> 
> Cc: Phil Eichinger <phil.eichinger@gmail.com>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>

Thanks, applied. Please submit the patch upstream so that one day we
can remove it from Buildroot.

Thanks,

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

  parent reply	other threads:[~2014-10-05 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 23:12 [Buildroot] [PATCH v2 1/1] package/sispmctl: fix static linking Romain Naour
2014-08-26  6:47 ` Phil Eichinger
2014-08-28 21:42   ` Romain Naour
2014-10-05 21:36 ` Thomas Petazzoni [this message]
2014-10-08 20:17   ` Romain Naour
2014-10-08 20:29     ` 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=20141005233651.6320c514@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