This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] Eliminate warnings about snprintf declaration
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: gcc-patches at gcc dot gnu dot org, gdb-patches at sources dot redhat dot com
- Date: Thu, 12 May 2005 18:38:38 +0300
- Subject: Re: [RFA] Eliminate warnings about snprintf declaration
- References: <01c4c990$Blat.v2.2.2$887ec720@zahav.net.il> <41994B9D.9080809@gnu.org> <01c55702$Blat.v2.4$d4764900@zahav.net.il> <20050512150804.GA1808@nevyn.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 12 May 2005 11:08:04 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
>
> I recommend copying the libiberty maintainers directly to get their
> attention.
Errr... who are they? libiberty/README says to send patches to
gcc-patches, which I did. What am I missing?
> Also, this isn't useful:
>
> > @@ -282,7 +282,7 @@
> > sysconf times sbrk gettimeofday ffs snprintf vsnprintf \
> > pstat_getstatic pstat_getdynamic sysmp getsysinfo table sysctl wait3 wait4 \
> > realpath canonicalize_file_name __fsetlocking)
> > - AC_CHECK_DECLS([basename, ffs, asprintf, vasprintf])
> > + AC_CHECK_DECLS([basename, ffs, asprintf, vasprintf, snprintf, vsnprintf])
> > AC_DEFINE(HAVE_SYS_ERRLIST, 1, [Define if you have the sys_errlist variable.])
> > AC_DEFINE(HAVE_SYS_NERR, 1, [Define if you have the sys_nerr variable.])
> > AC_DEFINE(HAVE_SYS_SIGLIST, 1, [Define if you have the sys_siglist variable.])
> > @@ -518,7 +518,7 @@
> > [AC_MSG_RESULT([no])])
> >
> > AC_CHECK_FUNCS($checkfuncs)
> > - AC_CHECK_DECLS([basename, ffs, asprintf, vasprintf])
> > + AC_CHECK_DECLS([basename, ffs, asprintf, vasprintf, snprintf, vsnprintf])
> > libiberty_NEED_DECLARATION(canonicalize_file_name)
> > fi
>
> That will only affect libiberty.h when building libiberty; it won't
> affect the users of libiberty.
Then how does one cause libiberty/configure to check for these
declarations and edit libiberty/config.h accordingly? I thought one
should modify configure.ac and the regenerate configure, no?
> I believe you've got this logic reversed. You also don't want or need
> the non-prototype - it's only needed for basename because basename
> returns a pointer. How about this, based on the later examples in the
> file:
Okay. But I guess I should wait for approval by libiberty maintainers
first.
Thanks.