Do you mean that there’s nothing in the ‘configure’ script that refers to Qt3? It must be in there somewhere, since it prints out that error message.
It looks like the script might be checking the environment for the location of the library, which is probably called “qtlib”-something.
It looks like BackTrack is at least partially Knoppix-based, so it might have apt-get. Try doing ‘apt-cache search qtlib’ or maybe ‘apt-cache search qt3’.
If you get a match on either of those that looks like it’s the right package, then you can do ‘dpkg -L [packagename]’ to get a list of the files that are associated with the package. It should be pretty obvious which one is the path you want. Then if you can’t find a place in the file to insert that path, it’s probably because the script is checking the environment for it. If you want to post that script I’ll take a look and probably be able to tell you what it’s doing.
The reason why I think the script is looking in the environment for its install paths is the message “please set QTDIR first” in the error message. Environment variables are all caps by convention, and a convenient place to put “sticky” variables that will get used more than once. For example, if the path to qt3 turns out to be /usr/lib/libqt3 then you’d do ‘export QTDIR=”/usr/lib/libqt3” ’ to set it. To see the value of the variable you’d do ‘echo $QTDIR’ (I don’t know why, but you omit the $ when you set the value, but include it in all other references to the variable.) To see all the environment variables and their values just type ‘env’.
By the way, if BackTrack uses the same or similar package names as Ubuntu, then the search you want to do is ‘apt-cache search libqt3’ and the package is probably libqt3-headers.