Wireshark build fails on 10.4.10 MacBook Core Duo
I'm trying to build Wireshark from MacPorts 1.5.1 on a 1st generation MacBook running OS X 10.4.10 with the following port command:
sudo port -v install wireshark +adns +ipv6 +net_snmp +pcre
The final error is:
cc1: warnings being treated as errors In file included from /opt/local/include/glib-2.0/glib/ gasyncqueue.h:30, from /opt/local/include/glib-2.0/glib.h:32, from wtap-int.h:30, from 5views.c:30: /opt/local/include/glib-2.0/glib/gthread.h: In function 'g_once_init_enter': /opt/local/include/glib-2.0/glib/gthread.h:335: warning: cast discards qualifiers from pointer target type make[3]: *** [libwiretap_la-5views.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2
Warning: the following items did not execute (for wireshark): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing.
Has anyone else seen this? I've attached the entire 'port -v' output. Thanks for any help, Chip Warden
Chip Warden <lgw4@mac.com> writes:
I'm trying to build Wireshark from MacPorts 1.5.1 on a 1st generation MacBook running OS X 10.4.10 with the following port command:
sudo port -v install wireshark +adns +ipv6 +net_snmp +pcre
The final error is:
cc1: warnings being treated as errors In file included from /opt/local/include/glib-2.0/glib/ gasyncqueue.h:30, from /opt/local/include/glib-2.0/glib.h:32, from wtap-int.h:30, from 5views.c:30: /opt/local/include/glib-2.0/glib/gthread.h: In function 'g_once_init_enter': /opt/local/include/glib-2.0/glib/gthread.h:335: warning: cast discards qualifiers from pointer target type make[3]: *** [libwiretap_la-5views.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2
Warning: the following items did not execute (for wireshark): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing.
Has anyone else seen this? I've attached the entire 'port -v' output.
I just tried it and I see the same thing on my MacBook Pro. Someone should create a ticket for it or ask the wireshark support list to go the extra mile. I suspect they would know the answer. I'm also cc'ing the maintainer. Mark
On 8/13/07, markd@macports.org <markd@macports.org> wrote:
Chip Warden <lgw4@mac.com> writes:
I'm trying to build Wireshark from MacPorts 1.5.1 on a 1st generation MacBook running OS X 10.4.10 with the following port command:
sudo port -v install wireshark +adns +ipv6 +net_snmp +pcre
Has anyone else seen this? I've attached the entire 'port -v' output.
I just tried it and I see the same thing on my MacBook Pro. Someone should create a ticket for it or ask the wireshark support list to go the extra mile. I suspect they would know the answer. I'm also cc'ing the maintainer.
Mark
About a week ago I upgraded to MacPorts 1.5 (not 1.510) and recompiled wireshark 0.99.6 with no variants (after updating dependencies first). No problems compiling or using Wireshark 0.99.6 on my MacBook Pro. Today I upgraded to MacPorts 1.510 and then uninstalled/cleaned wireshark. Next I successfully recompiled wireshark with no variants specified (sudo port install wireshark). My guess is one of the variants +adns or +ipv6 or +net_snmp or +pcre is causing the problem. BB
On Mon, Aug 13, 2007 at 03:48:28PM -0700, Brian Barrera wrote:
On 8/13/07, markd@macports.org <markd@macports.org> wrote:
Chip Warden <lgw4@mac.com> writes:
I'm trying to build Wireshark from MacPorts 1.5.1 on a 1st generation MacBook running OS X 10.4.10 with the following port command:
sudo port -v install wireshark +adns +ipv6 +net_snmp +pcre
Has anyone else seen this? I've attached the entire 'port -v' output.
I just tried it and I see the same thing on my MacBook Pro. Someone should create a ticket for it or ask the wireshark support list to go the extra mile. I suspect they would know the answer. I'm also cc'ing the maintainer.
Mark
About a week ago I upgraded to MacPorts 1.5 (not 1.510) and recompiled wireshark 0.99.6 with no variants (after updating dependencies first). No problems compiling or using Wireshark 0.99.6 on my MacBook Pro.
Today I upgraded to MacPorts 1.510 and then uninstalled/cleaned wireshark. Next I successfully recompiled wireshark with no variants specified (sudo port install wireshark).
My guess is one of the variants +adns or +ipv6 or +net_snmp or +pcre is causing the problem.
I suspect the new glib (2.14.0) and wireshark are not getting along, I'll see what I can do with it. -eric
Eric, I suspect you are correct. I just tried (re-)building against glib 2.14.0 on my Mac Pro with the same result... I had first built wireshark using glib 2.12.12 w/o any problems, On Aug 13, 2007, at 5:55 PM, Eric Hall wrote:
On Mon, Aug 13, 2007 at 03:48:28PM -0700, Brian Barrera wrote:
On 8/13/07, markd@macports.org <markd@macports.org> wrote:
Chip Warden <lgw4@mac.com> writes:
I'm trying to build Wireshark from MacPorts 1.5.1 on a 1st generation MacBook running OS X 10.4.10 with the following port command:
sudo port -v install wireshark +adns +ipv6 +net_snmp +pcre
Has anyone else seen this? I've attached the entire 'port -v' output.
I just tried it and I see the same thing on my MacBook Pro. Someone should create a ticket for it or ask the wireshark support list to go the extra mile. I suspect they would know the answer. I'm also cc'ing the maintainer.
Mark
About a week ago I upgraded to MacPorts 1.5 (not 1.510) and recompiled wireshark 0.99.6 with no variants (after updating dependencies first). No problems compiling or using Wireshark 0.99.6 on my MacBook Pro.
Today I upgraded to MacPorts 1.510 and then uninstalled/cleaned wireshark. Next I successfully recompiled wireshark with no variants specified (sudo port install wireshark).
My guess is one of the variants +adns or +ipv6 or +net_snmp or +pcre is causing the problem.
I suspect the new glib (2.14.0) and wireshark are not getting along, I'll see what I can do with it.
-eric
Marius -- Marius Schamschula Webmaster The Huntsville Macintosh Users Group www.hmug.org webmaster at hmug dot org marius at schamschula dot com
On 8/13/07, Eric Hall <opendarwin.org@darkart.com> wrote:
I suspect the new glib (2.14.0) and wireshark are not getting along, I'll see what I can do with it.
Curious, how do you install the new glib? MacPorts is 1.510 and was updated using selfupdate yet I'm running glib 2.12.12 according to /opt/local/lib/glib-2.0/include/glibconfig.h and otool. BB
On Aug 13, 2007, at 20:02, Brian Barrera wrote:
On 8/13/07, Eric Hall wrote:
I suspect the new glib (2.14.0) and wireshark are not getting along, I'll see what I can do with it.
Curious, how do you install the new glib? MacPorts is 1.510 and was updated using selfupdate yet I'm running glib 2.12.12 according to /opt/local/lib/glib-2.0/include/glibconfig.h and otool.
"sudo port sync", then "sudo port -nf upgrade glib2". glib2 was updated to 2.14.0 on 2007-08-11, and before that to 2.12.12 on 2007-07-21. I had hoped that updating glib2 to 2.14.0 would not cause any problems since the release notes say "This is the first in the 2.14 series, providing new functionality compared to GLib 2.12, while maintaining source and binary compatibility."
On Mon, Aug 13, 2007 at 08:58:26PM -0500, Ryan Schmidt wrote:
On Aug 13, 2007, at 20:02, Brian Barrera wrote:
On 8/13/07, Eric Hall wrote:
I suspect the new glib (2.14.0) and wireshark are not getting along, I'll see what I can do with it.
Curious, how do you install the new glib? MacPorts is 1.510 and was updated using selfupdate yet I'm running glib 2.12.12 according to /opt/local/lib/glib-2.0/include/glibconfig.h and otool.
"sudo port sync", then "sudo port -nf upgrade glib2". glib2 was updated to 2.14.0 on 2007-08-11, and before that to 2.12.12 on 2007-07-21. I had hoped that updating glib2 to 2.14.0 would not cause any problems since the release notes say "This is the first in the 2.14 series, providing new functionality compared to GLib 2.12, while maintaining source and binary compatibility."
Unfortunately it does cause some problems - there are warnings in the glib code (see error w/ wireshark that started this thread) and somethings (like wireshark) try to build with -Werror, resulting in problems. I've just committed a fix for wireshark, it should be available to 'port sync' by tomorrow morning. For those wanting the fix faster (and you know what you're doing), simply add '--disable-warnings-as-errors' to configure.args in the Portfile and rebuild. -eric
participants (6)
-
Brian Barrera
-
Chip Warden
-
Eric Hall
-
Marius Schamschula
-
markd＠macports.org
-
Ryan Schmidt