On Mar 24, 2010, at 13:52, LuKreme wrote: > On 24-Mar-2010, at 12:24, Ryan Schmidt wrote: > >> On Mar 24, 2010, at 13:17, LuKreme wrote: >> >>> Is there a simple way to point my ports to install everything in /usr/local >>> instead of /opt/local >> >> You cannot install MacPorts in /usr/local. > > To be clear, I do not want to install MAcPorts in /usr/local, it is fine in > /opt/local. But when I build a specific port i want THAT to be built and > installed into /usr/local/
Definitely not; ports installed by MacPorts are generally hard-coded to work only in the MacPorts install prefix. The only time you can change this is at the time when you configure and install MacPorts, before any ports have been installed. > having everything in /otp/local makes it very annoying to try and build > things against MacPorts that are not already in MacPorts. For example, I > notice that slrn that I built did not find the existing uudeview install, and > everything I try to get slrn's configure to see it has failed. If I could > simply build uudeview where it is expected to be, then I could build slrn > with the options I want. You are talking about the slrn and uudeview ports in MacPorts, or about building these from source by hand? If the former, file bugs if they don't work. If the latter, why not use the ports? To build software manually against dependencies already installed by MacPorts, you may have to set CFLAGS, CPPFLAGS, CXXFLAGS, and LDFLAGS like MacPorts does (see all the variables MacPorts sets in the configure phase by using debug output: sudo port -d configure someport). Or, you can try C_INCLUDE_PATH and LIBRARY_PATH instead. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
