Ethereal-users: Re: [Ethereal-users] can't belive i still can't install...
> "./configure" cannot run?? - Do not Unzip AND un-tar in windows before
> copying it over! Somehow the "carriage return" becomes ^M in Linux, then
> the Configure script will not run.
In DOS and Windows (all versions, whether NT-based or not), lines in
text files end with carriage return/line feed.
In UNIX, lines in text files end with line feed.
^M is carriage return, it didn't become carriage return; the file
probably got Windowsified in the process of copying it, or something.
(The Ethereal source "tar.gz" files contain UNIX text files; some
DOS/Windows tools can cope with both DOS/Windows-style and UNIX-style
text files, e.g. Microsoft's C compilers can.)
> "pcap.h" not found?? - Remember to install libpcap-devel.RPM AND
> lipcap.RPM...somehow it did not work for me when I just had one version
> installed.
The "libpcap-devel" and "libpcap" RPMs aren't different versions of the
same package, they're different packages. "libpcap" supplies the files
needed by binary programs linked with the libpcap shared library/DLL,
but not the files needed to compile from source code programs that use
libpcap; libpcap-devel supplies the files needed to compile. If you're
compiling Ethereal from source, you need libpcap-devel as well as
libpcap.
> "ltconfig wrong version"?? - Red-Hat 7.2 comes with libtool ver 1.4.
> Download and install the 1.3.4RPM. Maybe the next version of Ethereal
> will fix this one.?
Somehow the make process appears to be running the system's installed
version of "ltconfig", not the one in the Ethereal tarball, which is
1.3.4. Or perhaps it's regenerating the ltconfig file or the ltmain.sh
file using the installed libtool.
> LASTESTS PROBLEM!! - "ln" : Cannot create both symbolic and hard Links!,
> operation not permitted.
As noted, that's the problem you're going to have on a FAT32 file
system.
You should probably leave Windows out of the picture when installing
Linux software - don't unpack it on Windows, don't copy it on Windows,
and don't store it on a Windows file system. You'll run the risk of
seeing the first and the last of the listed problems all over again on
the next package if you do that.
