Cant find config files .

[Janet]

I have a list of 12 progs that I have unsucessfully tried to install. and a pattern is emerging.

Ive noticed with about five of them that the prog cant find the config file or the autoconfig or the config file isnt where the prog is looking for it.

So my question is this. When a prog is installed do config files normally install to a particular directory ?? Can anyone suggest why I could be having this problem ?? Im thinking maybe some thing is wrong with my path but Ive posted it to this board before and Im told its OK. Should I be creating links to correct these errors ??

[DMR]

Janet,

I don't have a definitive answer, but:

There isn't a single directory into which programs install their config files, but /etc or a subdir of /etc is where some programs put their configs (XFree86 and Samba, for example). If the program creates a directory for itself, the config may reside there.

I've found that some program installations look for a directory or file which, on my distro, either doesn't exist or is in a different location. Sometimes creating a symlink (which points to the actual location) in the location the program wants does the trick. I've had similar problems when compiling from source, where the makefile/source code seem to have been written for a different distro, and pathing/file location references differ from my directory structure. In those cases, it was neccessary to edit the references in the source code to point
to the correct locations on my system.

BTW- How are you installing the programs? RPM? Compiling from source?
Pehaps if you posted the names of the programs and the exact errors each gives you, someone here might be able to distill an answer from that info.

[ 08 September 2001: Message edited by: DMR ]

[Janet]

Thanks DMR,
I was hoping Id missed something but youve confirmed what I thought. Im not technical at all being a 7 mth linux user and a recent convert from Windows. So its down to links and setting in the configure file.
When you say edit references could you be a little more specific. Could you give an example of what you might change. I assume you are talking about a config file which is run first when installing the prog. So you would change the settings there and then run ./configure, make, make install right ??
Or would you just change them after the install is finished..
Thanks again.

On your other suggestion to post details to this board I have tried but on this config file problem havnt been able to get to the heart of the problem so Im trying a more general approach.

[DMR]

O.K., I think I've got a better idea of where you're coming from now. I wasn't sure if you were referring to the configuration files used by programs once they are installed (such as /etc/smb.conf for Samba), or the "configure" scripts used when compiling . The "autoconfig" reference ("autoconf" perhaps?) should have clued me in; your problems relate to compiling from source, right?

I'm about to be abducted by friends of mine who think that my Saturday night would be better spent going out to hear some music, and I think I agree. I'll repost with more info tomorrow morning.

[Janet]

Thanks yr post DMR.Hope you had a good night out.
I am getting messages after installation (from source) saying that the prog cant find the config file. The prog is looking for it but cant find it. In one case it cant find the autoconfig and in 3 others it cant find the programname.conf file.
I have found the .conf file for some of the progs in the /home/programname directory so I cant figure out why the prog cant see it.
Would you create a symlink in this case ??
Also as mentioned in a previous post could you expand on editing refs in the source code.
Thanks again.

[DMR]

I'll expand on all of the above after I expand on a few hours of sleep (and yes, it was a "good night out").

[DMR]

As far as altering the Makefiles/source goes: In my case it related to the program(s) not looking for libraries/header files in the right location, but that doesn't seem to be your issue. The basic idea is that by reading the contents of a source file or Makefile, you can sometimes get a clue as to why a compile fails. For instance, you might find the pathing to a library directory to be incorrect for your distro, or that an "include" line references a header (.h) file not present on your box. Information like that can point you in the direction of a fix. What you need to look for is often problem-specific, so I can't really be more definite than that. Also keep in mind that I couldn't program my way out of a coffee cup, so if my answer sounds vague, it's only due to lack of knowledge on my part. ;)

In terms of the .conf files, you can put a link (or a copy of the file itself, for that matter) in the directory the program is expecting, but the problem is that you have to know what that directory is. Have you read the .conf files? Sometimes they contain helpful comments relating to their usage and structure. Also, sometimes you have to create the config file by hand. The one you find in the program's home directory is only provided as a sample or template, and the documentation should state as much. It should also tell you how to create the "real" config file, and where that file should reside.
Without more specifics such as the program names and the names of their associated .conf files, I'm afraid that's all I can suggest right now; I hope it helps.