Alejandro Guerrieri schrieb: > Yes, of course, but it's unnecessarily more complex and tend to confuse > people, when it can be easily avoided. > > The goal of a ./configure script is to automatically find and link all > necessary objects for you. > > /opt/local is a very common location on Mac OSX and should be searched > by default IMHO. The patch only adds those folders when it detects a > darwin architecture, it doesn't affect other platforms at all.
hmmm, I'm sort of agreeing to Alan here. We should tend to: a) keep only real System V and BSD4.3 (that's the old school for you folks that don't know ;) style standard lookup paths. b) all others places should be inherited via CFLAGS and LDFLAGS env variables in the ./configure call, or via the configure own option switches. So the big question is: Is /opt/local really that common under MacOS X? Any others that run MacOS that can comment? Stipe -- ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org -------------------------------------------------------------------
