Re: gnucash fails on Darwin

[Greg Troxel <gdt%ir.bbn.com@localhost>]

I have redirected to pkgsrc-users as there is so far no reason to think
there is a pkgsrc infrastructure issue involved.

  /usr/bin/ld: Undefined symbols:
  _scm_boot_guile
  _scm_c_eval_string
  _scm_c_resolve_module
  _scm_c_use_module
  _scm_call_2
  _scm_set_current_module
  collect2: ld returned 1 exit status
  gnumake[4]: *** [gnucash-bin] Error 1
  gnumake[3]: *** [all-recursive] Error 1
  gnumake[2]: *** [all-recursive] Error 1
  gnumake[1]: *** [all-recursive] Error 1
  gnumake: *** [all] Error 2
  *** Error code 2

  Stop.
  bmake: stopped in /usr/pkgsrc/finance/gnucash

You left out the actual link line But, this really looks like the guile
library not being found.  Feel free to send the entire build log
(starting from make clean) to me and wiz@ privately.

A common source of problems on Mac OS X with guile is that Darwin uses a
different way of resolving shared libraries than NetBSD or most Linux
systems.

NetBSD: -rpath

Many linux: put libs in /usr/lib or use LD_LIBRARY_PATH (maybe -rpath)

Darwin: use -L at link time and find path and put that whole path in the
binary for the library

The problem comes with using dlopen to link modules; that seems to use
the stored rpath on NetBSD and LD_LIBRARY_PATH, but something needs
spiffing up there for Darwin.  From my notes:

pkg/33665 - feedback serious medium priority sw-bug
        g-wrap Makefile needs to set LTDL_LIBRARY_PATH
        http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=33665
# Looks like -rpath/search issue

pkg/36975 - open serious medium priority sw-bug
        devel/guile-lib fails to build on Darwin
        http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=36975
# Looks like -rpath/search issue

So, you or someone else with a mac will have to debug the link process.

It probably would help to look at the gnucash-user archives to see how
other people on the mac are getting this to work.  There seems to be a
lot of trouble with slib on Linux, but you don't seem to have that
problem, or at least not yet.