Hi,
(please CC me on replies, since I'm not subscribed to -bsd@.)
years ago, when Robert Millan improved the support for k*bsd* in gcc, he
added the __GLIBC__ define as part of the ones provided by gcc itself
(see [1][2]).
Unfortunately, __GLIBC__ is one of the defines provided by glibc itself
python3.3 build failure on kfreebsd and the hurd, please could somebody have a
look and propose a patch?
thanks, Matthias
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hi,
Alle martedì 6 novembre 2012, Matthias Klose ha scritto:
python3.3 build failure on kfreebsd and the hurd, please could
somebody have a look and propose a patch?
This was reported upstream months ago:
http://bugs.python.org/issue13669
I just left a comment with a possible solution
Hi,
I'd say the test at Modules/posixmodule.c:114 is wrong:
#if defined(HAVE_SYS_XATTR_H) defined(__GLIBC__)
#define USE_XATTRS
#endif
Because GLIBC doesn't imply a working xattr interface (traditionally a
Linux thing?). There seem to be implementations only for Linux,
GNU/Hurd and as part
Hi,
Alle martedì 6 novembre 2012, Steven Chamberlain ha scritto:
I'd say the test at Modules/posixmodule.c:114 is wrong:
#if defined(HAVE_SYS_XATTR_H) defined(__GLIBC__)
#define USE_XATTRS
#endif
Because GLIBC doesn't imply a working xattr interface (traditionally
a Linux thing?).
Hi!
On Tue, 2012-11-06 at 13:05:02 +0100, Pino Toscano wrote:
years ago, when Robert Millan improved the support for k*bsd* in gcc, he
added the __GLIBC__ define as part of the ones provided by gcc itself
(see [1][2]).
Unfortunately, __GLIBC__ is one of the defines provided by glibc itself
6 matches
Mail list logo
