This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Build error while trying to build wireshark source on linux 64 machine

0

Hello,

I'm new to linux and wireshark development and awfully clueless here. My task is to build wireshark source wireshark-1.8.7. I'm getting the below error when I try configure make uninstall also gives the same error.

./configure: line 24671: syntax error near unexpected token `3.0.0,'
./configure: line 24671: `                      AM_PATH_GTK_3_0(3.0.0,'

config.log has below error but I'm not sure if this has related

configure:23853: gcc -c -g -O2 -Wall -W -Wextra -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -Warray-bounds -Wcast-align -Wformat-security -Wold-style-definition -Wno-error=unused-but-set-variable -fexcess-precision=fast  conftest.c >&5
cc1: error: unrecognized command line option "-fexcess-precision=fast"

linux machine info: 2.6.32-358.el6.x86_64

[[email protected] Wireshark]# lsb_release -a
LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description:    Red Hat Enterprise Linux Server release 6.4 (Santiago)
Release:        6.4
Codename:       Santiago

Request for pointers what I might be missing.

This question is marked "community wiki".

asked 25 Jul '16, 04:48

satishp's gravatar image

satishp
16●2●2●6
accept rate: 0%

edited 25 Jul '16, 04:57

grahamb's gravatar image

grahamb ♦
19.8k●3●30●206

One Answer:

1

That error suggests that AM_PATH_GTK_3_0 wasn't replaced with the contents of that function. That's odd. Where did you get the source from. The 1.8.7 source tarball from wireshark.org don't have that problem.

I'd suggest running ./autogen.sh to re-generate ./configure.

If that doesn't fix it then you're probably working from a modified version of Wireshark. If that's the case then you're going to have to try to figure out which of the changes that have been applied locally are causing the breakage.

Of course I'd really suggest using a (much) more recent version. But I'm guessing from your question that there's a particular reason you have to use exactly that version.

answered 25 Jul '16, 12:30

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k●5●72
accept rate: 27%

Hello JeffMorriss,

Thanks a lot for your response. executing ./autogen.sh to re-generate ./configure fixed the issue.

(26 Jul '16, 02:55) satishp

You're welcome. Since this is a Q&A site (not a forum) please be sure to "accept" the answer that answers your question (by clicking the checkmark next to the answer). That way the question won't show up in the list of unanswered questions (among other things--see the FAQ).

(26 Jul '16, 05:04) JeffMorriss ♦