ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 53024: /trunk/image/ /trunk/image/:

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Sun, 3 Nov 2013 01:45:28 +0100
On Sat, Nov 02, 2013 at 06:36:56PM +0100, Pascal Quantin wrote:
> I dp not have a build environment on Windows 8/8.1 yet, but have access to
> a computer to check whether the generated binary runs or not. So I tried to
> build Wireshark with CMake for the fist time on my usual dev machine so as
> to copy the binaries generated on the Windows 8.1 box.
> 
> Running
> cmake --build . -- VERBOSE=1
> 
> Led to the following errors:
> ------ Début de la génération : Projet : wiretap, Configuration : Debug
> Win32 ------
> CUSTOMBUILD : cygwin warning :
>     MS-DOS style path detected: C:/wireshark/trunk/tools/runlex.sh
>     Preferred POSIX equivalent is:
> /cygdrive/c/wireshark/trunk/tools/runlex.sh
>     CYGWIN environment variable option "nodosfilewarning" turns off this
> warning.
>     Consult the user's guide for more details about POSIX paths:
>       http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
>   Generating ascend_scanner.c
>   Running C:/cygwin/bin/flex.exe
>   C:/wireshark/trunk/tools/runlex.sh: line 65: sed: command not found
>   flex: could not create
> --header-file=C:/wireshark/build/wiretap/ascend_scanner_lex.h
>   C:/cygwin/bin/flex.exe failed: exit status 0
>   ascend_scanner.c
> c1 : fatal error C1083: Impossible d'ouvrir le fichier source :
> 'ascend_scanner.c' : No such file or directory
>   k12text.c
> C:/wireshark/trunk/wiretap/k12text.l(82): fatal error C1083: Impossible
> d'ouvrir le fichier include : 'k12text_lex.h' : No such file or directory
>   Génération de code en cours...
> 
> sed is part of my Cygwin installation. Could it be related to a failure to
> locate my Cygwin installation?

Might be. Unfortunately my Windows test machine is offline for a possible but
unlikely virus infection until our admins get back into office to do the checks
on monday, so I have to guess here:
- Is cygwin part of your path?
- What is the output of the "cmake" run?

Thanks for testing!
   Jörg

-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.