From: Timothy Sample <samplet@ngyro.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: gash-devel@nongnu.org, 46537-done@debbugs.gnu.org
Subject: bug#46537: ‘uname -s’ from Gash-Utils-Boot returns nothing
Date: Wed, 17 Feb 2021 21:45:02 -0500 [thread overview]
Message-ID: <87a6s2w0up.fsf@ngyro.com> (raw)
In-Reply-To: <YC01nOSV4dBMlZej@3900XT> (Efraim Flashner's message of "Wed, 17 Feb 2021 17:26:20 +0200")
Hello!
Efraim Flashner <efraim@flashner.co.il> writes:
> On Wed, Feb 17, 2021 at 04:16:29PM +0100, Ludovic Courtès wrote:
>>
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>>
>> > On Mon, Feb 15, 2021 at 06:24:46PM +0100, Ludovic Courtès wrote:
>> >> Gash-Utils ‘uname’ seems to be confused:
>> >>
>> >> --8<---------------cut here---------------start------------->8---
>> >> $ $(guix build -e '(@@ (gnu packages commencement) gash-utils-boot)')/bin/uname -a
>> >> Linux ribbon 5.10.10-gnu #1 SMP 1 x86_64 GNU/Linux
>> >> $ $(guix build -e '(@@ (gnu packages commencement) gash-utils-boot)')/bin/uname -s
>> >>
>> >> $ guix describe
>> >> Generacio 175 Feb 04 2021 22:52:40 (nuna)
>> >> guix 5ae09d7
>> >> repository URL: https://git.savannah.gnu.org/git/guix.git
>> >> branch: master
>> >> commit: 5ae09d7979a0696d862b9555314eab199f7ce576
>> >> $ uname -s
>> >> Linux
>> >> --8<---------------cut here---------------end--------------->8---
>>
>> I forgot to mention the ‘uname -s’ problem is hidden by the fact that we
>> always pass ‘--build’ to ‘configure’. When we don’t do that,
>> ‘config.guess’ runs and fails.
>>
>> [...]
>>
>> I wonder if this should be kept but changed to:
>>
>> (kernel-name? (or kernel-name? (not (or …))))
>
> With it changed to this:
> (ins)efraim@3900XT ~/workspace/gash-utils$
> /gnu/store/9mb28yyzfh6pr4yk5nyy42vrfbj8caxp-gash-utils-boot-0.1.0.107-eedd-dirty/bin/uname
> -s
> Linux
Indeed! I noticed this same issue the other day. Check out commit
2ee2e2721367cc242ceb0e4b364468870a87f0b4:
https://git.savannah.nongnu.org/cgit/gash/gash-utils.git/commit/?id=2ee2e2721367cc242ceb0e4b364468870a87f0b4
I recommend that you take a look at the “wip-gcc-mesboot” branch. It
has a couple “from the hip” changes that I made while looking at getting
Gash-Utils to handle more of the work in “commencement.scm”. Last week
I was able to build to “gcc-mesboot1” with only Make, Diffutils, patch,
and Gzip (the first three were there before the “Scheme-only” bootstrap,
and Gzip saves writing “(delete 'compress-documentation)” over and
over). Unfortunately, building Glibc after that is quite difficult. To
do it with Gash-Utils, we would need (at least) to support redirects in
AWK and the “-t” and “-k” flags in sort. For fun, I tried building Gawk
and Coreutils at this point (using the ancient versions that we
bootstrap with now). That let me build Glibc, but then I hit a problem
with the “po2test.sed” script while building “gcc-mesboot”. I tried
again with ancient GNU Sed, but the build seemed to hang during a
configure test. I suspect adding Bash to the mix might fix it, but I
haven’t tried yet....
Back to the matter at hand: I’m closing this bug since it’s already been
fixed. :)
-- Tim
next prev parent reply other threads:[~2021-02-18 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 17:24 bug#46537: ‘uname -s’ from Gash-Utils-Boot returns nothing Ludovic Courtès
2021-02-16 9:52 ` Efraim Flashner
2021-02-17 15:16 ` Ludovic Courtès
2021-02-17 15:26 ` Efraim Flashner
2021-02-18 2:45 ` Timothy Sample [this message]
2021-02-18 13:34 ` Ludovic Courtès
2021-02-18 18:02 ` Timothy Sample
2021-02-19 15:02 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6s2w0up.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=46537-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=gash-devel@nongnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).