Sourceforge project page: TrueCrypt stops in 5/2014
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Quite a few years ago I somehow decided to look at encryption of volumes/disks (I was using SuSE). I've been going ape-crazy trying to remember what it was and finally did today...ScramDisk http://sd4l.sourceforge.net/
At the time I was looking at it, it was working wonderfully for kernel 2.x and my SuSE. There still seems to be a 'little' bit of work on it according to a post or two on the sourceforge page and one of the devs had uploaded a couple of patches to try and get it working on 3.x kernels.
QWithout the patch, the build gets stuck much earlier than after the patch is applied. After applying the patch, the build gets stuck at:
I've joined the users mailing list and sent that in, but haven't heard anything back yet. Hopefully if more people can get interested in it again it will let the devs know we miss it and need it (especially *IF* this truecrypt thing turns out to be real).
Not personally using but by the error message you would probably need qt3 installed, for latest release available here at SlackBuilds.org.
Or try to compile without Qt GUI if there is such option.
Thanks for that tip, dunric.
Unfortunately I just can't seem to get the makefile and the Scrqamdisk.pro fixed up right to start 'make'
Not being a programmer, I can sometimes muddle my way through these things just barely enough to make them work. This time though is one of those times that even after 8+ hours I just can't seem to get it right.
Maybe one day someone who understands this stuff will look at it. I'm pretty sure someone who programs, even a beginner, could fix it correctly...I'm just not even a 'beginner', no programming skills, I just 'look' at things and add this or delete that and keep trying (if that makes sense).
Anyway, I appreciate the tip as it's qt3 that this app is wanting to use to build it.
@irgunII If you've managed to install qt3, C++ compiler tells you it can't just find qt3 header file(s). You'd need to set correct paths for include and library files, either in Makefile or in an environment. Compiler recognizes C_INCLUDE_PATH and CPLUS_INCLUDE_PATH where searches header files and LIBRARY_PATH for library files. Multiple paths are colon-separated.
This I got done but wasn't as easy as just getting it off Slackbuilds.org, took a little more but not too bad.
Originally Posted by dunric
C++ compiler tells you it can't just find qt3 header file(s). You'd need to set correct paths for include and library files, either in Makefile or in an environment. Compiler recognizes C_INCLUDE_PATH and CPLUS_INCLUDE_PATH where searches header files and LIBRARY_PATH for library files. Multiple paths are colon-separated.
Believe it or not, as I (tried to) explained in another post in this thread, I was actually sort of getting there by over and over doing different things to the 'Makefiles' *and* Scramdisk.pro (found out that one was really messing my saves up after about 6 hours, heh). Something though just never seems to quite get it right and it always fails at one or the other above errors. Since I have no clue what I'm really doing, I'm just bumbling along and hoping for the best when I'm doing this kind of thing (again, I'm no programmer and can't even write a bash script).
It still doesn't explain why it worked for ml4711 with what he did and it doesn't do it for me (or more than likely I just simply don't understand something somewhere and am missing it completely).
Anyway, been going at it for at least a full 16 hours now and since I haven't the skills to figure out anything more than what I've already tried on my own and it doesn't seem like too much other interest has picked up for this, it's probably best I just let it gather dust and forget it. Kind of a bummer though since I believe it could be another good disk encryption app to have around so that the linux world isn't so sparse and running around with its head cut off trying to find a replacement. Thanks though for the help, it's honestly appreciated.
It seems Your qt3 install is not complete,
maybe You are missing "/etc/profile.d/qt.sh"
which set up needed environment variables for You.
The needed ones to set are: QTDIR and CPLUS_INCLUDE_PATH
Or you do not have the qt3 include files in the right place.
I did try to compile without those two variables set, and got the same errors as You get.
Actually you don't need to call qmake yourself, as it is called from the Makefile.
So the full command set to compile should be:
AHA!! That code is what worked! I didn't need anything in /etc/profile.d though.
When I was trying over and over to re-write the Makefile and .pro file and then doing 'make', even though I'd *thought* I'd found everything I could possibly find to do with 'includes' *and* QTDIR's, it would always give the errors I was telling about *and* would rewrite itself back to the stock Makefile (that one *really* was getting me PO'd, lol).
Anyway, it's now installed on my system and I'm going to wipe my spare hdd of any files and give this ScramDisk a try and see if it's working well enough and if it is, I'll try and figure out how to make all this into a Slackbuild for the community (and of course I'll more than likely be back here begging for help with *that too, heh).
I'm very, very grateful for all your help, ml4711, and glad you had the patience to stick with me with all my idiocy.
I also appreciate everyone else who helped. Thanks to all.
That little script
- qt.sh would have set QTDIR and CPLUS_INCLUDE_PATH for You,
so the only thing You had to do was an export of the PATH variable
Just get it from slackbuilds.org,
adjust the path in the script if needed and put it in place.
The qt3.SlackBuild also creates links to the qt3 executables from /opt/bin
so if you have these links, export PATH=/opt/bin:$PATH should also have worked!
Very good it worked for You - have a nice Sunday Evening!
I just took a look and it seems I do have a qt.sh. I can't be absolutely sure that what's in it is what I need when/if doing anything with qt3 ever again, but I *think* it has everything you were saying it *should* have, yes?