Re: Broken shared libraries in OS X

[Julio Merino <jmmv84%gmail.com@localhost>]

On Sun, Dec 20, 2009 at 11:32 AM, Matthias Scheler 
<tron%zhadum.org.uk@localhost> wrote:
> On Sat, Dec 19, 2009 at 01:01:29PM +0000, Julio Merino wrote:
>> See attached patch; will submit later.
>
> This fixes my problems, thanks a lot.

You're welcome.

> There is however a small problem in your patch:
>
> -BUILD_DEPENDS+=        f2c>20090411:../../lang/f2c # translator
> +BUILD_DEPENDS+=        f2c>20090411nb2:../../lang/f2c # translator

Yeah, I caught that too when using pkgsrc right after changing the
file (and after sending the email) :)

> This should either read "f2c>20090411nb1" or "f2c>=20090411nb2".
>
>> I'm not sure if the PKGREVISION changes are good enough.
>
> You should also bump "LIBTOOL_REQD" in "pkgsrc/mk/bsd.pkg.use.mk".

OK, done!

I'm still wondering what the right solution to this could be.  First
of all, why are we setting CPP to gcc in OS X?  Why not use cpp?  I
see the following in Darwin.mk:

# Use the GNU cpp, not the OS X cpp, don't look in "/usr/local/include"
# before "/usr/include".
CPP_PRECOMP_FLAGS?=     -no-cpp-precomp -isystem /usr/include

But it turns out /usr/bin/cpp is just a shell wrapper around gcc.  And
the reason cpp works and gcc doesn't is because cpp explicitly sets
the language of the source file to C, thus bypassing the .F suffix and
skipping the Fortran check.

-- 
Julio Merino