Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] divine: fix divine-config
Date: Sun, 06 Jan 2013 16:15:10 +0200	[thread overview]
Message-ID: <50E986EE.3030904@petroprogram.com> (raw)
In-Reply-To: <20130106054113.GD13545@sapphire.tkos.co.il>

Hi Baruch

6.1.2013 7:41, Baruch Siach kirjoitti:
> Hi Stefan,
>
> On Fri, Jan 04, 2013 at 04:56:53PM +0200, Stefan Fr?berg wrote:
>> Hello Gustavo, all
> [...]
>
>> (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...)
> Good to see work on wireshark. Did you fix the RPATH problem I encountered 
> while trying to build tshark 
> (http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/48053) ?
>
> baruch
>

Well, I have managed to compile almost out of the box of wireshark
version 1.8.4.
The only patch
I borrowed was from gentoo linux witch is suppose to fix those damn
-L/usr/lib being
included. Also needed to fix buildroots libpcap config file,
$(STAGING_DIR)/usr/bin/pcap-config.

I did the full gui-wireshark build with almost all the stuff inluded
(left out kerberos and geoip) and
then it stopped at the final linking phase where it was suppose to
create wireshark binary.
Really frustrating.

My buildroot full system is soon rebuild and then I will try to build
wireshark again and post
the error message here.

Regards
Stefan

  parent reply	other threads:[~2013-01-06 14:15 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
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 [this message]
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=50E986EE.3030904@petroprogram.com \
    --to=stefan.froberg@petroprogram.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