From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] nolibc for 6.12-rc1
Date: Thu, 5 Sep 2024 08:22:18 +0200 [thread overview]
Message-ID: <ZtlOGkADy7OkXY9u@1wt.eu> (raw)
In-Reply-To: <e594db6c-5795-4038-bcb2-1dc3290bfb27@t-8ch.de>
Hi Thomas,
On Thu, Sep 05, 2024 at 07:59:13AM +0200, Thomas Weißschuh wrote:
> > > > I tried setting TOOLCHAIN_BASE to the directory I installed gcc-13.2.0-nolibc
> > >
> > > Not sure where this variable comes from, but I have never seen it.
> >
> > This is from the notes I got from Willy.
>
> Could you forward those to me?
I've finding this in the old "test-all-full4.sh" script that I shared
last year:
https://lore.kernel.org/all/ZNvIkD1oxZENVkoe@1wt.eu/
> > > > Something changed since the last time I did the pull request handling.
> > >
> > > In the test setup not much has changed.
> > > Maybe you cleaned out your ~/.cache?
> >
> > Not intentionally ...
> > Guess I just have to do run download.sh again.
>
> I guess download.sh also comes from Willy?
I was about to say no until I saw it in the mail above :-) I did
not remember about it.
> > > Or it's the first PR with run-tests.sh?
> >
> > I have been running the following successfully in the past:
> >
> > From tools/testing/selftests/nolibc
> > make run
> > make run-user
> >
> > ./run-tests.sh -m user
> > ./run-tests.sh -m system
>
> Ack.
>
> Could you provide a transcript of the commands you are running and their
> outputs, including the failing command?
> From the error it looks like run-tests.sh is the one failing, but that
> script was written completely oblivious to download.sh and
> TOOLCHAIN_BASE, so those probably won't help solving the issue.
>
> The following command should automatically download the toolchains into
> the location from the error message:
>
> ./run-tests.sh -p -m user
>
> These toolchains can then also be used for direct "make" invocations
> through CROSS_COMPILE.
I really suspect an empty CC variable somewhere that could explain why
only CROSS_COMPILE is used. I'll try to find time today to give it a
try here as well, just in case I can reproduce the same issue.
Thanks,
Willy
next prev parent reply other threads:[~2024-09-05 6:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 18:53 [GIT PULL] nolibc for 6.12-rc1 Thomas Weißschuh
2024-08-27 12:56 ` Shuah Khan
2024-09-04 21:04 ` Shuah Khan
2024-09-04 21:13 ` Thomas Weißschuh
2024-09-04 21:19 ` Shuah Khan
2024-09-05 3:08 ` Willy Tarreau
2024-09-05 5:59 ` Thomas Weißschuh
2024-09-05 6:22 ` Willy Tarreau [this message]
2024-09-05 6:32 ` Willy Tarreau
2024-09-05 15:57 ` Thomas Weißschuh
2024-09-05 16:35 ` Willy Tarreau
2024-09-05 23:57 ` Shuah Khan
2024-09-08 10:22 ` Willy Tarreau
2024-09-09 17:50 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2024-09-16 23:37 Shuah Khan
2024-09-17 15:00 ` pr-tracker-bot
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=ZtlOGkADy7OkXY9u@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@kernel.org \
--cc=skhan@linuxfoundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox