XPost: linux.debian.maint.glibc
From: [email protected]

I'm also experiencing this bug. It is tagged "upstream", but it seems
that upstream is not considering it a bug, see:

https://sourceforge.net/tracker/?func=detail&atid=105470&aid=793764&group_id=5470

Since /usr/include/features.h is in glibc6-dev, this could be a glibc
bug, in case that we consider that it should check whether
_POSIX_C_SOURCE is defined before redefining it. That's why I'm CCing
glibc maintainers.

In any case, I guess that either this check is done there, or in /usr/include/python2.3/pyconfig.h

I'd also suggest highering the severity of this bug: I have an ITP that
cannot compile because of it.

Saludos,

Jesus.

--
Contribute to keep Europe free of software patents!
EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es
-----
Jesus M. Gonzalez Barahona | Grupo de Sistemas y Comunicaciones [email protected] / [email protected] | ESCET, Universidad Rey Juan Carlos tel: +34 91 664 74 67 | c/ Tulipan s/n
fax: +34 91 488 70 49 | 28933 Mostoles, Spain



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.glibc
From: [email protected]

At Mon, 16 Aug 2004 01:12:17 +0200,
Jesus M. Gonzalez-Barahona <[email protected]> wrote:

I'm also experiencing this bug. It is tagged "upstream", but it seems
that upstream is not considering it a bug, see:

https://sourceforge.net/tracker/?func=detail&atid=105470&aid=793764&group_id=5470

Since /usr/include/features.h is in glibc6-dev, this could be a glibc
bug, in case that we consider that it should check whether
_POSIX_C_SOURCE is defined before redefining it. That's why I'm CCing
glibc maintainers.

In any case, I guess that either this check is done there, or in /usr/include/python2.3/pyconfig.h

I'd also suggest highering the severity of this bug: I have an ITP that cannot compile because of it.

8. For the C programming language, shall define _POSIX_C_SOURCE to be
200112L before any header is included

_POSIX_C_SOURCE should be defined "before any header is included".

Regards,
-- gotom


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.glibc
From: [email protected]

On Mon, 2004-08-16 at 02:22, GOTO Masanori wrote:

8. For the C programming language, shall define _POSIX_C_SOURCE to be
200112L before any header is included

_POSIX_C_SOURCE should be defined "before any header is included".

Thanks!

Could you please give me the reference? (Sorry, I'm not familiar to
POSIX standards). It seems that this is incompatible with Python
mandate, but in any case I'd like to inform upstream about it.

Saludos,

Jesus.

--
Contribute to keep Europe free of software patents!
EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es
-----
Jesus M. Gonzalez Barahona | Grupo de Sistemas y Comunicaciones [email protected] / [email protected] | ESCET, Universidad Rey Juan Carlos tel: +34 91 664 74 67 | c/ Tulipan s/n
fax: +34 91 488 70 49 | 28933 Mostoles, Spain



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

At Tue, 17 Aug 2004 03:06:42 +0200,
Jesus M. Gonzalez-Barahona <[email protected]> wrote:

On Mon, 2004-08-16 at 02:22, GOTO Masanori wrote:

8. For the C programming language, shall define _POSIX_C_SOURCE to be
200112L before any header is included

_POSIX_C_SOURCE should be defined "before any header is included".

Thanks!

Could you please give me the reference? (Sorry, I'm not familiar to
POSIX standards).

That phrase was taken from the following comments:

https://sourceforge.net/tracker/?func=detail&atid=105470&aid=793764&group_id=5470

It's described at:

Single Unix Specification 3:
"2.2.1 Strictly Conforming POSIX Application" 8.

It seems that this is incompatible with Python mandate, but in any
case I'd like to inform upstream about it.

I don't know Python mandate well, but I think it's C language issue.

Regards,
-- gotom


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)