public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: "Marco Atzeri" <marco.atzeri@gmail.com>,
	cygwin@cygwin.com, "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
Date: Sun, 10 Apr 2016 23:27:00 -0000	[thread overview]
Message-ID: <359093.72519.qm@web101116.mail.kks.yahoo.co.jp> (raw)
In-Reply-To: <5709FCDF.5010107@gmail.com>

> From: Tatsuro MATSUOKA 
> To: Marco Atzeri ; cygwin Hans-Bernhard Bröker 
           > Cc: 
> Date: 2016/4/11, Mon 08:20
> Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
> 
>>  From: Tatsuro MATSUOKA 
>>  To: Marco Atzeri  cygwin
>>  Date: 2016/4/11, Mon 07:52
>>  Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
>> 
>>>   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
>>> 
>> 
>>  OK I will try and report results here.
> The results are almost the same as those at the stable release.
> The zipped config.log is placed here:
> http://www.geocities.jp/tmacchant2/config.log.20160411.zip
> The previous reply to Hans I made a mistake to extract the memcpy related part.
> I apologize for that.
> configure:9591: result: no
> configure:9591: checking for memcpy
> configure:9591: gcc -o conftest.exe -g -O2  -I/usr/local/include  
> -L/usr/local/lib -lcerf conftest.c  >&5
> conftest.c:86:6: warning: conflicting types for built-in function 
> 'memcpy'
>  char memcpy ();
> 
> Seeing configure output screen: one can see that:
> checking for atexit... no
> checking for memcpy... no
> checking for memmove... no
> checking for memset... no
> checking for on_exit... no
> checking for bcopy... no
> checking for bzero... no
> checking for setvbuf... no
> checking for strerror... no
> checking for strchr... no
> checking for strrchr... no
> checking for strstr... no
> checking for index... no
> checking for rindex... no
> checking for erf... no
> checking for erfc... no
> checking for gamma... no
> checking for lgamma... no
> checking for getcwd... no
> checking for poll... no
> checking for pclose... no
> checking for popen... no
> checking for fdopen... no
> checking for select... no
> checking for sleep... no
> checking for stpcpy... no
> checking for strcspn... no
> checking for strdup... no
> checking for strndup... no
> checking for strnlen... no
> checking for strcasecmp... no
> checking for stricmp... no
> checking for strncasecmp... no
> checking for strnicmp... no
> checking for sysinfo... no
> checking for tcgetattr... no
> checking for vfprintf... no
> checking for doprnt... no
> checking for uname... no
> checking for usleep... no
> checking for snprintf... no
>   WARNING: Could not find a working version of snprintf.
>            If a user provides gnuplot with an improper format statement
>            then a buffer overflow and/or segfault can result.
>            Please consider providing snprintf via an external library.
> The above is very strange. Checks of many fucntions are no.
> Tatsuro

I have come back to the gcc 5.3.0-3 to 4.9.3-1.
However, the results are the same.
Tatsuro

--
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 23:27 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
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 [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=359093.72519.qm@web101116.mail.kks.yahoo.co.jp \
    --to=tmacchant2@yahoo.co.jp \
    --cc=HBBroeker@t-online.de \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    --cc=matsuoka@nuce.nagoya-u.ac.jp \
    /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).