Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: new package
Date: Wed, 30 Jan 2013 14:20:43 +0200	[thread overview]
Message-ID: <20130130122042.GC12106@sapphire.tkos.co.il> (raw)
In-Reply-To: <51090847.2040208@zacarias.com.ar>

Hi Gustavo,

On Wed, Jan 30, 2013 at 08:47:19AM -0300, Gustavo Zacarias wrote:
> On 01/30/2013 02:42 AM, Baruch Siach wrote:
> > +WIRESHARK_CONF_ENV = LIBGCRYPT_CONFIG=$(STAGING_DIR)/usr/bin/libgcrypt-config
> 
> I need ac_cv_path_PCAP_CONFIG=$(STAGING_DIR)/usr/bin/pcap-config in
> CONF_ENV also. That's because configure is finding /usr/bin/pcap-config
> from my distribution before the staging one.
> And also the exec_prefix/prefix fixups in
> $(STAGING_DIR)/usr/bin/pcap-config since they point to /usr (the usual
> way in libpcap or Stefan's patch for the nice fixup).
> With these tweaks it builds nicely.
> Also might be worth to bump (again!) to 1.8.5 a security release.

Thanks for testing. I'll updated the patch an resend.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2013-01-30 12:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30  5:42 [Buildroot] [PATCH] wireshark: new package Baruch Siach
2013-01-30 11:47 ` Gustavo Zacarias
2013-01-30 12:20   ` Baruch Siach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-28  8:53 Baruch Siach
2012-10-22  6:27 Baruch Siach
2012-10-23 17:05 ` Arnout Vandecappelle
2012-10-24  7:31   ` Baruch Siach
2012-10-24  7:49     ` Arnout Vandecappelle

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=20130130122042.GC12106@sapphire.tkos.co.il \
    --to=baruch@tkos.co.il \
    --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