Subject: Re: libraries & security (was Mosaic compile)
To: Bill Studenmund <wrstuden@loki.stanford.edu>
From: T. Sean (Theo) Schulze <71410.25@compuserve.com>
List: port-mac68k
Date: 12/11/1997 16:12:17
On 12/10/97 12:57 AM, Bill Studenmund at wrstuden@loki.stanford.edu wrote:

>> >ld.so.conf tells the system where libraries are, not where header files 
>> >are.  Remove any changes you made to ld.so.conf.  (Incidentally, I don't 
>> >think I've ever had to modify the ld.so.conf file.)  To tell the
>> >compiler 
>> >where libraries are (you can add this in the Makefile), add 
>> >-L/dir/where/special/libs/are to the line where it is looking for the 
>> >library.
>> >
>> Well, I had to edit /etc/ld.so.conf to get X to work (as per the FAQ).  
>> When I added /usr/X11R6/include it was the first entry.  I have now added 
>> /usr/lib, /usr/include, /usr/local/include and /usr/local/lib to 
>> /etc/ld.so.conf.  I know there is a security issue with library files 
>> (which, even after reading man ld.so.conf I am not completely clear on), 
>> but other than that, is there another issue?  Can it screw something up?
>
>As I understand it, ld.so.conf does need to contain all the library
>directories, not just non-standard ones you want to add. It should NOT
>contain includes directories, though.
>

OK, I'll take the includes out.  One thing that has me going though.  If 
I can find the includes I need using find, why can't configure find them? 
 Couldn't someone right a configure that actually finds things like 
includes and that could be given a flag to ask the user if it had found 
the ones it was supposed to find?  (If you're waiting for me to write it, 
it might be a while :-)

Cheers,

Sean.


                 T. Sean (Theo) Schulze
71410.25@compuserve.com            TSSchulze@aol.com
****************************************************
Custom reconciles us to everything.  -- Edmund Burke