I would have expected SOMETHING to say what was wrong also, MOE-lnx. The vector://home/bruce/grisbi/libofx-0.9.0 root:# is the system prompt and make was my command, the rest, through Error 2, was make output.

After reading your message wcs, tried making grisbi from thunar and received no errors. But I can't find it any where on the system, the menu, nor any of the directories. Since I am operating as root when I installed it (and still am), I'll log back as Bruce and see if it shows up.

The only thing I can add to my first post is my directory structure:/home/bruce/grisbi/libofx-0.9.0/ grisbi-0.5.9-i486-1chg.tgz latex-ucs-20040509-noarch-1gn.tgz libofx-0.9.0.tar.gz opensp-1.5.1-i686-1ak.tgz

libofx-0.9.0/ contains 495 items 8.7Mb

I don't know why 'make' dropped back a directory. I hadn't even unpacked the other files at the time of that 'make'.

When I right click on *.tgz, thunar offers the option to install. It only offers to unpack *.qz or *.tar.gz.

Also, before you comment on my working as root, the other evening I apparently mis-typed my password to 'sudo su' twice and Linux would no longer let me even start that command. So, rather than log off and lose all of my windows to log on as root, I just stay here.

suinstallpkg <name of package>Or by right-clicking in thunar and choosing install.

It is VERY likely that they will work just fine in Vector, so no need to do anything else.Just install all of them.

What happened is that you extracted the .tgz package instead of installing it (I think).The libofx problem is because you're starting the grisbi slackware binary, and that was compiled with support for ofx files.

If you want, just for the kick of it, you can have a shot at compiling the source (not sure if you get kicks out of compiling source code, but hey, sometimes I do). In which case delete whatever you downloaded before, download the grisbi source package (and only that) at the top of the download page here (http://prdownloads.sourceforge.net/grisbi/grisbi-0.5.9.tar.bz2?download), extract the contents with thunar, then do exactly as I described above and you will have installed it as well.

Quote

root:# slocate libofx

Now for the searching.Slocate searches a database of the files on your system, and is very fast, provided the database is updated. To update it, do (as root):

Also, before you comment on my working as root, the other evening I apparently mis-typed my password to 'sudo su' twice and Linux would no longer let me even start that command. So, rather than log off and lose all of my windows to log on as root, I just stay here.

The way it works in vector and most other distributions (except ubuntu and the like), is:1. You don't use "sudo" (unless you actually need it and configure it properly). Forget it for now.2. You use "su" from a terminal to go to root. Type only "su" and nothing else. Insert your root password.

You become root inside a terminal, do what you need, and then close the terminal, or type exit.When you start a program like gslapt and you're asked a password, you're also starting that program as root.

3. No need to login as root in your login manager.

At least for me, this applies virtually all the time, but other people may have different needs.

I cleaned out all of the files that I had downloaded after running gslat to remove anything that might have been installed - I even took the files out of .Trash-0. Downloaded from the link you provided and extracted the tar ball. vector://home/bruce/actg/grisbi-0.5.9 root:# ./configue --prefix=/usr bash: ./configue: No such file or directoryI did verify that /usr exists and that I wasn't using the DOS \. Opps! It works better if one doesn't misspell the command!

root:# ./configure --prefix=/usr checking ... Boy! Is that make a long one! Thank you MOE-lnx. Now, all I have to do is get it to use American currency instead of European.

BTW: Thank you for letting me know what catfish does. That's one of the hard things about learning Linux, the names seem to have no bearing on what they do.

Also, I have written and compiled many small utilities in DOS but the compiler was NOT strict at all and my programs would crash with no indication of the problem when I tried making larger programs. Trying to compile with VC1.5 told me what was wrong but I couldn't figure out how to get it to make the conversion between foo[] and *foo. VC4 was worse as it would reference variables that, as far as I could see, weren't even there.

Now to get into the Networking section and find why Linux and Samba won't talk to my Win200 or Win 95 machines.