unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: John Darrington <john@darrington.wattle.id.au>
Cc: 19233@debbugs.gnu.org, request@debbugs.gnu.org
Subject: bug#19233: Errors building guile on Armv7
Date: Sun, 07 Dec 2014 11:56:53 -0500	[thread overview]
Message-ID: <87bnnf4cve.fsf@yeeloong.lan> (raw)
In-Reply-To: <20141207082420.GA32405@jocasta.intra> (John Darrington's message of "Sun, 7 Dec 2014 09:24:20 +0100")

tags 19233 + notabug
close 19233
thanks

John Darrington <john@darrington.wattle.id.au> writes:

> On Sun, Dec 07, 2014 at 12:24:42AM -0500, Mark H Weaver wrote:
[...]
>      I guess that both iconv and gdb are somewhat broken on your system.
>      
>
>
> You are right.  I was linking to the wrong libiconv

Okay.

> I think however, that your suggested work-around or something similar
> could do with pushing to the master: There is a circular dependency
> here: If iconv_open fails, guile tries to report the error using
> scm_locale_string which itself calls iconv_open ...

In the common case, the failure is not that iconv is broken, but rather
that the string contains a character that cannot be encoded in the
specified encoding.  'scm_encoding_error' raises an exception, which
could be caught and handled by user code.  If uncaught, it would print
an error message that contains only ASCII characters, so should not
fail.

What I suggested was not a workaround, but rather a temporary hack to
debug your problem.

     Thanks,
       Mark





      reply	other threads:[~2014-12-07 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 11:28 bug#19233: Errors building guile on Armv7 John Darrington
2014-12-07  5:24 ` Mark H Weaver
2014-12-07  8:24   ` John Darrington
2014-12-07 16:56     ` Mark H Weaver [this message]

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=87bnnf4cve.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=19233@debbugs.gnu.org \
    --cc=john@darrington.wattle.id.au \
    --cc=request@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).