Processed: Re: Bug#403658: lowlevellock.h missing on amd64.
Processing commands for [EMAIL PROTECTED]: reassign 403658 purelibc Bug#403658: lowlevellock.h missing on amd64. Bug reassigned from package `libc6-dev' to `purelibc'. retitle 403658 purelibc: FTBFS: Makes use of glibc internal _IO_MTSAFE_IO. Bug#403658: lowlevellock.h missing on amd64. Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403658: lowlevellock.h missing on amd64.
reassign 403658 purelibc retitle 403658 purelibc: FTBFS: Makes use of glibc internal _IO_MTSAFE_IO. thanks Theoretically you should not define _IO_MTSAFE_IO it is reserved for glibc internals. That's why you get an error there, when using a NPTL libc. So, I've reassign it to purelibc, because it shouldn't be using it. (It seems you tried to merge bugs, but I guess control never got those, so I've just reassigned one of them to purelibc instead of cloning one.) I will try to find a hack to ignore all occurences of _IO_MTSAFE_IO from the headers installed by the glibc. At which point purelibc won't be able to build on any arch, so they really should look at it. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403658: lowlevellock.h missing on amd64.
severity 403658 normal merge 404532 403658 thanks Kurt Roeckx a écrit : Package: libc6-dev Version: 2.3.6.ds1-9 Severity: important Hi, While trying to build purelibc on amd64 I get the following error: In file included from /usr/include/libio.h:171, from /usr/include/stdio.h:72, from stdio.c:25: /usr/include/bits/stdio-lock.h:24:26: error: lowlevellock.h: No such file or directory stdio.c: In function '__overflow': stdio.c:238: warning: control reaches end of non-void function stdio.c: In function '_pure_assign_file': stdio.c:261: error: 'LLL_LOCK_INITIALIZER' undeclared (first use in this function) stdio.c:261: error: (Each undeclared identifier is reported only once stdio.c:261: error: for each function it appears in.) stdio.c: In function '_pure_freopen': stdio.c:314: error: '_IO_lock_t' has no member named 'mutex' stdio.c:320: error: '_IO_lock_t' has no member named 'mutex' [...] purelibc's stdio.c looks like: #define _IO_MTSAFE_IO #include stdio.h Theoretically you should not define _IO_MTSAFE_IO it is reserved for glibc internals. That's why you get an error there, when using a NPTL libc. I will try to find a hack to ignore all occurences of _IO_MTSAFE_IO from the headers installed by the glibc. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403658: lowlevellock.h missing on amd64.
Package: libc6-dev
Version: 2.3.6.ds1-9
Severity: important
Hi,
While trying to build purelibc on amd64 I get the following error:
In file included from /usr/include/libio.h:171,
from /usr/include/stdio.h:72,
from stdio.c:25:
/usr/include/bits/stdio-lock.h:24:26: error: lowlevellock.h: No such file or
directory
stdio.c: In function '__overflow':
stdio.c:238: warning: control reaches end of non-void function
stdio.c: In function '_pure_assign_file':
stdio.c:261: error: 'LLL_LOCK_INITIALIZER' undeclared (first use in this
function)
stdio.c:261: error: (Each undeclared identifier is reported only once
stdio.c:261: error: for each function it appears in.)
stdio.c: In function '_pure_freopen':
stdio.c:314: error: '_IO_lock_t' has no member named 'mutex'
stdio.c:320: error: '_IO_lock_t' has no member named 'mutex'
[...]
purelibc's stdio.c looks like:
#define _IO_MTSAFE_IO
#include stdio.h
on i386 we have:
#include bits/libc-lock.h
__libc_lock_define_recursive (typedef, _IO_lock_t)
Which results in:
typedef struct { pthread_mutex_t mutex; } __libc_lock_recursive_t;
typedef __libc_lock_recursive_t _IO_lock_t;
on amd64 we have:
#include bits/libc-lock.h
#include lowlevellock.h
typedef struct { int lock; int cnt; void *owner; } _IO_lock_t;
It looks to me like the version on amd64 currently isn't really working,
since the functions/defines in stdio-lock.h atleast don't work with
itself.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
