unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: master build issue
Date: Thu, 04 Jun 2009 20:17:35 -0400	[thread overview]
Message-ID: <rmioct31qlc.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87eiu07qse.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Thu, 04 Jun 2009 02:04:33 +0100")

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]


Neil Jerram <neil@ossau.uklinux.net> writes:

> configure:52553: ccache gcc -o conftest -g -O2   conftest.c -L/usr/local/lib -lunistring -R/usr/local/lib -lgmp -lcrypt -lm -lltdl  >&5
> gcc: unrecognized option '-R/usr/local/lib'
>
> My GCC is version 4.3.2, so pretty recent.
>
> Ludo, Andy, I'm wondering why this isn't a problem for you too.  Is it
> because you've installed libunistring in /usr, perhaps?

I haven't tried it either, but it would seem prudent to verify that the
new dependency builds w/o hassle on all the places guile builds now.

I downloaded it and built on NetBSD/i386 5.0 with
--prefix=/usr/y0/libunistring, and it seems to build fine with no
warnings that I noticed as it scrolled by.  Looking at the package, it
looks quite well baked.  Despite my initial negative reaction to new
dependencies, this package seems exceptionally well done for one that
has (to me) appeared suddenly.  I did get one failure in make check:

test-striconveh.c:389: assertion failed
Jun  4 20:16:24 foo /netbsd: pid 28621 (test-striconveh), uid 10853: exited on signal 6 (core dumped)
[1]   Abort trap (core dumped) EXEEXT="" LOCALE...
FAIL: test-striconveh

but the rest were ok.

I can add it to pkgsrc, and that should fix my master build.


[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]

  parent reply	other threads:[~2009-06-05  0:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  1:04 master build issue Neil Jerram
2009-06-04 19:31 ` Andy Wingo
2009-06-04 20:38   ` Neil Jerram
2009-06-04 20:49     ` Neil Jerram
2009-06-04 21:42     ` Neil Jerram
2009-06-05  0:17 ` Greg Troxel [this message]
2009-06-05  3:05   ` Mike Gran
2009-06-05 22:02   ` Neil Jerram
2009-06-06 13:14 ` 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=rmioct31qlc.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).