Re: Query of type of memcpy (and sys_errlist) on Cygwin
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
Re: Query of type of memcpy (and sys_errlist) on Cygwin
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
Re: [ANNOUNCEMENT] Updated: mutt-1.6.0-1
On Wed, Apr 6, 2016 at 3:15 PM, Ismail Donmez wrote:
> Hi,
>
> On Wed, Apr 6, 2016 at 1:42 PM, Marco Atzeri wrote:
>> On 06/04/2016 11:32, Ismail Donmez wrote:
>>>
>>> Hi,
>>>
>>> On Wed, Apr 6, 2016 at 12:22 PM, Marco Atzeri
>>> wrote:
A counter example:
http://chbrauner.blogspot.de/2014/02/mutt-compiled-against-ncurses-and.html
try and let me know
>>>
>>>
>>> I am not using a mutt colorscheme but a mintty one which mutt fails to
>>> render. I will, however, try the change but a quote from the page
>>>
>>> "The solution is to replace a lot of the very specific color
>>> specifications of the colorscheme by the value default. "
>>>
>>> This proves the point that mutt is unable to use 256-color specifications.
>>>
>>> Thanks,
>>> Ismail
>>
>>
>> ncurse can handle 256 color.
>> I doubt that mutt is different from other programs.
>>
>>
>> which TERM variable are you using ?
>>
>> $ TERM="xterm"
>> $ tput colors
>> 8
>>
>> $ TERM="xterm-256color"
>> $ tput colors
>> 256
>
> My TERM is also xterm-256color but however that won't matter because
> looking at mutt-1.6.0/color.c
>
> I see:
>
> #ifdef USE_SLANG_CURSES
> static char *get_color_name (char *dest, size_t destlen, int val)
> {
> static const char * const missing[3] = {"brown", "lightgray", "default"};
> int i;
> [...]
> #endif
>
> and similar functions. So looks like "some" color functionality
> depends on slang.
So, can we enable slang dependency now?
Thanks,
Ismail
--
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
Re: Mintty font problem
Paul Ausbeck soe.ucsc.edu> writes: > > Cygwin setup just updated some older packages while installing a > requested new component and now mintty does not recognize fonts > properly. I was previously using lucinda-console but now some default > font is being used. When I try to change the mintty font through the > Options... dialog, the following message appears when I press Select...: > > "There are no fonts installed. > Open the Fonts folder from the Control Panel to install fonts." > > I've looked through the cygwin announce history and mintty v2.3.3 > advertises some font support changes. I'm still running Windows XP on > this machine and I'm wondering if it could be that this new version of > mintty has not been tested on XP? > > I'm having the same problem with a new XP install and cygwin, where it worked before. Tried v 2.3.3, v2.3.5, and older archived v2.2.4 which certainly worked fine on previous XP machine. Nothing works now, so not sure if it is mintty or XP setup. Exact same XP install disk as previous. Different hardware. One MS forum suggested to make sure that at least 1 printer was installed to make fonts visible in some applications. Another suggested checking permissions on the font directory. A cygwin forum suggested that there might be no monospace fonts installed and that mintty needs monospaced fonts only (make sense). I've tried all the above, and no luck. Something else suggested using tweakui to rebuild certain system folders. I'll try that next. John Refling -- 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
[ANNOUNCEMENT] [Updated] maxima-5.38.0
Maxima has been updated to the upstream relese 5.38.0 on Cygwin. Maxima - Computer Algebra System Maxima is a system for the manipulation of symbolic and numerical expressions, including differentiation, integration, Taylor series, Laplace transforms, ordinary differential equations, systems of linear equations, polynomials, sets, lists, vectors, matrices and tensors. Maxima yields high precision numerical results by using exact fractions, arbitrary-precision integers and variable-precision floating-point numbers. Maxima can plot functions and data in two and three dimensions. Maxima is written in CommonLisp and based on the DOE Macsyma that was developed at MIT. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
[ANNOUNCEMENT] [Updated] Perl Distributions
The following Perl distributions have been updated to their latest release available on CPAN: perl-Archive-Zip-1.57-1 perl-Data-OptList-0.110-1 perl-Devel-CheckLib-1.07-1 perl-IO-Socket-SSL-2.025-1 perl-Module-ScanDeps-1.21-1 perl-Mojolicious-6.57-1 perl-Scalar-List-Utils-1.45-1 perl-Socket6-0.27-1 perl-Test-Reporter-Transport-Metabase-1.999010-1 perl-Unicode-LineBreak-2016.003-1 The following Perl distribution is re-released to fix a packaging error on x86: perl-Encode-ISO2022-0.04-3 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Postinstall script errors on cygwin x86 install
Hello I have tried to install Cygwin x86 in my netbook (win 10 32bit). Only default packages were installed. In the final panel, I saw the following: Postinstall script errors Package: 0/Perpetual 0p_000_autorebase.dash exit code 2 0p_update-info-dir.dash exit code 2 Package: _/base-cygwin 000-cygwin-post-install.sh exit code 254 Package: _/coreutils coreutils.sh exit code 127 Package: _/bash bash.sh exit code 254 Package: _/base-files base-files-mketc.sh exit code 254 base-files-profile.sh exit code 254 Package: _/ca-certificates ca-certificates.sh exit code 254 Package: _/lynx lynx.sh exit code 254 Package: _/man-db man-db.sh exit code 254 What were happened? As expecteded from the errors above installed Cywin were buggy and colud not be usable 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
Re: Postinstall script errors on cygwin x86 install
On 4/10/2016 4:18 PM, Tatsuro MATSUOKA wrote: Hello I have tried to install Cygwin x86 in my netbook (win 10 32bit). Only default packages were installed. In the final panel, I saw the following: Postinstall script errors Package: 0/Perpetual 0p_000_autorebase.dash exit code 2 0p_update-info-dir.dash exit code 2 Package: _/base-cygwin 000-cygwin-post-install.sh exit code 254 Package: _/coreutils coreutils.sh exit code 127 Package: _/bash bash.sh exit code 254 Package: _/base-files base-files-mketc.sh exit code 254 base-files-profile.sh exit code 254 Package: _/ca-certificates ca-certificates.sh exit code 254 Package: _/lynx lynx.sh exit code 254 Package: _/man-db man-db.sh exit code 254 What were happened? As expecteded from the errors above installed Cywin were buggy and colud not be usable Take a look at var/log/setup.log.full and see if it gives any clues as to why the postinstall scripts are failing. You could also try running them manually. Ken -- 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
Re: Query of type of memcpy (and sys_errlist) on Cygwin
> From: Hans-Bernhard Bröker
> To: cygwin@cygwin.com
> Cc:
> Date: 2016/4/10, Sun 16:10
> Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin
>
> 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.
The zipped config.log is available here:
http://www.geocities.jp/tmacchant2/config.log.20160411.zip
Related part of config.log
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 ();
^
/usr/lib/gcc/x86_64-pc-cygwin/5.3.0/../../../../x86_64-pc-cygwin/bin/ld: cannot
find -lcerf
collect2: error: ld returned 1 exit status
configure:9591: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "gnuplot"
| #define PACKAGE_TARNAME "gnuplot"
| #define PACKAGE_VERSION "5.1"
| #define PACKAGE_STRING "gnuplot 5.1"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define DEVELOPMENT_VERSION 1
| #define PACKAGE "gnuplot"
| #define VERSION "5.1"
| #define VERSION_MAJOR "5.1"
| #define PATCHLEVEL "0"
| #define PROTOTYPES 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define HAVE_STRINGIZE 1
| #define HAVE_OFF_T 1
| #define HAVE_FSEEKO 1
| #define X_DISPLAY_MISSING 1
| #define STDC_HEADERS 1
| #define HAVE_DIRENT_H 1
| #define HAVE_ERRNO_H 1
| #define HAVE_FLOAT_H 1
| #define HAVE_LANGINFO_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_LOCALE_H 1
| #define HAVE_MATH_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_TIME_H 1
| #define HAVE_SYS_TIME_H 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_IOCTL_H 1
| #define HAVE_SYS_PARAM_H 1
| #define HAVE_SYS_SELECT_H 1
| #define HAVE_SYS_SOCKET_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_SYS_TIMEB_H 1
| #define HAVE_SYS_UTSNAME_H 1
| #define HAVE_MALLOC_H 1
| #define HAVE_POLL_H 1
| #define HAVE_TERMIOS_H 1
| #define HAVE_DIRENT_H 1
| #define HAVE_DLFCN_H 1
| #define HAVE__BOOL 1
| #define HAVE_STDBOOL_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_TIME_T_IN_TIME_H 1
| /* end confdefs.h. */
| /* Define memcpy to an innocuous variant, in case declares memcpy.
| For example, HP-UX 11i declares gettimeofday. */
| #define memcpy innocuous_memcpy
|
| /* System header to define __stub macros and hopefully few prototypes,
| which can conflict with char memcpy (); below.
| Prefer to if __STDC__ is defined, since
| exists even on freestanding compilers. */
|
| #ifdef __STDC__
| # include
| #else
| # include
| #endif
|
| #undef memcpy
|
| /* Override any GCC internal prototype to avoid an error.
| Use char because int might match the return type of a GCC
| builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern "C"
| #endif
| char memcpy ();
| /* The GNU C library defines this for functions which it implements
| to always fail with ENOSYS. Some functions are actually named
| something starting with __ and the normal name is an alias. */
| #if defined __stub_memcpy || defined __stub___memcpy
| choke me
| #endif
|
| int
| main ()
| {
| return memcpy ();
| ;
| return 0;
| }
configure:9591: result: no
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
Re: Query of type of memcpy (and sys_errlist) on Cygwin
> From: Marco Atzeri > To: cygwin> Cc: > Date: 2016/4/10, Sun 16:12 > Subject: Re: Query of type of memcpy (and sys_errlist) on Cygwin > > Hi Tatsuro, > May be was better to not reply to a different thread ? > I am pending the other thread and I want to discuss here. > 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 > OK I will try and report results here. 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
Re: Postinstall script errors on cygwin x86 install
> From: Ken Brown > To: cygwin > Cc: > Date: 2016/4/11, Mon 07:12 > Subject: Re: Postinstall script errors on cygwin x86 install > > On 4/10/2016 4:18 PM, Tatsuro MATSUOKA wrote: >> Hello >> I have tried to install Cygwin x86 in my netbook (win 10 32bit). >> Only default packages were installed. >> In the final panel, I saw the following: >> Postinstall script errors >> >> Package: 0/Perpetual >> 0p_000_autorebase.dash exit code 2 >> 0p_update-info-dir.dash exit code 2 >> Package: _/base-cygwin >> 000-cygwin-post-install.sh exit code 254 >> Package: _/coreutils >> coreutils.sh exit code 127 >> Package: _/bash >> bash.sh exit code 254 >> Package: _/base-files >> base-files-mketc.sh exit code 254 >> base-files-profile.sh exit code 254 >> Package: _/ca-certificates >> ca-certificates.sh exit code 254 >> Package: _/lynx >> lynx.sh exit code 254 >> Package: _/man-db >> man-db.sh exit code 254 >> What were happened? >> As expecteded from the errors above installed Cywin were buggy >> and colud not be usable > > Take a look at var/log/setup.log.full and see if it gives any clues as to why > the postinstall scripts are failing. You could also try running them > manually. > Thanks! I will try when I will be back to my home. 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
Re: Postinstall script errors on cygwin x86 install
> [Please don't reply to some totally unrelated message when you're starting a new thread.] Tatsuro MATSUOKA yahoo.co.jp> writes: > I have tried to install Cygwin x86 in my netbook (win 10 32bit). > Only default packages were installed. Please check /var/log/setup.log.full for what those errors were specifically. What is the user you are running setup under? Regards, Achim.
