This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Upstreaming the glibc Hurd port
- From: Zack Weinberg <zackw at panix dot com>
- To: Joseph Myers <joseph at codesourcery dot com>, Florian Weimer <fweimer at redhat dot com>, Thomas Schwinge <thomas at codesourcery dot com>, GNU C Library <libc-alpha at sourceware dot org>, bug-hurd at gnu dot org, David Michael <fedora dot dm0 at gmail dot com>
- Date: Mon, 19 Mar 2018 11:36:18 -0400
- Subject: Re: Upstreaming the glibc Hurd port
- References: <20180118165923.ymreisuzexxz4gt3@var.youpi.perso.aquilenet.fr> <alpine.DEB.2.20.1801182304260.26137@digraph.polyomino.org.uk> <20180118235924.r4z4ppvj7xlvmmfp@var.youpi.perso.aquilenet.fr> <alpine.DEB.2.20.1801190030000.26137@digraph.polyomino.org.uk> <87a7xaupjx.fsf@euler.schwinge.homeip.net> <alpine.DEB.2.20.1801191721480.329@digraph.polyomino.org.uk> <20180124011051.5s2vugyq3ybnurwc@var.youpi.perso.aquilenet.fr> <20180124012726.tibylwp4re5dtgc3@var.youpi.perso.aquilenet.fr> <20180125014143.2hxhzon5lzxtqq6j@var.youpi.perso.aquilenet.fr> <alpine.DEB.2.20.1801251544550.22734@digraph.polyomino.org.uk> <20180319015122.j5tzslkdcnvampoh@var.youpi.perso.aquilenet.fr>
On Sun, Mar 18, 2018 at 9:51 PM, Samuel Thibault
<samuel.thibault@gnu.org> wrote:
> Hello,
>
> Thanks a lot for the feedback on what needs to be done. It was a busy
> week-end :)
>
> We should be almost there, I believe I had addressed in
> sthibaul/hurd-builds all requirements except a few remaining bits:
Is it still expected that glibc trunk cannot be built in the
--host=i686-gnu configuration? I am getting
In file included from ../include/link.h:52:0,
from ../include/dlfcn.h:4,
from ../sysdeps/generic/ldsodefs.h:32,
from ../sysdeps/i386/ldsodefs.h:39,
from ../sysdeps/gnu/ldsodefs.h:46,
from setup-thread.c:22:
../sysdeps/mach/libc-lock.h:227:11: fatal error: libc-lockP.h: No such
file or directory
# include <libc-lockP.h>
^~~~~~~~~~~~~~
compilation terminated.
(I would like to suggest that getting "scripts/build-many-glibcs.py
$workdir compilers i686-gnu" to succeed, and
"scripts/build-many-glibcs.py $workdir glibcs i686-gnu" to fail only
in the testsuite phase, when $workdir/src/glibc contains a trunk
checkout, should be top priority -- once you get to that point, people
working on cross-cutting changes (like me) can ensure that they
haven't made the state of the Hurd port worse.)
zw