-- checking for fink

Ethan Blanton elb at
Fri Mar 28 21:01:16 EDT 2008

David Fang spake unto us the following wisdom:
> >> 	The following excerpt of, checking for a hard-coded
> >>default path for fink is not recommended, and should be removed.
> >
> >What do you recommend, instead?
> 	Either remove the hard-coded check for fink, or automatically take 
> $prefix and append the include/ lib/ to CPPFLAGS and LDFLAGS.  The latter 
> would cover the cases where the user desires to install in the same prefix 
> used by [favorite package manager], whatever it may be.  It's a tradeoff 
> between flexibility and convenience.

Oh ... I think you're confused.  This isn't for building *from* fink.
We expect fink itself to provide proper CFLAGS and LDFLAGS.  This is
for people building by hand on a Mac which has fink installed, and
Pidgin dependencies provided by fink.

> I understand the motivation for the shortcut check.
> But I also wanted to point out that people who happen to use fink (in /sw) 
> and say, macports, might be surprised at to find building against /sw even 
> after options for other paths have been specified.

This is a valid point; however, that particular check was added to
stem the flow of users asking why Pidgin wouldn't build on their OSX
box, even though they had installed the proper dependencies in fink.
People who don't fall under this category can hopefully figure things


The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <>

More information about the Devel mailing list