public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Matt Minnis" <mminnis@prefres.com>
To: gcc@gcc.gnu.org
Subject: Declaration clashing
Date: Mon, 31 Jul 2000 12:45:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20000731143528.021ea008@mail.prefres.com> (raw)
In-Reply-To: <20000731111450.A6913@cygnus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

I am getting this error now:

/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/string.h:27:
\
warning: declaration of `void * memcpy(void *, void *, unsigned
int)'

/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/string.h:27:
\
warning: conflicts with built-in declaration `void * memcpy(void *, const
void *, unsigned int)'

How are the headers conflicting?  I see that one is const and the
other isn't.  

How do I resolve this issue?

Are my headers messed up?

Thanks,

Matt

Cthulhu for President. Why settle for a lesser evil?

=========================================================
Preferred
Resources          (314)
567-7600 phone
701 Emerson
rd.             
(314) 993-6699 fax
Suite
475                        
mminnis@prefres.com
St. Louis,
MO                

63141
=========================================================



      reply	other threads:[~2000-07-31 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-28 12:47 Implementation of <tgmath.h> Joseph S. Myers
2000-07-28 12:54 ` Mark Mitchell
2000-07-28 13:43 ` Geoff Keating
2000-07-28 13:55   ` Ulrich Drepper
2000-07-28 15:12     ` Joern Rennecke
2000-07-28 15:36       ` Joseph S. Myers
2000-07-28 19:04       ` Joseph S. Myers
2000-07-31 11:14 ` Richard Henderson
2000-07-31 12:45   ` Matt Minnis [this message]

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=4.3.2.7.2.20000731143528.021ea008@mail.prefres.com \
    --to=mminnis@prefres.com \
    --cc=gcc@gcc.gnu.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).