From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Native build fails in winsup/cygwin/libc/strptime.cc because of strtou?l_l()
Date: Wed, 24 Aug 2016 00:22:00 -0000 [thread overview]
Message-ID: <930c2619-1e9e-7275-c245-0a8c4bd92e6c@t-online.de> (raw)
Hello everyone,
building the git version of cygwin natively on Cygwin-2.5.3, I'm running
into a problem with strtoul_l / strtol_l.
winsup/cygwin/libc/strptime.cc fails to build:
hbbro@NB4 ~/prg/cygwin/bld/x86_64-unknown-cygwin/winsup/cygwin
$ make
c++wrap -O2 -g -fno-rtti -fno-exceptions -fno-use-cxa-atexit -Wall
-Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin
-fmessage-length=0 -MMD -Werror -fmerge-constants -ftracer
-mcmodel=small -c -o strptime.o
../../../../newlib-cygwin/winsup/cygwin/libc/strptime.cc
../../../../newlib-cygwin/winsup/cygwin/libc/strptime.cc: In function
'era_info_t* get_era_info(const char*, locale_t)':
../../../../newlib-cygwin/winsup/cygwin/libc/strptime.cc:125:53: error:
'strtol_l' was not declared in this scope
ei[cur].offset = strtol_l (era, &c, 10, locale);
^
../../../../newlib-cygwin/winsup/cygwin/libc/strptime.cc: In function
'char* __strptime(const char*, const char*, tm*, era_info_t**,
alt_digits_t**, locale_t)':
../../../../newlib-cygwin/winsup/cygwin/libc/strptime.cc:390:50: error:
'strtoul_l' was not declared in this scope
width = strtoul_l (fmt - 1, &end, 10, locale);
^
make: ***
[../../../../newlib-cygwin/winsup/cygwin/../Makefile.common:41:
strptime.o] Fehler 1
Looking at the .ii file, it appears __GNU_VISIBLE is not active for this
C++ source file?
--
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 reply other threads:[~2016-08-23 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 0:22 Hans-Bernhard Bröker [this message]
2016-08-24 8:38 ` Corinna Vinschen
2016-08-24 18:39 ` Hans-Bernhard Bröker
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=930c2619-1e9e-7275-c245-0a8c4bd92e6c@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).