From: LRN <lrn1986@gmail.com>
To: binutils@sourceware.org
Subject: stpcpy() redefined
Date: Fri, 18 Oct 2013 19:00:00 -0000 [thread overview]
Message-ID: <52618556.2040909@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Recent mingw-w64 added a stpcpy() implementation for sources that
request appropriate compatibility (_XOPEN_SOURCE or _GNU_C_SOURCE).
This created problems with binutils (or, to be precise, with libintl):
i686-w64-mingw32-gcc -c -g -O2 -D__USE_MINGW_ACCESS -DHAVE_CONFIG_H
- -I. -I../../binutils-2.23.90.20131017/intl
../../binutils-2.23.90.20131017/intl/l10nflist.c
../../binutils-2.23.90.20131017/intl/l10nflist.c:445:1: error:
redefinition of ‘stpcpy’
stpcpy (dest, src)
^
In file included from ../../binutils-2.23.90.20131017/intl/l10nflist.c:30:0:
/home/lrn/src/mingw-w64-mingw32-native/cross-toolchain/i686-w64-mingw32/include/string.h:56:21:
note: previous definition of ‘stpcpy’ was here
__mingw_ovr char *stpcpy(char * __restrict__ _Dest,const char *
__restrict__ _Source) { return __mingw_stpcpy(_Dest, _Source); }
^
make[2]: *** [l10nflist.o] Error 1
Before i try to come up with a patch for this, do you have any
recommendations on dealing with it?
- --
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
iQEcBAEBAgAGBQJSYYVWAAoJEOs4Jb6SI2Cwh3gIANuSEncJstzFuApZrgfwEJVu
k15HiSBUO7bUCAQhwVJlBEFCp6cYVbcCzKUNOqK5kT1b489k1DzhbKe1bfACQ8to
RZKyApvAS38zu7pJqumnHY7wdLfffZhv561XyQc3a62EMLc397Qi5mjBVbhJ/BBv
85Bo4cKjlGFo9lNfO3/9HdN0E8kJCkqFq0qrqExuo/oCqS2DBECEksbKBP5Rg19i
EPYC1vVF1r/oKNoZzy8MMsAlwRBT7umxL3erH4dAZTgmjvdypV2hn5oK3LVrMSd6
nzOlM20uzUAKgUBS3ZXMjYJCyy4F33EXngYUSglWp2psFhJ4puKZoneAG791oBk=
=IYnw
-----END PGP SIGNATURE-----
next reply other threads:[~2013-10-18 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 19:00 LRN [this message]
2013-10-18 20:18 ` Ian Lance Taylor
2013-10-18 22:18 ` LRN
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=52618556.2040909@gmail.com \
--to=lrn1986@gmail.com \
--cc=binutils@sourceware.org \
/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).