linux-kernel - Re: [GIT PULL] nolibc for 6.12-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZtlOGkADy7OkXY9u@1wt.eu>
Date: Thu, 5 Sep 2024 08:22:18 +0200
From: Willy Tarreau <w@....eu>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Shuah Khan <skhan@...uxfoundation.org>,
        "Paul E. McKenney" <paulmck@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] nolibc for 6.12-rc1

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