That is close to what I do on Slackware 8.0 (apart from me using
/opt/ethereal instead of /opt/gnome and therefor having to add an entry to
/etc/profile.d) and it works perfectly.
Did you previously run configure with different options, and not run "make
distclean" before re-running with the options you listed? configure will use
the cached value for lots of things, even if you re-specify them on the
command line.
Regards,
Andrew Hood
A distributed system is one in which the failure of a computer you didn't
even know existed can render your own computer unusable. -- Leslie Lamport,
as quoted in CACM, June 1992
-----Original Message-----
From: c0c0 [mailto:c0c0@xxxxxxxxxxxxxxx]
Sent: Wednesday, 6 February 2002 09:02
To: ethereal-users@xxxxxxxxxxxx
Subject: Re: [Ethereal-users] Problem with configure script in 0.9.1?
On Tue, 5 Feb 2002 12:52:03 -0800 (PST)
Guy Harris <guy@xxxxxxxxxx> wrote:
> > I downloaded the 0.9.1 version and tried to install it on my Slackware
> > 8.0 system. My configure options is like this:
> >
> > ./configure --prefix=/opt/gnome --exec-prefix=/opt/gnome
> >
> > it configures and when i make and make install
> >
> > root@darkstar:~# which ethereal
> > /usr/bin/ethereal
>
> What does
>
> ls -l /opt/gnome/bin/ethereal
>
> print?
root@darkstar:~# ls -l /opt/gnome/bin/ethereal
/bin/ls: /opt/gnome/bin/ethereal: No such file or directory
>
> If it shows that there's an "/opt/gnome/bin/ethereal" file, the problem
> may just be that your command search path setting either doesn't search
it is in the search path.
> "/opt/gnome/bin" or searches it after it searches "/usr/bin".
may be this could be the problem, but then why it goes to the /usr/bin in
the first place?
-------------------------------------------------------
NOTE: The attachment below was deleted because it had a
suspicious file name (winmail.dat).
It is the policy of this list to drop any message
attachments that may be executable. See
http://www.ethereal.com/lists/#lists
for more details.
-------------------------------------------------------
This message has been 'sanitized'. This means that potentially
dangerous content has been rewritten or removed. The following
log describes which actions were taken.
Sanitizer (start="1012949480"):
Part (pos="1823"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
Match (rule="2"):
Enforced policy: accept
Part (pos="3643"):
SanitizeFile (filename="winmail.dat", mimetype="application/ms-tnef"):
Match (rule="1"):
Enforced policy: drop
Replaced mime type with: text/plain
Replaced file name with: MANGLED_ON_PURPOSE-177932.txt
Total modifications so far: 1
Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.32 2001/10/11 19:27:15 bre Exp $
