F.A.Q. - 7. Compile Problems - Specific Packages

Q7.1: A package fails to build with errors involving sed.

A: This can happen if your login script (e.g. ~/.cshrc) does something that writes to the terminal, e.g "echo Hello" or xttitle. To get rid of the problem, the easy solution is to comment out the offending lines.

If you want to keep the echo, then you can do something like the following:

if ( $?prompt) then 
	echo Hello 

Q7.2: I can't install gtk+2 on OS 10.5

A: Typically this involves missing libraries, such as: /usr/X11/lib/libXrandr.2.0.0.dylib or /usr/X11/lib/libXdamage.1.1.0.dylib (or other versions of libraries in /usr/X11/lib/).

The current wisdom on the best fix for such an issue is to install Xcode 3.1.3 or later.

Q7.3: I get errors involving _Perl_Gthr_key_ptr when installing an xml-sax-pm package

A: If you get an error that looks similar to:

update-perl5123-sax-parsers: adding Perl SAX parser
module info file of XML::SAX::Expat...
dyld: lazy symbol binding failed: Symbol not found:
  Referenced from: /opt/sw/lib/perl5/5.12.3/darwin-
  Expected in: flat namespace

this is usually due to a build picking up a different perl5.12 executable than the system's (or perl5.10.0, or perl5.8.8, depending on your OS version).

You can verify this by running:

type -a perl5.12

if you're using the bash shell, or

where perl5.12

if you're using tcsh (and replace perl5.12 appropriately for your situation).

To work around this issue, temporarily rename the non-system perl5.12 while you are building with Fink.

Q7.4: I can't build a Fink gcc package due to "conflicting types for 'pointer_t'"

A: Such errors typically look like:

error: conflicting types for 'pointer_t'
note: previous declaration of 'pointer_t' was here
make[3]: *** [fortran/module.o] Error 1

This is associated with someone having unnecessarily added a /usr/include/malloc.h->/usr/include/malloc/malloc.h symlink. Get rid of that.

On OS X, #include <stdlib.h> should normally be used in place of #include <malloc.h>.

Q7.5: I'm having issues with a package that isn't listed here.

A: Since package problems tend to be transient, we've decided to put them up on the Fink wiki. Check the Package issues page.

Next: 8. Package Usage Problems - General