From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Willy Tarreau <w@1wt.eu>, "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 07:59:13 +0200 [thread overview]
Message-ID: <e594db6c-5795-4038-bcb2-1dc3290bfb27@t-8ch.de> (raw)
In-Reply-To: <13169754-c8ea-4e9e-b062-81b253a07078@linuxfoundation.org>
On 2024-09-04 15:19:42+0000, Shuah Khan wrote:
> On 9/4/24 15:13, Thomas Weißschuh wrote:
> > On 2024-09-04 15:04:35+0000, Shuah Khan wrote:
> > > On 8/27/24 06:56, Shuah Khan wrote:
> > > > On 8/24/24 12:53, Thomas Weißschuh wrote:
> > > > > Hi Shuah,
> > > > >
> > > > > The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
> > > > >
> > > > > Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
> > > > >
> > > > > are available in the Git repository at:
> > > > >
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git nolibc-20240824-for-6.12-1
> > > > >
> > > > > for you to fetch changes up to 25fb329a23c78d59a055a7b1329d18f30a2be92d:
> > > > >
> > > > > tools/nolibc: x86_64: use local label in memcpy/memmove (2024-08-16 17:23:13 +0200)
> > > > >
> > > > > ----------------------------------------------------------------
> > > > > nolibc changes for 6.12
> > > > >
> > > > > Highlights
> > > > > ----------
> > > > >
> > > > > * Clang support (including LTO)
> > > > >
> > > > > Other Changes
> > > > > -------------
> > > > >
> > > > > * stdbool.h support
> > > > > * argc/argv/envp arguments for constructors
> > > > > * Small #include ordering fix
> > > > >
> > > >
> > > > Thank you Thomas.
> > > >
> > > > Pulled and pushed to linux-kselftest nolibc branch for Linux 6.12-rc1
> > > >
> > >
> > > I am running sanity tests and getting this message:
> > >
> > > $HOME/.cache/crosstools/gcc-13.2.0-nolibc/i386-linux/bin/i386-linux-: No such file or directory
> >
> > This indicates you are using 'run-tests.sh'.
> > Pass "-p" to let it download the toolchain automatically.
> >
> > > 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?
> > > 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?
> > 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.
As Willy said, thanks for the report!
Thomas
next prev parent reply other threads:[~2024-09-05 5:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 18:53 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 [this message]
2024-09-05 6:22 ` Willy Tarreau
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
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=e594db6c-5795-4038-bcb2-1dc3290bfb27@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®