From: Jeffrey A Law <law@cygnus.com>
To: Bruno Haible <haible@ilog.fr>
Cc: egcs@cygnus.com
Subject: Re: [patch] Reducing build warnings (2)
Date: Tue, 31 Mar 1998 00:46:00 -0000 [thread overview]
Message-ID: <1862.891240897@hurl.cygnus.com> (raw)
In-Reply-To: <199801021305.OAA07456@halles.ilog.fr>
In message <199801021305.OAA07456@halles.ilog.fr>you write:
>
> Hi,
>
> Second step: Include <string.h> in order to declare `strcat' and similar
> functions. libiberty/cplus-dem.c already includes <string.h> unconditionall
> y,
> and this apparently succeeds on all platforms supported by egcs, hence I'm
> taking this same approach instead of the old-style (pre-1990)
>
> #ifdef HAVE_STRING_H
> #include <string.h>
> #else
> #ifdef HAVE_STRINGS_H
> #include <strings.h>
> #endif
> #endif
>
>
> Thu Jan 1 13:07:51 1998 Bruno Haible <bruno@linuix.mathematik.uni-karlsr
> uhe.de>
>
> * prefix.c: Include string.h.
[ ... ]
I believe this is also unnecessary with the system.h conversion.
jeff
parent reply other threads:[~1998-03-31 0:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199801021305.OAA07456@halles.ilog.fr>]
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=1862.891240897@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=haible@ilog.fr \
/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).