BackTrack Linux, what am I doing wrong?

This is probably occurring because Qt3 is installed to a different path from the one the ‘configure’ script is expecting. I advise you to open up the file and look for the section where it checks for the existence of these files.
Once you know the expected path, you can look at that location on your system and see if the Qt3 is actually there. If it’s not then you can use ‘apropos qt’ to get the name of the filename the system knows for that program (apropos gives you a list of manpages, you might have to read the appropriate man page to figure out what to look for) and then ‘which Qt3’ (assuming that Qt3 was the correct filename) to determine the installed path.
Then you can edit the ‘configure’ file to reflect the true path, and the error should go away.

@koanhead Thanks! I’ll try that when I get home.

damnit, nothing in there that says QT3, and copying the qt3 folder in doesnt work. fuck

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.

Here is everything.

Oh, I didn’t realize that this was using some goofy make replacement. I don’t know SCons, so I can’t help you with this, I’m afraid. I read up on it some, and it doesn’t use the system environment apparently. If you want to get this thing working I’m afraid you’re going to have to read the SCons wiki and figure out how to tweak it.

Don’t you just love it when software developers expect you to learn some obscure BS just to get their stupid project to work?

@koanhead Oh, totally