Help with libEQ.a ASAP

[mucktail]

I am using SUSE linux 7.2! I had showeq working before(about 4-5 months ago)!

I created a new /seq folder! Downloaded Showeq from CVS! I have compiled a new QT 3.1.1! I have downloaded the newest libEQ.a from ftp://emurfeete.rifocus.net/publibeq/i386/linux/libEQ.a

Now I am trying to compile showEQ, but everytime I try to ./configure , it keeps saying that I am missing the correct libEQ.a

configure: WARNING: "/usr/lib/libEQ.a f45cb14c6e0a4c55c3b60bc0959945d6 which doesn't match reference md5sum

<---- sourceforge doesn't include the newest md5sum on this website anymore. (currentl libEQ.a md5 not needed)

I read the news and I know that libEQ.a is not needed anymore, but then why is it needed when i do the ./configure?

I did a search on libEQ.a and no one has the most current md5sum libEQ.a! I read the newbie install guide about 5 times now, and can't figure the problem out. Oh, and I only have one libEQ.a, and it's in the /usr/lib.

Does anyone have a current version of libEQ.a?
And what is the md5sum?
Do I need libEQ.a to compile Showeq?
Is my md5sum above the most current one! I downloaded off trifocus.com?

Please help! I know it's not the QT 3.1.1, or the gcc3, but I'm thinking its the libEQ.a! I prolly have the wrong version, but I can't verify this cause, it's not on this webpage anymore.

Someone else had this problem, in one of the earlier post, and I have already read that post more then 5 times now.

[LordCrush]

Seems that ou dont have the latest Version form CVS ... The actual Configure dont look for libEQ.a ... make a complete new download - dont update

btw running Suse 7.2. too with QT 3.0.5. - SEQ works fine

[mucktail]

I got Showeq Compiled now! I have Suse linux 7.2, qt 3.1.1, and gcc3!

but when i tried to start showeq by typing

showeq -i et0 192.168.0.6

I keep getting the old version of Showeq that I had before a long time ago. Its version 4.3.5

Where did the new compiled version of showeq go to. I downloaded the Showeq stuff into the /usr/seq/showeq

and compiled it from there. using the command line prompt?

Please help.

[Dedpoet]

Did you do "make install" after you did "make"?

[mucktail]

Yeah, I did ./configure

make

and

make install

Showeq is all compiled!

So, I'm thinking I have 2 versions of Showeq in my computer now. One is the old version, it use to be in the

cd /root/showeq


The new one i compiled is in the

cd /usr/seq/showeq

I use to execute showeq a long time ago, by going to the /usr/local/bin

and type ./showeq -i eth0 192.168.0.6

but now if I do that It just keep using the old version. So the question is, Where is the new one?

maybe i'll try a search for "Showeq".

[Mongo222]

<basic unix knowledge>



sifter root # man which


WHICH(1) WHICH(1)



NAME
which - shows the full path of (shell) commands.

SYNOPSIS
which [options] [--] programname [...]

DESCRIPTION
Which takes one or more arguments. For each of its arguments it prints
to stdout the full path of the executables that would have been exe-
cuted when this argument had been entered at the shell prompt. It does
this by searching for an executable or script in the directories listed
in the environment variable PATH using the same algorithm as bash(1).

This man page is generated from the file which.texinfo.

OPTIONS
--all, -a
Print all matching executables in PATH, not just the first.

--read-alias, -i
Read aliases from stdin, reporting matching ones on stdout. This is
useful in combination with using an alias for which itself. For
example
alias which=<B4<B4>alias | which -i<B4<B4>.

--skip-alias
Ignore option `--read-alias<B4>, if any. This is useful to explicity
search for normal binaries, while using the `--read-alias<B4> option
in an alias or function for which.

--read-functions
Read shell function definitions from stdin, reporting matching ones
on stdout. This is useful in combination with using a shell func-
tion for which itself. For example:
which() { declare -f | which --read-functions $@ }
export -f which

--skip-functions
Ignore option `--read-functions<B4>, if any. This is useful to explic-
ity search for normal binaries, while using the `--read-functions<B4>
option in an alias or function for which.

--skip-dot
Skip directories in PATH that start with a dot.

--skip-tilde
Skip directories in PATH that start with a tilde and executables
which reside in the HOME directory.

--show-dot
If a directory in PATH starts with a dot and a matching executable
was found for that path, then print "./programname" rather than the
full path.

--show-tilde
Output a tilde when a directory matches the HOME directory. This
option is ignored when which is invoked as root.

--tty-only
Stop processing options on the right if not on tty.

--version,-v,-V
Print version information on standard output then exit success-
fully.

--help
Print usage information on standard output then exit successfully.

RETURN VALUE
Which returns the number of failed arguments, or -1 when no `program-
name<B4> was given.

EXAMPLE
The recommended way to use this utility is by adding an alias (C shell)
or shell function (Bourne shell) for which like the following:

[ba]sh:

which ()
{
(alias; declare -f) | /usr/bin/which --tty-only --read-alias --read-functions --show-tilde --show-dot $@
}
export -f which

[t]csh:

alias which <B4>alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde<B4>

This will print the readable ~/ and ./ when starting which from your
prompt, while still printing the full path when used from a script:

> which q2
~/bin/q2
> echo `which q2`
/home/carlo/bin/q2


BUGS
The HOME directory is determined by looking for the HOME environment
variable, which aborts when this variable doesn<B4>t exist. Which will
consider two equivalent directories to be different when one of them
contains a path with a symbolic link.

AUTHOR
Carlo Wood <[email protected]>

SEE ALSO
bash(1)




WHICH(1)


</basic unix knowledge>

[Dedpoet]

Mmmm....Manwich.

The other day I was reading the man page for "man", something I have actually never done in my almost 10 years of using *nix. I almost fell out of my chair when I saw a shell variable used by man called MANSECTS. Yeah, say it fast.

[Mongo222]

Your a great guy an all, Dedpoet, but we don't like you that way. :)