Ethereal-dev: Re: [Ethereal-dev] (no subject)
Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.
From: Ed Warnicke <hagbard@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 25 Dec 2000 22:14:27 -0500 (EST)
OK... I can't speak at all as to your issues with Windows. I just don't use that platform. As to you problems with linux... I can make a few guesses. First, you must have flex, bison, and python installed for ethereal to compile. Since you didn't say which distribution of linux you're trying to compile on I can't comment precisely on what you should do to check, but try looking for flex, bison, and python in /usr/bin or /usr/bin/local. Second, you need to have the appropriate header files for glib. This usually is separate for most linux distributions from having the glib. Typically the header files will be in a glib-dev package of some sort ( libglib1.2-dev for Debian Woody ). You can check to see if you have the headers by looking for /usr/include/glib.h. Third, you should just be able to check the source out of CVS and then type ./autogen.sh make make install You shouldn't have to be applying flex, bison, or python to any of these files manually, the compile process should do it for you. These are the potential pitfalls that come to mind. I have attatched a file containing a trace of the build process on my system so that you can at least see what it is supposed to look like (I've ofter found such things useful). If you could say what linux distribution you are using I might be able to help more. Ed P.S. If you could make a trace of your attempts to compile that might also be helpful. This can be accomplished with the program script. If you type script then you will get a prompt back. From then on everything you type and everything that is displayed back to you will be written to the file typescript until you type exit at which point you will get your old prompt back. If you could in this way capture a trace of your attempts perhaps I could see what you are doing. On Mon, 25 Dec 2000, Guillaume Le Malet wrote: > Hi! > Im trying to compile ethereal since more than a week...And it still > doesnt work. > So I decided to ask you some questions: > -why do have I to change the :: in : in the makefile.nmake?? > (If I dont do it, it doesnt even begin to compile) > -what are the precise commands to make the unix-ish generated files? > (dfilter-grammar.y ,dfilter-scanner.l, wiretap/ascend-grammar.y, > wiretap/ascend-scanner.l, make-reg-dotc, packet*.c, ncp2222.py) > because I've tried with cygwin and under linux and I've got > errors...so I suppose I didn't used the right options. > -Is there a special manip for including those bin in the config.nmake, > cause when I write the path, it doesnt seem to see it (and I didnt > make mystakes, I dont think so). > > Thanks. > > Merry christmas and happy newyear. > > Guillaume. > > _______________________________________________ > Ethereal-dev mailing list > Ethereal-dev@xxxxxxxxxxxx > http://www.ethereal.com/mailman/listinfo/ethereal-dev >
Attachment:
typescript
Description: Binary data
- References:
- [Ethereal-dev] (no subject)
- From: Guillaume Le Malet
- [Ethereal-dev] (no subject)
- Prev by Date: [Ethereal-dev] Help: compiling ether under win
- Next by Date: [Ethereal-dev] some dfilter work
- Previous by thread: [Ethereal-dev] (no subject)
- Next by thread: [Ethereal-dev] Flexible file formats
- Index(es):