all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53964@debbugs.gnu.org
Subject: [bug#53964] [PATCH 0/4] Build nhc98 and ghc@4 with regular dependencies
Date: Mon, 14 Feb 2022 12:22:54 +0100	[thread overview]
Message-ID: <87o839y9o1.fsf_-_@gnu.org> (raw)
In-Reply-To: <87mtitzta4.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 14 Feb 2022 10:33:55 +0100")

Ludovic Courtès <ludo@gnu.org> skribis:

> Maxime Devos <maximedevos@telenet.be> skribis:
>
>> Ludovic Courtès schreef op za 12-02-2022 om 22:45 [+0100]:
>>> +           #:tests? #f
>>
>> Why are tests disabled here?
>
> That’s the same for all the GCC variants, including ‘gcc-core-mesboot0’,
> which was the inspiration for this one.  I think the main reason is that
> “it’s difficult” (there’s a dependency on DejaGNU, the fact that you
> cannot expect all tests to pass, and the fact that many tests would
> probably need to be adjusted.)

So I tried out of curiosity and was surprised to see that ‘make check’
succeeds!  It’s not entirely clear how many tests were run though since
DejaGNU isn’t very talkative:

--8<---------------cut here---------------start------------->8---
Test run by nixbld on Mon Feb 14 11:21:04 2022
Native configuration is i686-unknown-linux-gnu
Test run by nixbld on Mon Feb 14 11:21:04 2022

		=== gcc tests ===

Native configuration is i686-unknown-linux-gnu

		=== g77 tests ===

Schedule of variations:
WARNING: Couldn't find tool init file
    unix


[...]


		=== g++ Summary ===

make[1]: Leaving directory '/tmp/guix-build-gcc-2.95.3.drv-0/gcc-2.95.3/gcc'
/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh ./regress-demangle ./demangle-expected
All 616 tests passed
make[2]: Leaving directory '/tmp/guix-build-gcc-2.95.3.drv-0/gcc-2.95.3/libiberty/testsuite'
make[1]: Leaving directory '/tmp/guix-build-gcc-2.95.3.drv-0/gcc-2.95.3/libiberty'
--8<---------------cut here---------------end--------------->8---

Anyway, it can’t hurt.

I also found that building in parallel is reliable enough.

Ludo’.




  reply	other threads:[~2022-02-14 11:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 21:43 [bug#53964] [PATCH 0/4] Build nhc98 and ghc@4 with regular dependencies Ludovic Courtès
2022-02-12 21:45 ` [bug#53964] [PATCH 1/4] gnu: nhc98: Build with the current tool chain Ludovic Courtès
2022-02-12 21:45   ` [bug#53964] [PATCH 2/4] gnu: gcc: Add 2.95 Ludovic Courtès
2022-02-12 22:35     ` Maxime Devos
2022-02-12 22:37     ` Maxime Devos
2022-02-14  9:23       ` Ludovic Courtès
2022-02-12 22:40     ` Maxime Devos
2022-02-14  9:25       ` Ludovic Courtès
2022-02-12 22:43     ` Maxime Devos
2022-02-12 22:45     ` Maxime Devos
2022-02-14  9:26       ` Ludovic Courtès
2022-02-12 22:47     ` Maxime Devos
2022-02-14  9:33       ` Ludovic Courtès
2022-02-14 11:22         ` Ludovic Courtès [this message]
2022-02-12 21:45   ` [bug#53964] [PATCH 3/4] gnu: ghc@4: Build without referring to packages in commencement.scm Ludovic Courtès
2022-02-12 22:49     ` Maxime Devos
2022-02-14  9:35       ` Ludovic Courtès
2022-02-12 22:52     ` Maxime Devos
2022-02-14  9:36       ` Ludovic Courtès
2022-02-12 21:45   ` [bug#53964] [PATCH 4/4] gnu: Remove glibc@2.2.5 and gcc-2.95-wrapper Ludovic Courtès
2022-02-12 22:14 ` [bug#53964] [PATCH 0/4] Build nhc98 and ghc@4 with regular dependencies Ricardo Wurmus
2022-02-14 14:58   ` bug#53964: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o839y9o1.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=53964@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.