On 4/21/06, linux23dragon <[EMAIL PROTECTED]> wrote: > > That did the trick Dan. Thanks. > It looks like I have to learn up on editing or configuring my own Makefiles, > when situations like this pop up from time to time :)
Here's a really good thing to know about Makefiles. The variables, like "LIB = -lGL -lXrender", can be set at the command line as arguments to make. So, if you'd run "make" during the nvidia build instead of running a shell script which called make, you could have done make LIB="-L/opt/lib -lGL -lXrender" Possibly just `make LIB=-L/opt/lib' would have worked in that case too since the Makefile variable is defined as LIB +=, but I'm not an expert in make. I wouldn't worry about it much, though. Most build systems are designed specifically to handle the fact that people install things with different prefixes. You probably won't have to do much editing of Makefiles. However, X is something of a special case. It's historically been installed in /usr/X11R6, so some builds hard-code that location. > Do you think it would be a good idea for me to create a /usr/X11R6/lib link > to /opt/lib? I wouldn't bother. As above, most build systems will just handle it. Only a few rare cases won't, and they should be noted in the BLFS (SVN) book since we test for not installing in /usr/X11R6 now. The libtool archives (.la files) don't matter that much, either. RedHat goes so far as to delete them all. I'm not an expert in libtool, though, so I can't really speculate about them. I think you'll be fine with your setup as is for 90% of packages. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
