From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: Csaba Raduly <rcsaba@gmail.com>,
matsuoka@nuce.nagoya-u.ac.jp, cygwin@cygwin.com
Cc: "Marco Atzeri" <marco.atzeri@gmail.com>,
"Hans-Bernhard Bröker" <HBBroeker@t-online.de>,
sfeam <sfeam@users.sourceforge.net>
Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
Date: Mon, 11 Apr 2016 08:13:00 -0000 [thread overview]
Message-ID: <866227.9952.qm@web101108.mail.kks.yahoo.co.jp> (raw)
In-Reply-To: <CAEhDDbCU_8C_mNw=fW4Gzp70URp8mgdeMhOARq-OOyO4vH5bXw@mail.gmail.com>
> From: Csaba Raduly
> To: Tatsuro MATSUOKA ; cygwin list
> Cc: Marco Atzeri ; Hans-Bernhard Bröker
> Date: 2016/4/11, Mon 16:52
> Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
>
> Hi,
>
> On Mon, Apr 11, 2016 at 1:20 AM, Tatsuro MATSUOKA wrote:
>
>> 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 ();
>>
>
> You forgot to copy the important line from config.log:
>
> /usr/lib/gcc/x86_64-pc-cygwin/5.3.0/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -lcerf
>
> Why on earth does a test for memcpy try to link to libcerf?
>
> Csaba
Ah!
I configured with
LIBCERF_CFLAGS='-I/usr/local/include' \
LIBCERF_LIBS='-L/usr/local/lib -lcerf' \
../gnuplot/configure --prefix=/opt/gp510 --without-qt --with-caca --with-readline=builtin
I do not why configure add -lcerf.
Without
LIBCERF_CFLAGS='-I/usr/local/include' \
LIBCERF_LIBS='-L/usr/local/lib -lcerf' \
memcpy and other functions are correctly recognized
and make was went well.
But libcerf was not recognised.
This is gnuplot issue but not the Cygwin.
I will be back gnuplot ML and leave from the Cygwin list on this matter.
Thanks!
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
next prev parent reply other threads:[~2016-04-11 8:13 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 [this message]
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=866227.9952.qm@web101108.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 \
--cc=rcsaba@gmail.com \
--cc=sfeam@users.sourceforge.net \
/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).