From: Daniel Jacobowitz <drow@false.org>
To: Adam Nemet <anemet@lnxw.com>
Cc: Jerome Guitton <guitton@adacore.com>, binutils@sources.redhat.com
Subject: Re: [RFA] fix compilation warning in libiberty.h
Date: Mon, 25 Apr 2005 01:44:00 -0000 [thread overview]
Message-ID: <20050425014421.GB18863@nevyn.them.org> (raw)
In-Reply-To: <17001.33583.831885.170218@anemet1.lynx.com>
On Fri, Apr 22, 2005 at 04:05:19PM -0700, Adam Nemet wrote:
> Daniel Jacobowitz writes:
> > On Thu, Mar 31, 2005 at 03:27:34PM +0200, Jerome Guitton wrote:
> >> +AC_MSG_CHECKING(for a declaration for basename)
> >> +AC_CACHE_VAL(bfd_cv_decl_basename,
> >> +[AC_TRY_COMPILE([#include "sysdep.h"],
> >> +[#ifndef basename
> >
> > Can't this be just AC_CHECK_DECLS(basename)?
>
> The checked in version was:
>
> AC_CHECK_DECLS(basename, , , [#include "sysdep.h"])
>
> How is this supposed to find sysdep.h? I am getting:
>
> $ grep -C basename bfd/config.log
> configure:9522: $? = 0
> configure:9534: result: yes
> configure:9545: checking whether basename is declared
> configure:9570: gcc -c -g -O2 conftest.c >&5
> conftest.c:73:20: sysdep.h: No such file or directory
This should be fixed as of Wednesday; do you still see the problem?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-25 1:44 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 [this message]
2005-04-25 4:51 ` Adam Nemet
2005-04-26 10:40 ` Jerome Guitton
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=20050425014421.GB18863@nevyn.them.org \
--to=drow@false.org \
--cc=anemet@lnxw.com \
--cc=binutils@sources.redhat.com \
--cc=guitton@adacore.com \
/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).