Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: -skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13669
___
___
Python-bugs-list
Pino Toscano added the comment:
*_MAX constants are usually defined when the system declares that the maximum
limit for that option exist and is already known at compile time.
Python should simply not rely on XATTR_LIST_MAX and XATTR_SIZE_MAX being
defined, but just grow the buffers as needed
New submission from Zbyszek Szmek zbys...@in.waw.pl:
Extended attribute support was added in issue 12720. Doesn't compile on
kfreebsd/debian, which uses eglibc and gcc. The error is that the symbols
XATTR_LIST_MAX and XATTR_SIZE_MAX are not defined.
After
Benjamin Peterson benja...@python.org added the comment:
Are you telling me that XATTR_SIZE_MAX is defined nowhere on eglibc?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13669
___
Zbyszek Szmek zbys...@in.waw.pl added the comment:
Unless I'm completely confused, XATTR_SIZE_MAX is defined by linux kernel
headers, not the libc.
On my linux debian box:
$ grep -r XATTR_SIZE_MAX -I /usr
include/linux/limits.h:#define XATTR_SIZE_MAX 65536
$ dpkg -l libc6
libc6
Zbyszek Szmek zbys...@in.waw.pl added the comment:
Forgot to add (on the fedora box):
$ rpm -q glibc
glibc-2.14.90-13.x86_64
(The GNU libc libraries from http://www.gnu.org/software/glibc/)
So the glibc/eglibc split is not important here.
--
___
Antoine Pitrou pit...@free.fr added the comment:
On my linux debian box:
$ grep -r XATTR_SIZE_MAX -I /usr
include/linux/limits.h:#define XATTR_SIZE_MAX 65536
$ dpkg -l libc6
libc6 2.11.2-10 Embedded GNU C Library: Shared libraries
$ dpkg -S /usr/include/linux/limits.h
Zbyszek Szmek zbys...@in.waw.pl added the comment:
Yes, it must be, because XATTR_SIZE_MAX is only defined in
linux/limits.h. The problem is that with the kfreebsd kernel,
/usr/include/sys/limits.h doesn't define or include anything that
defines XATTR_SIZE_MAX.
Maybe the test should be
Stefan Krah stefan-use...@bytereef.org added the comment:
So the problem occurs on:
http://www.debian.org/ports/kfreebsd-gnu/
Did I get that right? Is __FreeBSD__ defined on that system?
I'm not sure though if we should start supporting hybrid systems.
--
Zbyszek Szmek zbys...@in.waw.pl added the comment:
That's the one.
No. I'm putting the complete list below.
Actually python2.5-7 and 3.2 is normally packaged by debian for
is arch, so it mostly works.
$ gcc -dM -E - /dev/null
#define __DBL_MIN_EXP__ (-1021)
#define __UINT_LEAST16_MAX__ 65535
Zbyszek Szmek zbys...@in.waw.pl added the comment:
[Why does roundup remove quoted text being replied to???]
On 12/28/2011 06:05 PM, Stefan Krah wrote:
http://www.debian.org/ports/kfreebsd-gnu/
That's the one.
Is __FreeBSD__ defined on that system?
No. I'm putting the complete list below.
11 matches
Mail list logo
