[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13169754-c8ea-4e9e-b062-81b253a07078@linuxfoundation.org>
Date: Wed, 4 Sep 2024 15:19:42 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Willy Tarreau <w@....eu>, "Paul E. McKenney" <paulmck@...nel.org>,
linux-kernel@...r.kernel.org, Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [GIT PULL] nolibc for 6.12-rc1
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.
>
>> 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.
> 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
thanks,
-- Shuah
Powered by blists - more mailing lists