From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: basename conflicting definitions
Date: Tue, 21 Apr 2015 07:38:00 -0000 [thread overview]
Message-ID: <20150421073803.GV3657@calimero.vinschen.de> (raw)
In-Reply-To: <5535E0BA.3030800@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Hi Marco,
On Apr 21 07:31, Marco Atzeri wrote:
> Hi Corinna,
> building open-mpi on
>
> $ uname -svrm
> CYGWIN_NT-6.1 2.0.0(0.287/5/3) 2015-04-17 12:08 x86_64
>
> I see a conflict from 2 header of
>
> $ cygcheck -f /usr/include/libgen.h /usr/include/string.h
> cygwin-devel-2.0.0-0.7
> cygwin-devel-2.0.0-0.7
>
>
> configure:59845: gcc -std=gnu99 -c -DNDEBUG -ggdb -O2 -pipe
> -Wimplicit-function-declaration -fdebug-prefix-map=/pub/devel/openmpi/openmpi-1.8.5pre2-1.x86_64/build=/usr/src/debug/openmpi-1.8.5pre2-1 -fdebug-prefix-map=/pub/devel/openmpi/openmpi-1.8.5pre2-1.x86_64/src/openmpi-1.8.5pre2=/usr/src/debug/openmpi-1.8.5pre2-1
> -finline-functions -fno-strict-aliasing -fexceptions conftest.c >&5
> In file included from conftest.c:429:0:
> /usr/include/libgen.h:18:14: error: conflicting types for 'basename'
> extern char *basename (char *path);
> ^
> In file included from /usr/include/stdio.h:29:0,
> from conftest.c:396:
> /usr/include/string.h:172:7: note: previous declaration of 'basename' was
> here
> char *_EXFUN(basename,(const char *))
> ^
That's Yaakov's patch to introduce GNU basename with the different
behaviour depending whether you include via libgen.h or via #define
_GNU_SOURCE, string,h.
Which one is it here? The conflict shouldn't occur, one of them should
have been filtered out based on the order.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-21 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 5:31 Marco Atzeri
2015-04-21 7:38 ` Corinna Vinschen [this message]
2015-04-21 8:44 ` Marco Atzeri
2015-04-21 9:21 ` Corinna Vinschen
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=20150421073803.GV3657@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).