From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: bootstrap: i686-linux now builds without binutils, gcc seeds
Date: Sun, 02 Sep 2018 07:21:28 +0200 [thread overview]
Message-ID: <87pnxwscdj.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=pju0ZGodG12WQf9475QFrbcXQ+uGAm0re4aR2wkmiAnNw@mail.gmail.com> ("Gábor Boskovits"'s message of "Sat, 1 Sep 2018 20:16:23 +0200")
Gábor Boskovits writes:
> +) After bootstrapping a static glibc-2.2.5, I tried building a shared
> 2.2.5, 2.3, 2.3.4, 2.3.6, 2.4, 2.5 and 2.6. When all failed, I
> invested a couple of days to patch 2.3.6...but that started to look
> like a gargantuan undertaking. Iow, I'm stuck here.
>
> Hello Jan, I'm currently on vacation, but I would be interested to
> have a look into this issue when I get home. Could you send me some
> details?
Thank you! First, enjoy your vacation!
I'll share some details here, but things are changing pretty fast; it
appears I'm unstuck.
Building glibc-2.3.6, I found many files to complain about missing
size_t, wchar_t, NULL, offsetof and some other stray missing types or
macros.
While it's usual to make some patches like a missing include, this
didn't feel OK.
Yesterday I got the advice onl #glibc to try build 2.16 or 2.17, so I
gave that a try. Same troubles...So i got down to inspecting the
include chain for `stddef.h' that failed to supply size_t...I found an
empty stddef.h from linux-libre-headers. There was no stddef.h from the
new libc OR from the old libc included. Although I did set -I flags to
the old libc, and for many files it worked.
That got me supsecting that I used glibc's --with-headers wrongly. I
had it point to the linux-libre-headers.
The (hopefully) major step forward now is that I added two packages:
mesboot-headers (early) and glibc-mesboot-headers (later), that combine
their libc header and the linux-libre-headers in one package; and point
--with-headers to that combination include.
With this change, all the missing types and declarations turned in to
duplicate defines :-) So I have been removing those again from the glibc
patches. Currently I'm finding that glibc-2.16.0 needs some more
linux/*.h headers that were stripped out of the bootstrap libc.
"a.out.h ; for 2.2.5"
"atalk.h" ; for 2.2.5
"errno.h"
"falloc.h"
"if_ether.h" ; for 2.2.5
"ioctl.h"
"kernel.h"
"limits.h"
"netlink.h" ; for 2.16.0
"param.h"
"prctl.h" ; for 2.16.0
"posix_types.h"
"rtnetlink.h" ; for 2.16.0
"socket.h"
"stddef.h"
"swab.h" ; for 2.2.5
"sysctl.h"
"sysinfo.h" ; for 2.2.5
"types.h"
"version.h" ; for 2.2.5
I'll keep you all informed here, thanks.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-09-02 5:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 16:31 bootstrap: i686-linux now builds without binutils, gcc seeds Jan Nieuwenhuizen
2018-09-01 18:16 ` Gábor Boskovits
2018-09-02 5:21 ` Jan Nieuwenhuizen [this message]
2018-09-16 19:24 ` Ludovic Courtès
2018-09-17 6:10 ` Pjotr Prins
2018-09-17 18:29 ` Ricardo Wurmus
2018-09-17 19:25 ` Jan Nieuwenhuizen
2018-09-17 19:47 ` Jan Nieuwenhuizen
2018-09-17 21:55 ` Ricardo Wurmus
2018-09-18 8:27 ` Jan Nieuwenhuizen
2018-09-18 8:04 ` Vincent Legoll
2018-09-18 8:33 ` Jan Nieuwenhuizen
2018-09-18 20:53 ` Jan Nieuwenhuizen
2018-09-19 5:07 ` Jan Nieuwenhuizen
2018-09-19 18:07 ` Jan Nieuwenhuizen
2018-09-22 12:35 ` Ludovic Courtès
2018-09-22 15:34 ` Jan Nieuwenhuizen
2018-09-22 18:23 ` Jan Nieuwenhuizen
2018-09-23 8:02 ` branched core-updates-next [WAS: Re: bootstrap: i686-linux now builds without binutils, gcc seeds] Jan Nieuwenhuizen
2018-09-23 16:09 ` bootstrap: i686-linux now builds without binutils, gcc seeds Joshua Branson
2018-09-23 16:29 ` Jonathan Brielmaier
2018-09-22 12:23 ` Ludovic Courtès
2018-09-22 14:38 ` Jan Nieuwenhuizen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnxwscdj.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.