wvdial in 10.1
 

I tried the latest wvstreams.


I've asked on the wvdial list, thinking that's where the most likely gurus hang out, but with this result:
> Make went further, but ended with this:
>
> compiling qt/wvqtstring.o...
> linking libwvqt.so...
> /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../../../i486-slackware-linux/
bin/ld:
> cannot find -lqt
> collect2: ld returned 1 exit status
> make: *** [libwvqt.so] Error 1
> root@host:/home/william/temp/wvstreams-4.0.1#
>
> Need I install another version of something?

That's bizarre. If you didn't have Qt, then configure shouldn't have
detected it and it wouldn't have built.

But try installing the Qt development environment.


On the webpage for QT (trolltech?) I can't see any link to download qt-devel, and don't know if it's necessary.

The advice from the developer is:wvstreams-3.75 will NOT work on more recent systems because the folks over at
OpenSSL changed their API in an incompatible way.



Ideas?

YOu might try installing an earlier version of OpenSSL (from slack 10.0 or before the changes...).
Do you have QT installed, I mean the runtime libs?

pkgtool shows qt-3.3.3 installed, that's all I know about qt, except that qt-devel was hard to find, don't know if I ever found it last time I looked,
but this is probably the reason:
root@host:/home/william# find / -name *libwvqt.so
root@host:/home/william#

A url for where I can find the needed qt would be most welcome, as I remember having trouble finding the right one.

Downgrading to an older version of OpenSSL seems an unusual solution.:scratch:

do:
ldd `which wvdial` to find out which version of libwvqt it is calling for..

# ldd `which wvstreams`
which: no wvstreams in (/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)
ldd: missing file arguments

# ldd `which wvdial`
which: no wvdial in (/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)
ldd: missing file arguments

If it's all the same, I would try the wvdial + wvstream packages from linuxpackages.net

They are compiled on 10.0 but they worked just fine for me last time I tried. That is, if you don't have some specific reason for wanting to compile. ;(

Thanks, Duo.
Why didn't I think of that? (kicking self)

Works perfectly.

I have wvstreams installed in my slack 10.1
If you remove the -lqt option from the makefile after you do the ./configure, wvstreams will compile just fine.

I could not find the -lqt option in the makefile, but after finding a .rpm of qt-devel and using rpm2tgz then installing, the latest wvstreams installed OK, but only as root.

Why is it so hard to find qt-devel?

Anyone know of a home website whence it can be downloaded?

I think qt-development packages are installed, otherwise you wouldn't be able to compile a KDE program.

It's just the -lqt is no longer used.

Obviously the -lqt you are seaching if you are using the same version as me is in the 246 line in vars.mk
SO just change this line to:
libwvqt.so-LIBS+= #-lqt
Use a grep like i did and you'll find the -lqt

This is a puzzle -
pkgtool showed no qt-devel until I installed the one I got from FC,
and $ grep -n -e "-lqt" -i * returned nothing.

I installed from cds from the slackware store, can I assume yours are downloaded?

I dont have a qt-devel either. But the devel-package should just contain some header files, you can include in a program, in order to be able to use qt functions that are compiled inside the qt libraries and qt-3.3.3-i486-3 contains the header files, so the qt-devel you are talking about are inside the qt-3.3.3-i486-3 package. The -lqt is an option you use in a compiler to tell it to the linker to search for a library libqt.a or libqt.so which does not exist in slackware 10.1. Where did you do the grep -n -e "-lqt" -i *? You should do it inside the directory where you did the ./configure and make thing and returned the -qt error. Look at what inside this file vars.mk is stated:
In order to use it with libwvqt.so which is a wvstreams library the program tries to create, it searches in /usr/lib/ for a library called libqt-mt.so. If it finds this he uses -lqt-mt. If not it uses -lqt. The libqt-mt.so does exist but it's in the /usr/lib/qt-3.3.3/ in slackware 10.1 and so the program uses the -lqt option that creates an error because libqt does not exist. There is no problem with the qt development packages. It's just the configuration files are not smart enough and don't work with slackware. Since by removing the -lqt option (which is what i did) it compiles fine, and i don't get errors from the linker like undefined reference, you probably do not need the -lqt-mt either. gcc finds it by itself.

Even if you debug all those things and compile it, you'll have problems because after u connect the namespace IP's (DNS) are not written in /etc/resolv.conf like it should be in slackware but in /etc/ppp/resolv.conf and you have to make a link to this file. I've also encountered some other problems, which means that the whole wvstreams-4.0.1 and wvdial-1.54.0 (That's what i tried to compile) needs to be patched in order to work well for slackware. My guess is that it was never meant to be used with slackware. I've even found a C++ error in one of the 2 packages (I think wvdial). A function that had a boolean returning value, had a "return fail" instead of "return false" line.

Anyway I tried the precompiled packages from linuxpackages today and they work fine. SO stay with those.
Also using the fedora qt-devel packages was a stupid thing to do, and you should remove them.
Sorry if I was the one who has driven you to do those things by saying you that I managed to compile wvstreams/wvdial. :(

Finally, my slackware 10.1 is an update of slackware 10, using the two 10.1 iso images i found in a PC magazine's DVD. I would guess they downloaded them from a mirror but i don't think this does make any difference at all. Aren't the ones the slackware store is selling, the same ones you download from a mirror?

Much of this is beyond my present level of understanding, but what I get from it is that:
1- I don't need the qt-devel.
2- The latest wvstreams works no better than the older version, which is a much easier install, so use the .tgz from linuxpackages.
3- Easier to do a fresh install (what I did) than to update.
4- The CDs/DVDs/ISOs *should* be identical.

After unpacking transcode-0.6.14.tar.gz with tar because ark can't open it, I wondered what else might be wrong with my new OS.

Thanks for your explanation of the wvstreams problem. I wonder if the developer is aware of this.

1. YES!!!!
2.the latest wvstreams is something I think included in debian and they changed it(I think). The packages in linuxquestions could be patched to work for slackware, I don't know, that's one of the problems with linuxpackages, they don't include the .SlackBuild script, you don't know how they were created, you just have to trust the guy that created them, but in this case (wvstreams) it worked better than the source, at least for me.
3. English is not my native language, but i think u misunderstood me on this. I never said that. You told me that you bought slack 10.1, i told you that I did an update from slack 10 with 2 slack 10.1 iso images i found in a PC magazine's DVD, but this does not make any difference.
4. Yes I think there is no difference as I said before. Slackware do not have 2 versions (commercial / free) like Mandrake SuSE or Redhat. This is something I feel guilty about, because although slack is my default OS the last 6 months (I just love it :) ), I never paid for it. No one in my family has credit cards and I cannot find it in any Greek computer store...:(