From: Jerome Guitton <guitton@adacore.com>
To: Adam Nemet <anemet@lnxw.com>
Cc: Daniel Jacobowitz <drow@false.org>, binutils@sources.redhat.com
Subject: Re: [RFA] fix compilation warning in libiberty.h
Date: Tue, 26 Apr 2005 10:40:00 -0000 [thread overview]
Message-ID: <20050426102746.GA29592@adacore.com> (raw)
In-Reply-To: <17001.33583.831885.170218@anemet1.lynx.com>
Adam Nemet (anemet@lnxw.com):
> The checked in version was:
>
> AC_CHECK_DECLS(basename, , , [#include "sysdep.h"])
>
> How is this supposed to find sysdep.h?
It makes me think that I did the same mistake in opcodes. I checked in
the following patch, as obvious. Hopefully everything I broke recently
is now fixed. Thanks for your patience, all of you.
2005-04-26 Jerome Guitton <guitton@gnat.com>
* configure.in: Fix the check for basename declaration.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/opcodes/configure.in,v
retrieving revision 1.55
diff -u -r1.55 configure.in
--- configure.in 14 Apr 2005 09:48:22 -0000 1.55
+++ configure.in 26 Apr 2005 10:14:18 -0000
@@ -72,7 +72,7 @@
AC_CHECK_HEADERS(string.h strings.h stdlib.h)
-AC_CHECK_DECLS(basename, , , [#include "sysdep.h"])
+AC_CHECK_DECLS(basename)
cgen_maint=no
cgendir='$(srcdir)/../cgen'
next prev parent reply other threads:[~2005-04-26 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 15:51 Jerome Guitton
2005-03-31 16:01 ` Daniel Jacobowitz
2005-03-31 17:08 ` Jerome Guitton
2005-03-31 17:28 ` Daniel Jacobowitz
2005-03-31 17:38 ` Jerome Guitton
2005-04-22 23:03 ` Adam Nemet
2005-04-25 1:44 ` Daniel Jacobowitz
2005-04-25 4:51 ` Adam Nemet
2005-04-26 10:40 ` Jerome Guitton [this message]
2005-03-31 21:16 ` Maciej W. Rozycki
2005-03-31 23:29 ` Jerome Guitton
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 19:54 [RFA] Fix " Joel Brobecker
2005-03-18 19:56 ` Daniel Jacobowitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050426102746.GA29592@adacore.com \
--to=guitton@adacore.com \
--cc=anemet@lnxw.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.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).