Wireshark-dev: Re: [Wireshark-dev] Build error: NMAKE : fatal error U1077: 'sed'
From: "Peter Johansson" <[email protected]>
Date: Thu, 22 Nov 2007 07:57:29 +0100
I compile Wireshark using both VS 2005 and VS 2005EE and do not run into problems like this. What version of cygwin sed are you using? Mine is ver 4.1.5-2.
There are no "special" settings you need to setup to build with VS 2005 (either version) other than updating config.nmake to reflect which VC++ version you are compiling with.
/ Peter

2007/11/21, [email protected] <[email protected]>:
To begin with,
From the output listed it looks like your using a flavor of Visual Studio 2005 (VS 8.0).  It is still recommended to use VS 6.
I have not tried using VS 2005 to build Wireshark.  I know that some developers on the "Wireshark-dev" list have successfully built Wireshark with VS 2005.  I don't remember if there are any special settings for the VS 2005 build.
I've kept my VS 6 installed just for Wireshark!!
Sorry I can't provide any insight.  Your problem does sound familiar. I know that it's been discussed previously.

From: Stage Ontw [mailto:[email protected]]
Sent: Wednesday, November 21, 2007 9:52 AM
To: Cook, Timothy [EPM/WAT]
Subject: Re: [Wireshark-dev] Build error: NMAKE : fatal error U1077: 'sed'


Hi there,

I'm trying to build Wireshark on Windows XP. The first time I tried it worked fine, but after that every time I try to build the source I get an error. It's the same error as Alex Diaconou talked about in http://www.mail-archive.com/[email protected]/msg07445.html . You replied in that topic that he should setup his build environment like in the developers guide. I did that the first time already, but the problem occurred. Have you got any idea what will solve my problem?

Thanks in advance,

Joost van Zoest

P.S. the output of "nmake -f Makefile.nmake all" is:

Microsoft (R) Program Maintenance Utility Version 8.00.50727.762

Copyright (C) Microsoft Corporation.  All rights reserved.

        sed -e s/@[email protected]/0.99.6-MX/IP protocol V1.0/  -e "s/@[email protected]/#d

efine HAVE_GNU_ADNS 1/"  -e "s/@[email protected]/#define HAVE_LIBPCRE 1/"  -e "s/@HAVE

[email protected]/#define HAVE_MIT_KERBEROS 1/"  -e "s/@[email protected]//"  -e "s/@[email protected]/#

define HAVE_LIBZ 1/"  -e "s/@[email protected]/#define HAVE_LIBPCAP 1/"  -e "s/@HAVE

[email protected]/#define HAVE_PCAP_FINDALLDEVS 1/"  -e "s/@HAVE_PCAP_DATALINK_

[email protected]/#define HAVE_PCAP_DATALINK_NAME_TO_VAL 1/"  -e "s/@HAVE_PCAP_DATALI

[email protected]/#define HAVE_PCAP_DATALINK_VAL_TO_NAME 1/"  -e "s/@HAVE_PCAP_BRE

[email protected]//"  -e "s/@[email protected]/#define HAVE_LIBWIRESHARKDLL 1/"  -e "s

/@[email protected]/#define WPCAP_CONSTIFIED 1/"  -e "s/@[email protected]/#define

 HAVE_LIBGNUTLS 1/"  -e "s/@[email protected]/#define HAVE_LIBGCRYPT 1/"  -e "s/@H

[email protected]/#define HAVE_LUA 1/"  -e "s/@[email protected]/#define HAVE_LUA_5_1 1/"  -e

 "s/@[email protected]/#define HAVE_AIRPCAP 1/"  -e "s/@[email protected]/#define HAVE_

AIRPDCAP 1/"  -e "s/@[email protected]/#define HAVE_LIBPORTAUDIO 1/"  -e "s/@PO

[email protected]//"  -e "s/@[email protected]/#define HAVE_NET_SNMP 1/"  < config.h.w

in32 > config.h

sed: -e _expression_ #1, char 24: unknown option to `s'

NMAKE : fatal error U1077: 'sed' : return code '0x1'


CONFIDENTIALITY NOTICE - This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify Stage Ontw by telephone or [email protected] and delete the original transmission and its attachments without reading or saving in any manner.

Wireshark-dev mailing list
[email protected]