unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: Build Error in Latest Git
Date: Fri, 17 Dec 2010 12:10:45 -0500	[thread overview]
Message-ID: <AANLkTi=VRtwhcin6wa_Bj8Uo6e73XpDNQK4aGgbDHW0D@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=jffZmExWqQHDwZN=yWhzUA8xLzsTaWZSsieqy@mail.gmail.com>

After looking at this a bit more, I think it's an issue with Gnulib,
or possibly the configuration system. I'd like to report it to one of
those projects, but could someone tell me how Guile's configuration
mechanism interacts with Gnulib's? I don't really understand what is
configuring Gnulib, since it has no configure script.

Thanks,
Noah

On Wed, Dec 15, 2010 at 4:19 PM, Noah Lavine <noah.b.lavine@gmail.com> wrote:
> Mac OS X 10.6. There's some weirdness because I have two versions of
> libiconv installed - the one that comes with OS X, and one from
> Macports. They also define different symbols for the same functions -
> the regular OS X library has "_iconv_close", and the Macports one has
> "_libiconv_close". I wonder if this is a case of the configure script
> picking up one set of names and then linking with the other set.
> (Although that doesn't explain why it used to build, back when I had
> the same setup.)
>
> I've tried building with both of those libraries, using
> --with-libiconv-prefix to switch, and I get the same error. (I started
> with 'make distclean' each time.)
>
> Noah
>
> On Wed, Dec 15, 2010 at 4:02 PM, Andy Wingo <wingo@pobox.com> wrote:
>> On Wed 15 Dec 2010 07:49, Noah Lavine <noah.b.lavine@gmail.com> writes:
>>
>>> Undefined symbols:
>>>   "_iconv", referenced from:
>>
>> Odd. On what platform is this?
>>
>> Andy
>> --
>> http://wingolog.org/
>>
>



  reply	other threads:[~2010-12-17 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  6:49 Build Error in Latest Git Noah Lavine
2010-12-15 21:02 ` Andy Wingo
2010-12-15 21:19   ` Noah Lavine
2010-12-17 17:10     ` Noah Lavine [this message]
2010-12-17 18:52       ` Ludovic Courtès
2010-12-17 22:06       ` Andy Wingo
2010-12-17 22:12         ` Noah Lavine
2010-12-17 20:51     ` Ludovic Courtès
2010-12-17 18:53 ` Ludovic Courtès

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='AANLkTi=VRtwhcin6wa_Bj8Uo6e73XpDNQK4aGgbDHW0D@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=bug-guile@gnu.org \
    --cc=wingo@pobox.com \
    /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).