From: Andy Wingo <wingo@pobox.com>
To: "Stewart\, Adam James" <ajstewart@anl.gov>
Cc: "23911-done@debbugs.gnu.org" <23911@debbugs.gnu.org>
Subject: bug#23911: Cat broken pipe segmentation fault when building Guile
Date: Thu, 14 Jul 2016 12:11:30 +0200 [thread overview]
Message-ID: <87bn201qct.fsf@pobox.com> (raw)
In-Reply-To: <9F5501637440B04B9DE4C86279C60B6E4A57541D@PAYTON.anl.gov> (Adam James Stewart's message of "Wed, 13 Jul 2016 20:45:33 +0000")
On Wed 13 Jul 2016 22:45, "Stewart, Adam James" <ajstewart@anl.gov> writes:
> I finally have success! I think the problem was that I was building
> guile, gettext, and libunistring with my own libiconv. When I stopped
> building with libiconv and just used the system version, everything
> worked. The build passes make check and make installcheck now.
>
> I'm not sure if there's a way for guile to detect whether or not
> libiconv is built properly. It would be nice if configure crashed with
> a useful error message instead of this core dump. But I'm satisfied
> now. Thanks for your help!
Yeah what a mess! We have historically had problems making sure that
libunistring was compiled with iconv support, but I didn't hear about
this particular one. Strange. I guess I will close this one though :)
Cheers,
Andy
next prev parent reply other threads:[~2016-07-14 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 16:03 bug#23911: Cat broken pipe segmentation fault when building Guile Stewart, Adam James
2016-07-10 12:42 ` Andy Wingo
[not found] ` <9F5501637440B04B9DE4C86279C60B6E4A574FC1@PAYTON.anl.gov>
2016-07-11 15:55 ` Andy Wingo
[not found] ` <9F5501637440B04B9DE4C86279C60B6E4A575001@PAYTON.anl.gov>
2016-07-11 19:35 ` Andy Wingo
2016-07-13 17:00 ` Stewart, Adam James
2016-07-13 20:45 ` Stewart, Adam James
2016-07-14 10:11 ` Andy Wingo [this message]
2017-03-01 8:12 ` 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=87bn201qct.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=23911@debbugs.gnu.org \
--cc=ajstewart@anl.gov \
/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).