From: Andy Wingo <wingo@pobox.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 21:31:57 +0200 [thread overview]
Message-ID: <m34ouvdccy.fsf@pobox.com> (raw)
In-Reply-To: <87eiu07qse.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Thu, 04 Jun 2009 02:04:33 +0100")
On Thu 04 Jun 2009 03:04, Neil Jerram <neil@ossau.uklinux.net> writes:
> I built and installed libunistring this evening, to /usr/local, and
> now ./configure is failing for me at:
>
> checking size of float... configure: error: cannot compute sizeof
> (float)
I had this at one point today, as well, when I had installed
libunistring into /opt/foo/ but had my libdir wrong (/opt/foo/lib vs
/opt/foo/lib64)...
Crazy to get an error about sizeof(float). I wish unistring added its
info to UNISTRING_CFLAGS/UNISTRING_LIBS like other libraries instead of
CFLAGS so it would affect checks like this.
While we're complaining about the build :-) It seems we require gperf
now. Is that correct? Can that build-dependency be removed somehow? It
seems to be a build-time dependency, though it could be only for
maintainers.
If in fact it is only for maintainers, perhaps we should keep the
generated whatevers in git. I just had to ask the build folks at work to
add unistring as a dep, and I'm a little concerned about asking for
gperf too :P
> 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'
I think that's how my error panned out too, but for you it should work.
Maybe we should get Bruno involved, if Ludovic doesn't know anything...
> Ludo, Andy, I'm wondering why this isn't a problem for you too. Is it
> because you've installed libunistring in /usr, perhaps?
On my laptop, yes, in anticipation of someone packaging it up. Grr
unpackaged dependencies!!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-06-04 19:31 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 [this message]
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
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=m34ouvdccy.fsf@pobox.com \
--to=wingo@pobox.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).