From: Jay <jay.krell@cornell.edu>
To: <bug-guile@gnu.org>
Subject: configure vs. build with different switches leads to breaks
Date: Sat, 8 Nov 2008 08:03:20 +0000 [thread overview]
Message-ID: <COL101-W3215A72EC3FE85F31402C8E6180@phx.gbl> (raw)
Guile failed to build for me, I forget what system, either Irix or OpenBSD, for
the following reason.
It goes and looks for some functions, like isnan or isnanf I think,
with autoconf:
compiles this program:
#include
int main()
{
do something with isnan
}
it compiles ok.
Later on it builds some similar code of its own, but this time with -Werror and
either -Wall or -Wmissing-prototypes. The function in question is not prototyped
in math.h, nor whatever else is #included.
I worked around by removing -Werror from the Makefile.
This seems like a general class of bug -- configure one way, build another.
(That sounds like a user error, but isn't, it is what is done automatically.)
Later on the build core dumps.
I haven't figured out why.
- Jay
next reply other threads:[~2008-11-08 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 8:03 Jay [this message]
2008-11-19 21:44 ` configure vs. build with different switches leads to breaks 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=COL101-W3215A72EC3FE85F31402C8E6180@phx.gbl \
--to=jay.krell@cornell.edu \
--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).