Alexander Hansen wrote: > On 3/15/10 12:14 PM, James Mckenzie wrote: > > Alexander Hansen <[email protected]> wrote: > >> On 3/15/10 10:24 AM, James Mckenzie wrote: > >>> Alexander Hansen <[email protected]> wrote: > >>>> > >>>> On 3/14/10 2:24 PM, James McKenzie wrote: > >>>>> When attempting to update dbus from 1.2.6-1 to 1.2.16-14 on MacOSX > >>>>> 10.5.8 using Fink's supplied gcc-4.2 I get the following: > >>>>> > >>>> Wrong. It's not supposed to use Fink's gcc42. It uses Apple's > gcc-4.2 > >>> >from Xcode (on 10.5 and later). If you did any manual hacking > around to > >>>> have it use Fink's gcc-4.2, then that could present a problem. > >>>> > >>>>> checking for library containing strerror... none required > >>>>> checking how to run the C preprocessor... cpp-4.2 > >>>>> configure: error: C preprocessor "cpp-4.2" fails sanity check > >>>>> See `config.log' for more details. > >>>>> ### execution of /var/tmp/tmp.1.DKb9ZM failed, exit code 1 > >>>>> Removing runtime build-lock... > >>>>> Removing build-lock package... > >>>>> /sw/bin/dpkg-lockwait -r fink-buildlock-dbus-1.2.16-4 > >>>>> > >>>>> What should I do to fix this. > >>>>> > >>>>> Also, this is not on the Wiki as a current package problem. > >>>>> > >>>>> Thank you. > >>>>> > >>>>> James McKenzie > >>>>> > >>>>> > >>>>> > >>>> Look in the config.log file, as noted above, and go to the line which > >>>> mentions "preprocessor". That will indicate what command is actually > >>>> being run, and possibly give a more verbose error message to indicate > >>>> what's going on. > >>> Thank you Alexander. The error message seems to state that the > preprocessor is not even installed. > >>> > >>> Will look at the log since I also installed gcc-4.3 as well. > >>> > >>> James McKenzie > >>> > >> That shouldn't matter, because the package should explicitly point at > >> Apple's gcc-4.2, rather than just looking for any old "gcc" or > "gcc-4.2". > > I don't have Apple's gcc-4.2, only Fink's. Apple's gcc is 4.0.1. > Does this mean I have to update XCode? > > > James McKenzie > > > It doesn't appear to be mandatory in the package description, which > misled me. What may be going on is as follows (from the CompileScript): > > #!/bin/sh -ev > > if [ -x /usr/bin/gcc-4.2 ]; then > export CC=gcc-4.2 > export CXX=g++-4.2 > export CPP=cpp-4.2 > fi > ... > > I.e. it uses /usr/bin/gcc-4.2 if present (new enough Xcode on 10.5, and > 10.6) > > If you have a /usr/bin/gcc-4.2 on your system (maybe as a symbolic link > to /sw/bin/gcc-4.2) then this could potentially derail the build. > It is. cpp-4.2 is NOT present.
You are correct in that this may be the cause of the failure. James McKenzie ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
