From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Eliminate warnings about snprintf declaration
Date: Fri, 20 May 2005 14:16:00 -0000 [thread overview]
Message-ID: <01c55d34$Blat.v2.4$78a096c0@zahav.net.il> (raw)
In-Reply-To: <20050515170435.GB11855@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 15 May 2005 13:04:35 -0400)
> Date: Sun, 15 May 2005 13:04:35 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, gcc-patches@gcc.gnu.org,
> gdb-patches@sourceware.org, binutils@sourceware.org
>
> > > gdb/ChangeLog:
> > > 2005-05-14 Eli Zaretskii <eliz@gnu.org>
> > >
> > > * configure.ac: Add snprintf and vsnprintf to AC_CHECK_DECLS.
> >
> > I can't approve this one, but it looks fine to me.
>
> Eli can approve it himself; or I will :-) Same comment as above
> applies; please mention configure.
It turns out I don't know how to regenerate configure and config.in.
I looked everywhere for some dependency in some Makefile.in or for
something similar that will show me which commands are to be used for
that and in what way, but failed to find anything. I tried to run
autoconf and autoheader, but the resultant config.in misses quite a
few undef's, like HAVE_VALUES_H and HAVE_STRCHR, so I guess I didn't
invoke it correctly.
So could someone please educate me: how should I invoke autoconf and
autoheader to produce gdb/configure and gdb/config.in, what input
files are needed (use by autoconf and autoheader) for this, and where
(in what makefile or script) are the rules to do that spelled out?
TIA
next prev parent reply other threads:[~2005-05-20 12:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01c4c990$Blat.v2.2.2$887ec720@zahav.net.il>
[not found] ` <41994B9D.9080809@gnu.org>
2005-05-12 15:08 ` Eli Zaretskii
2005-05-12 15:33 ` Daniel Jacobowitz
2005-05-12 15:45 ` Eli Zaretskii
2005-05-12 15:53 ` Daniel Jacobowitz
2005-05-12 16:25 ` Eli Zaretskii
2005-05-12 18:07 ` Daniel Jacobowitz
2005-05-12 20:48 ` Eli Zaretskii
2005-05-12 21:05 ` Daniel Jacobowitz
2005-05-12 21:27 ` DJ Delorie
2005-05-14 10:23 ` Eli Zaretskii
2005-05-14 16:39 ` Daniel Jacobowitz
2005-05-14 19:43 ` Eli Zaretskii
2005-05-15 16:31 ` Ian Lance Taylor
2005-05-15 17:15 ` Daniel Jacobowitz
2005-05-15 19:48 ` Eli Zaretskii
2005-05-15 20:21 ` Daniel Jacobowitz
2005-05-20 12:42 ` Eli Zaretskii
2005-05-20 14:16 ` Eli Zaretskii [this message]
2005-05-20 14:34 ` Andreas Schwab
2005-05-20 15:02 ` Eli Zaretskii
2005-05-20 15:06 ` Andreas Schwab
2005-05-20 18:24 ` Eli Zaretskii
2005-05-20 18:26 ` Eli Zaretskii
2005-05-20 20:47 ` Daniel Jacobowitz
2005-05-20 22:16 ` Eli Zaretskii
2005-05-22 14:54 ` Daniel Jacobowitz
2005-05-22 17:11 ` Andreas Schwab
2005-05-15 19:55 ` Eli Zaretskii
2005-05-12 16:01 ` Ian Lance Taylor
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='01c55d34$Blat.v2.4$78a096c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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