Debian Bug report logs - #403658
purelibc: FTBFS [amd64] Makes use of glibc internal _IO_MTSAFE_IO.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: submit@bugs.debian.org

Subject: lowlevellock.h missing on amd64.

Date: Mon, 18 Dec 2006 19:58:03 +0100

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

Message #10 received at 403658@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Kurt Roeckx <kurt@roeckx.be>, 403658@bugs.debian.org

Subject: Re: Bug#403658: lowlevellock.h missing on amd64.

Date: Tue, 09 Jan 2007 01:47:51 +0100

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
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Message #15 received at 403658@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Aurelien Jarno <aurelien@aurel32.net>

Cc: 403658@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#403658: lowlevellock.h missing on amd64.

Date: Sat, 13 Jan 2007 18:56:02 +0100

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

Message #28 received at 403658-close@bugs.debian.org (full text, mbox, reply):

From: Filippo Giunchedi <filippo@debian.org>

To: 403658-close@bugs.debian.org

Subject: Bug#403658: fixed in purelibc 0.3-1

Date: Wed, 06 Feb 2008 23:47:24 +0000

Source: purelibc
Source-Version: 0.3-1

We believe that the bug you reported is fixed in the latest version of
purelibc, which is due to be installed in the Debian FTP archive:

libpurelibc0-dev_0.3-1_amd64.deb
  to pool/main/p/purelibc/libpurelibc0-dev_0.3-1_amd64.deb
libpurelibc0_0.3-1_amd64.deb
  to pool/main/p/purelibc/libpurelibc0_0.3-1_amd64.deb
purelibc_0.3-1.diff.gz
  to pool/main/p/purelibc/purelibc_0.3-1.diff.gz
purelibc_0.3-1.dsc
  to pool/main/p/purelibc/purelibc_0.3-1.dsc
purelibc_0.3.orig.tar.gz
  to pool/main/p/purelibc/purelibc_0.3.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 403658@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Filippo Giunchedi <filippo@debian.org> (supplier of updated purelibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 07 Feb 2008 00:33:38 +0100
Source: purelibc
Binary: libpurelibc0-dev libpurelibc0
Architecture: source amd64
Version: 0.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian VSquare Team <pkg-vsquare-devel@lists.alioth.debian.org>
Changed-By: Filippo Giunchedi <filippo@debian.org>
Description: 
 libpurelibc0 - libc+syscalls to libc-only wrapper for libc functions
 libpurelibc0-dev - Development files for the purelibc library
Closes: 403658 404517 410543
Changes: 
 purelibc (0.3-1) unstable; urgency=low
 .
   * New upstream release (Closes: #403658, #410543, #404517)
   * Fix watch file
   * Restrict architectures to i386 amd64 powerpc ppc64
   * Switch to cdbs
Files: 
 96e611cf5d782f2a51eda4c8880fdf5e 904 libs optional purelibc_0.3-1.dsc
 871aec89b879f6708b6fb78262c66d25 341490 libs optional purelibc_0.3.orig.tar.gz
 3888bf96ffd0953514968549b2b7a031 2320 libs optional purelibc_0.3-1.diff.gz
 86eaa74fc95418465f448ef485174014 16870 libdevel optional libpurelibc0-dev_0.3-1_amd64.deb
 7e0bfe84468e006e029fb9d23185638d 18250 libs optional libpurelibc0_0.3-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHqkTJABzeamt51AERAthgAJ9teBO1Zk/xr93AaqERM2UDR8ItIwCgwFJN
ElmbGQJqVprnzVRY8kDSioQ=
=kpv2
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.