unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Jens Bauer <jens-guile-bug@plustv.dk>
To: 24631@debbugs.gnu.org
Subject: bug#24631: Mac OS X 10.5.8: build error, undefined symbols
Date: Thu, 6 Oct 2016 23:07:08 +0200	[thread overview]
Message-ID: <20161006230708020209.79856bb1@plustv.dk> (raw)

I'm trying to build autogen on Mac OS X 10.5.8.
Building all dependencies goes alright until I'm building guile.
I've built all libraries as static libraries and placed them in /opt, mostly because I don't want gmp to be shared.

Here's my build-recipe. "dlxb" means "download, extract and build", the arguments are passed to configure from package's own build directory:
--8<-----8<-----8<-----
dlxb gmp-5.1.3.tar.bz2 --disable-shared --prefix=/opt
dlxb libunistring-0.9.6.tar.gz --disable-shared --prefix=/opt
dlxb libffi-3.2.1.tar.gz --disable-shared --prefix=/opt

dlxb libatomic_ops-7.4.4.tar.gz --disable-shared --prefix=/opt
dlxb gc-7.6.0.tar.gz --disable-shared --prefix=/opt

dlxb guile-2.0.12.tar.gz --disable-shared --with-libgmp-prefix=/opt --with-libunistring-prefix=/opt --prefix=/opt
-->8----->8----->8-----

Here's the last lines of the output:
--8<-----8<-----8<-----
ranlib: file: .libs/libguile-2.0.a(unistd.o) has no symbols
ranlib: file: .libs/libguile-2.0.a(wctype-h.o) has no symbols
  CCLD     guile
Undefined symbols:
  "_CFRelease", referenced from:
      _libunistring_gl_locale_name_default in libunistring.a(localename.o)
  "_CFLocaleCopyCurrent", referenced from:
      _libunistring_gl_locale_name_default in libunistring.a(localename.o)
  "_CFLocaleGetIdentifier", referenced from:
      _libunistring_gl_locale_name_default in libunistring.a(localename.o)
  "_CFStringGetCString", referenced from:
      _libunistring_gl_locale_name_default in libunistring.a(localename.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[3]: *** [guile] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Failed (guile) 
-->8----->8----->8-----

-As you see, it's a linker error, and it means that the CoreFoundation framework is not linked.
The error might be related to libunistring referencing the mentioned symbols.

I've searched the net and come across only very few similar problems.
This is probably the closest match:
<http://stackoverflow.com/questions/13683581/undefined-symbols-when-trying-to-compile-rtaudio>

When I look at the Makefile in the build directory, I see lines including the CoreFoundation framework:


Makefile:INTLLIBS = -lintl -Wl,-framework -Wl,CoreFoundation
Makefile:INTL_MACOSX_LIBS = -Wl,-framework -Wl,CoreFoundation
Makefile:LIBINTL = -lintl -Wl,-framework -Wl,CoreFoundation
Makefile:LTLIBINTL = -lintl -Wl,-framework -Wl,CoreFoundation

-And in other Makefiles as well, a whole bunch in total.

Here's some relevant output from uname:
uname -m: Power Macintosh
uname -p: powerpc
uname -r: 9.8.0
uname -s: Darwin

-Yes, I'm on a PowerMac, a PowerPC based one; not an Intel based Mac. ;)
The error might show up on Intel based Macs too, though.


Love
Jens





             reply	other threads:[~2016-10-06 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 21:07 Jens Bauer [this message]
2017-03-01  9:24 ` bug#24631: Mac OS X 10.5.8: build error, undefined symbols Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161006230708020209.79856bb1@plustv.dk \
    --to=jens-guile-bug@plustv.dk \
    --cc=24631@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).