Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] divine: fix divine-config
Date: Fri, 04 Jan 2013 12:00:59 -0300	[thread overview]
Message-ID: <50E6EEAB.4020001@zacarias.com.ar> (raw)
In-Reply-To: <50E6EDB5.9070004@petroprogram.com>

On 01/04/2013 11:56 AM, Stefan Fr?berg wrote:

> So should I continue patching correct buildroot prefixes to all those
> *-config files that
> are in $(STAGING_DIR)/usr/bin or not ?
> 
> From my $(STAGING_DIR)/usr/bin/*-config files only libpng and libxml2
> and few others
> do the right thing and give the buildroot prefix and not the host system
> prefix.
> (It took a long time for me to figure why wireshark that im trying to
> compile here did not
> work out with libpcap, untill I found out that the
> $(STAGING_DIR)/usr/bin/pcap-config spit a
> wrong prefix all the time...)

That's because libpng & libxml2 are doing what your patches do, fixing
up the *-config files.
What Samuel said (correct me if i'm wrong) is the developers meeting
kind of agreed on just dropping the *-config files in favour of
pkgconfig-based (*.pc) solutions, and patch wherever necessary.
What i say is let's fix the dreaded *-config files but in a generic way,
just declaring the relevant files to be fixed as the original mail i
replied to you said until we can properly move to a pkgconfig-only
solution, which i think won't be fast or easy.
Regards.

  reply	other threads:[~2013-01-04 15:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 22:09 [Buildroot] [PATCH] divine: fix divine-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] giblib: fix giblib-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imlib2: fix imlib2-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libgcrypt: fix libgcrypt-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imagemagick: fix Magick[++|Core|Wand]-config Stefan Fröberg
2013-01-04 21:45   ` Peter Korsgaard
2013-01-03 22:09 ` [Buildroot] [PATCH] neon: fix neon-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libnspr: fix nspr-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] xlib_libXft: fix xft-config Stefan Fröberg
2013-01-04 23:30   ` Peter Korsgaard
2013-01-05 13:33     ` Stefan Fröberg
2013-01-04 11:41 ` [Buildroot] [PATCH] divine: fix divine-config Gustavo Zacarias
2013-01-04 14:17   ` Samuel Martin
2013-01-04 14:29     ` Gustavo Zacarias
2013-01-04 14:56       ` Stefan Fröberg
2013-01-04 15:00         ` Gustavo Zacarias [this message]
2013-01-06  5:41         ` Baruch Siach
2013-01-06  8:27           ` Samuel Martin
2013-01-06  8:34             ` Baruch Siach
2013-01-06 12:39               ` Thomas Petazzoni
2013-01-06 14:15           ` Stefan Fröberg
2013-01-06 18:12           ` Stefan Fröberg
2013-01-07 22:17             ` Arnout Vandecappelle
2013-01-07 22:35               ` Stefan Fröberg
2013-01-08  7:48                 ` Arnout Vandecappelle
2013-01-08  8:10                   ` Thomas Petazzoni
2013-01-08  8:24                     ` Arnout Vandecappelle
2013-01-04 16:29     ` Thomas Petazzoni
2013-01-04 16:31   ` Thomas Petazzoni
2013-01-04 17:10     ` Gustavo Zacarias
2013-01-04 17:13       ` Stefan Fröberg
2013-01-04 21:49 ` 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=50E6EEAB.4020001@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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