public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
Date: Sun, 10 Apr 2016 07:12:00 -0000	[thread overview]
Message-ID: <5709FCDF.5010107@gmail.com> (raw)
In-Reply-To: <375427.72225.qm@web101113.mail.kks.yahoo.co.jp>

Hi Tatsuro,
May be was better to not reply to a different thread ?

On 10/04/2016 05:14, Tatsuro MATSUOKA wrote:
> Hello
> The topic was discussed on gnuplot mailing list.
> http://gnuplot.10905.n7.nabble.com/stdfn-h-error-conflicting-types-for-memcopy-and-sys-errlist-on-Cygwin-build-td20061.html
> Frorm discussion there (the topic is now pending.) ,
> I decided ask here.
> In compling gnuplot I have met errors:
> ../../gnuplot/src/stdfn.h:67:8: error: conflicting types for 'memcpy'
>   char * memcpy __PROTO((char *, char *, size_t));
>
> ../../gnuplot/src/stdfn.h:171:14: error: conflicting types for 'sys_errlist'
>   extern char *sys_errlist[];
>
> Ethan A Merritt suggested in the gnuplot mailing list that:
> Anyhow, the correct typing for memcpy is:
>     void *memcpy(void *,  const void *,  size_t);

correct, when in doubt this is a good place to look for:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/memcpy.html

> I have complied many times this source but I have not met such kinds of errors.
> (Today I have cleanly installed Cygwin because I have cleanly install windows 10)

> Any suggestions?
> Tatsuro
>

cygwin/newlib headers are under re-shuffle to simplify the guarding 
clauses in the main headers.
It is possible that gnuplot is misleaded and don't correctly detect 
memcopy as it should.

Have you tried to use latest test release ?
https://www.cygwin.com/ml/cygwin-announce/2016-04/msg00012.html

Regards
Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-04-10  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 15:13 xgraph 12.1-3 segfaults when run Stefan Parviainen
2016-04-02 13:24 ` Marco Atzeri
2016-04-08 18:06 ` Marco Atzeri
2016-04-09  9:39   ` Stefan Parviainen
2016-04-10  3:14     ` Query of type of memcpy (and sys_errlist) on Cygwin Tatsuro MATSUOKA
2016-04-10  7:10       ` Hans-Bernhard Bröker
2016-04-10 22:48         ` Tatsuro MATSUOKA
2016-04-10  7:12       ` Marco Atzeri [this message]
2016-04-10 22:52         ` Tatsuro MATSUOKA
2016-04-10 23:20         ` Tatsuro MATSUOKA
2016-04-11  7:52           ` Csaba Raduly
2016-04-11  8:13             ` Tatsuro MATSUOKA
2016-04-10 23:27         ` Tatsuro MATSUOKA

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=5709FCDF.5010107@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.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).