First, the compiler needs to be told where extra headers might be found, and the linker needs to be told where extra libraries might be found.
This usually involves setenv CFLAGS = $CFLAGS -I/sw/include setenv CXXFLAGS = $CXXFLAGS -I/sw/include (for c++ programs) setenv LDFLAGS = $LDFLAGS -L/sw/lib although it's often easier to specify this via configure flags. If properly written, a configure script will be able to detect the absence of required libraries and headers. Unfortunately, some configure scripts are poorly written, and thus, passing the configure test does not guarantee a successful build. Some configure scripts expect that all X11 related libraries wil be found in the same directory. Thus, the script, upon detecting that /usr/X11R6/ contains the basic X11 related libraries, will neglect the additional widget sets (motif... for one) to be found in /sw/include. Some configure scripts, upon neglecting the extra libraries in /sw, will turn off the extra feature set. Thus running "./configure; make; sudo make install" will obscure these errors. It's best to run "configure", and carefully note if mesages such as "motif libaries not found-- X11 support will not be used" appear. It would be useful if fink supported several additional commands configure_as_fink: runs "configure" with the appropriate CFLAGS, CXXFLAGS etc. (the package would be built in /usr/local however). for package builders: (The unpacked package should be owned by the user invoking fink-- not by root) fink configure <package>: runs configure %c. Allows package developer to pick up configure warnings. fink make <package>: runs make in configured package. A third command would attempt to run "make install" as an unprivileged user. (The idea would be that /sw/src/root-packagename would be writable, but /sw would not be.) This might be useful in ensuring that the resulting dpkg is complete, and that a novice developer does not accidentally clutter up /sw with packageless files. (In the absence of a fakeroot command set , of course, the package would be broken. But I believe that partial tools will be useful for debugging packages) A fourth command or command set might generate preliminary patch files. e.g. fink configure <pn> fink make <make fails> <user makes neccesary changes> fink make <package builds> fink makeinstall <no errors found> fink make distclean fink patch fink rebuild <pn> fink validate <pn> <user cleans up patch files, and submits package for consideration> Jeremy On Sunday, August 18, 2002, at 04:21 PM, Alexander Hansen wrote: > Probably because the configuration is looking for libraries, headers, > etc. that you installed with fink in the wrong locations. Most > .configure scripts have options you can feed them like > --with-lib-dir=/sw (Check your .configure for the actual syntax--I'm not > sure if this is exactly correct). > On Sun, 2002-08-18 at 17:09, [EMAIL PROTECTED] wrote: >> Ok why is it that no matter what I try to install, the only way to >> install x11 apps on mac is through fink? >> anything that needs ./configure ; make ; make install will fail at make ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
