checking for ranlib... ranlib
checking for ar... ar
checking for lrelease-qt4... no
checking for lrelease... /opt/qt4/bin/lrelease
checking for lupdate-qt4... no
checking for lupdate... /opt/qt4/bin/lupdate
checking for moc-qt4... no
checking for moc... /opt/qt4/bin/moc
checking for uic-qt4... no
checking for uic... /opt/qt4/bin/uic
checking how to run the C preprocessor... gcc -E
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for Qt headers... configure: error: not found

any ideas?

EDIT: Should have stated I'm using Slacko 5.3.1._________________helping Wiki for helpLast edited by darkcity on Wed 02 Oct 2013, 14:08; edited 3 times in total

I'm afraid I don't know what the package is that you are trying to compile. There are a couple of ideas you could try which I have had success with previously when I have encountered "headers not found" errors.

It could be that the headers are installed in a nonstandard path where it can't see them. Presumably you can use ROX or your file manager to see where they are and then add the CPPFLAGS to tell it where to look. Along the lines of:-

Code:

./configure CPPFLAGS=-I/path/to/includes

(character after the dash is a capital "i")

I have sometimes had to do this in Wary because some headers are down the /usr/X11R7/include path.

The other thing that sometimes happens is that headers are in a sub-folder when they need to be out in the open or vice versa. Creating symlinks to correct the path may resolve this but I'm not sure how practical that would be in the case of Qt._________________Oscar in England

It might be worth grabbing a copy of slax 6 since it will have all the dev files included for qt3 though seems odd that the header files you obtained from debian will not play but perhaps debians qt3 layout differes in some way which would not be surprising...or qt variables need setting up..or it expects package config files to be already present.

i'm using precise puppy and i installed pemasus qt4.8.2.sfs and qt4.8.2.dev http://smokey01.com/pemasu/pet_packages-upup/ then libqt4-qt3support from the PPM. when installing libqt4-qt3support, i unchecked all the other libqt4 stuff as it's in the .sfs.

The java program looks very interesting at http://www.falstad.com/circuit/
Nice find, ill dig in when I have more time

I have installed Qucs 0.16 packaged by WN2A. I just wanted to try the latest version - looks like a few years between releases even though it only a 0.01 version increase.
The copy you linked to seems to be corrupted, I used Geoffrey's mirror, see http://murga-linux.com/puppy/viewtopic.php?p=727423#727423

@666philb

Thanks for your help making progress. Using qt4.8.2 and DEV SFSs meant I could configure Qucs, and added libqt4-qt3support from a deb (can't find in slacko repos). It won't compile though -

I think this means it Qucs in compiled against Glibc 2.15, but Slacko 5.3.1 is only 2.13. It may have to wait until I upgrade Puppy.

seems more likely the QT4 library wants glibc 2.15...do the set you have work with other apps?

Note...such as QT etc can usually be built against older glibc....and debian tend to force a higher glibc than actually needed as part of keeping things in the fold. Not sure how they do it...I just recompile the same sources and lo and behold glibc needs drop several versions...even if built on a system with a higher version.

Hmm perhaps dig into the configure and see what its looking for in terms of headers... different sources have different ways of checking dependancies...some want those little binaries that splurge out library infoi for example.
In linux one thing that is consistant is a lack of consistancy

OR..compile QT4 yourself....sometimes its easier....and you have a library set you can rely on

open the PPM and tick the .dev box and search for qt
then install the qt-everywhere.dev package... this will also install qt (slacko version) and another dep. (qt everywhere includes libqt4-qt3support)

you will then either have to copy /opt/include to /usr/include, or you can tell the compiler to look for the headers in /opt/ .. i don't know how to do that, so i just dragged and dropped /opt/include to /usr.

qucs should then compile.

you need to make sure all your other qt remnants are uninstalled or they might conflict.

>In linux one thing that is consistant is a lack of consistancy Very Happy
the standard is no standard ; -)

>OR..compile QT4 yourself....sometimes its easier....and you have a library set you can rely on
I had I go at that, it takes quite a long time on my machine.

>then install the qt-everywhere.dev package... this will also install qt (slacko version) and another dep. (qt everywhere includes libqt4-qt3support)
maybe this is where I was going wrong, looking for libqt4-qt3support on its own.

>i can post you the .pet if you want?
I would appreciate that, as I don't have much time at mo_________________helping Wiki for help

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum