Ethereal-dev: Re: [Ethereal-dev] Problems in compiling 0.10.5 on Windows

Note: This archive is from the project's previous web site, This list is no longer active.

From: Michael Tuexen <[email protected]>
Date: Thu, 8 Jul 2004 23:27:43 +0200
Dear all,

see my comments below.

Best regards

On Jul 8, 2004, at 11:07 PM, Guy Harris wrote:

Ulf Lamping said:
It might be a good idea to supply the error messages to make your
problems understandable, as always :-(
I suspect the error message complains that <unistd.h> doesn't exist.

Yes, that is correct.
This is a problem that's happened in the past.

However, the
files can be generated from the corresponding *.l files and
I don't think that .l files will be generated by a typical MSVC
Presumably you mean "...will be run through Flex in a typical MSVC
Well, I installed all the cygin stuff and just run
nmake -f Makefile.nmake

and the .c files are generated in the Windows environment from the
Makefile.nmake. It uses flex...
So why are the two .c files included in the tarball?
It may compile in your specific environment...
...if your specific environment is a UN*X.  Unfortunately, to get 
of those files that compile in an MSVC++ environment, you may have to 
the ".l" files through a Windows-ified version of Flex.

Yes, I think that is the point. The windows flex version puts in the
necessary #ifdefs...
The files are included because there might be UN*X environments that have
a C compiler capable of compiling Ethereal but that don't have Flex
(consider one of the commercial UN*Xes that come with an
AT&T^H^H^H^HNovell^H^H^H^H^H^HSCO-derived lex rather than with Flex;
unless somebody's installed Flex on the machine, it won't be possible to
turn the ".l" files into ".c" files).

OK. So what about just removing the files on the window platform using
the Makefile.nmake script before compiling the stuff, if that is possible?
Ethereal-dev mailing list
[email protected]