From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: build errors: 9172 Broken pipe and 9173 Segmentation fault
Date: Mon, 18 Apr 2011 23:16:09 +0200 [thread overview]
Message-ID: <8739lf8dly.fsf@gnu.org> (raw)
In-Reply-To: 87mxjp4ncv.fsf@netris.org
Hi Mark,
Mark H Weaver <mhw@netris.org> writes:
> Douglas and I did some investigation over this over IRC, and discovered
> that this problem is not within Guile. On his platform (uClibc on
> PowerPC, using GCC 4.6.0 and libunistring-0.9.3) u32_conv_from_encoding
> does not work correctly, as demonstrated by the attached minimal C
> program, which is not linked with Guile.
Great. Did you report it on bug-libunistring?
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-04-18 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 1:05 build errors: 9172 Broken pipe and 9173 Segmentation fault Douglas Mencken
2011-03-24 1:45 ` Neil Jerram
[not found] ` <AANLkTindvcPaJ4qYr7OCvWbitFCzb2oALNO1ya6x0_Y4@mail.gmail.com>
2011-03-29 17:07 ` Douglas Mencken
2011-04-01 9:08 ` Andy Wingo
2011-04-16 11:19 ` Douglas Mencken
2011-04-16 16:01 ` Andy Wingo
2011-04-17 2:34 ` Mark H Weaver
2011-04-18 21:16 ` Ludovic Courtès [this message]
2011-04-18 23:45 ` Mark H Weaver
2011-04-21 10:28 ` Andy Wingo
2011-04-17 2:38 ` Mark H Weaver
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=8739lf8dly.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@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).