|
From: Tatsuro M. <tma...@ya...> - 2016-04-11 10:27:02
|
> From: Tatsuro MATSUOKA > To: Hans-Bernhard Broeker ; gnuplot-beta > Cc: > Date: 2016/4/11, Mon 17:22 > Subject: Re: stdfn.h: error: conflicting types for 'memcopy' and 'sys_errlist' on Cygwin build > >> From: Hans-Bernhard Bröker >> To: gnuplot-beta >> Cc: > >> Date: 2016/4/10, Sun 15:49 >> Subject: Re: stdfn.h: error: conflicting types for 'memcopy' and > 'sys_errlist' on Cygwin build >> >> Am 10.04.2016 um 04:42 schrieb Ethan Merritt: >>> On Sunday, 10 April 2016 10:11:55 AM Tatsuro MATSUOKA wrote: >> >>>> At compiling src/boundary.c I have met errors. >> >> Actually, you met them in almost every single source file. Which is >> understandable, given that the conflict is in stdfn.h, which is included >> just about everywhere. >> >>> How is it possible that cygwin does not provide memcpy()? >> >> It's not. Cygwin does of course provide it. The error messages are >> caused by the provided declaration conflicting with gnuplot's internal >> fall-back. >> >> The problem here is that configure somehow managed to not find the >> declaration, although it most definitely is there. We need to see >> Tatsuro's config.log to find out what went wrong. >> > > The origin of the issue does not lie on the Cygwin but on gnuplot. > > So I am back here. > > See: > https://cygwin.com/ml/cygwin/2016-04/msg00202.html > > Why adding > > LIBCERF_CFLAGS='-I/usr/local/include' \ > LIBCERF_LIBS='-L/usr/local/lib -lcerf' \ > > flags affect configure process those are not related to libcerf ? > > Tatsuro > I have completely forgotten to build and install libcerf again. Sorry for the noise. However, why LIBCERF_CFLAGS='-I/usr/local/include' \ LIBCERF_LIBS='-L/usr/local/lib -lcerf' \ flags affect checking functions that are not related libcerf ? Tatsuro |