-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/13/10 4:23 AM, Tim Harder wrote: > Hey, > > I am trying to install ffmpeg from the fink repository, but it > unfortunately fails when trying to build > one of the dependencies, namely xmkmf package.
The fact that you're ultimately trying to install ffmpeg isn't particularly relevant to _this_ error. > It looks like the error message is actually coming from the imake > package, which I guess is part of > xmkmf. I could get it to configure manually, but wasn't able to get fink > to do it, nor to except that > I had it install manually .. > > Error message is: > ... > checking dependency style of gcc... gcc3 > checking for a BSD-compatible install... /usr/bin/install -c > checking how to run the C preprocessor... gcc -E > checking for sed... /usr/bin/sed > checking for cpp... /sw/bin/cpp > checking if /sw/bin/cpp requires -undef... gcc: no input files > gcc: no input files > configure: error: /sw/bin/cpp defines unix with or without -undef. I > don't know what to do. > ### execution of /var/tmp/tmp.2.W6maOZ failed, exit code 1 > Removing runtime build-lock... > Removing build-lock package... > /sw/bin/dpkg-lockwait -r fink-buildlock-xmkmf-1.0.2-1002 > (Reading database ... 83446 files and directories currently installed.) > Removing fink-buildlock-xmkmf-1.0.2-1002 ... > Failed: phase compiling: xmkmf-1.0.2-1002 failed > ... > > I am running 10.6.3 on a late 2007 MacBookPro. The vintage of your machine is also not particularly relevant. What would potentially have been more relevant would be whether you're on a 32-bit or 64-bit Fink setup--but it probably doesn't matter in this case. > My default compiler is gcc4.4. > > I would be grateful for any hints or tips. > > Thanks > Tim > > When you say that your default compiler is gcc4.4, does this mean that you made symbolic links to fink's gcc4.4 (or another installation) including the /sw/bin/cpp noted above? That would be what is causing your error. We deliberately _don't_ put the FSF gcc tools from fink's gcc4N packages in the path as "cpp", "gcc", "g++", etc. because they don't work identically to the corresponding tools from Xcode, and Fink's packages for the most part assume the Xcode compilers are what will be used to build them. And those that actually use e.g. gcc44 are set up appropriately to do so without additional modifications. Get rid of those symlinks. If you really want e.g. "gcc" to point to Fink's gcc4.4, then an option would be to have that in $HOME/bin, and have $HOME/bin in your PATH. Fink tries not to use anything from your environment apart from what it sets itself, and so it will see /usr/bin/gcc as "gcc". - -- Alexander Hansen Fink User Liaison -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvr4JYACgkQB8UpO3rKjQ98dACdGqPjSzh2SkjjK5AP7mpef9uf nBMAn09pyVvNkJWmz20U8S9QF9QL1uce =uGPi -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
