From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
Date: Sun, 10 Apr 2016 07:10:00 -0000 [thread overview]
Message-ID: <5709FC5D.3080603@t-online.de> (raw)
In-Reply-To: <375427.72225.qm@web101113.mail.kks.yahoo.co.jp>
Am 10.04.2016 um 05:14 schrieb Tatsuro MATSUOKA:
> 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));
Before everybody gets entirely confused, let me interject that this is
quite certainly not an actual problem about the memcpy() declaration
itself, but rather an extremely surprising failure of an
autoconf-generated configure script.
The configure script in question never failed like that in years of
usage. Well, setting aside occasional, remarkably stubborn rebase
problems with Cygwin's Perl DLLs, that is. See the thread "makeinfo
causes perl error ? Cygwin X86 download todayâ" from last week, also
started by Tatsuro Matsuoka.
--
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
next prev parent reply other threads:[~2016-04-10 7:10 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 [this message]
2016-04-10 22:48 ` Tatsuro MATSUOKA
2016-04-10 7:12 ` Marco Atzeri
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=5709FC5D.3080603@t-online.de \
--to=hbbroeker@t-online.de \
--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).