mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Willy Tarreau" <w@1wt.eu>, "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [GIT PULL] nolibc for 6.12-rc1
Date: Thu, 5 Sep 2024 17:57:52 -0600	[thread overview]
Message-ID: <e36fb1f5-f370-4806-912e-d9d2f777a1bc@linuxfoundation.org> (raw)
In-Reply-To: <Ztnd26IlnMwrywUO@1wt.eu>

On 9/5/24 10:35, Willy Tarreau wrote:
> On Thu, Sep 05, 2024 at 05:57:22PM +0200, Thomas Weißschuh wrote:
>> On 2024-09-05 08:32:14+0000, Willy Tarreau wrote:
>>> On Thu, Sep 05, 2024 at 08:22:18AM +0200, Willy Tarreau wrote:
>>>>>
>>>>> ./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.
>>>
>>> In fact I'm getting it without any options:
>>>
>>>    $ ./run-tests.sh
>>>    realpath: /home/willy/.cache/crosstools/gcc-13.2.0-nolibc/i386-linux/bin/i386-linux-: No such file or directory
>>>
>>> It comes from here in test_arch():
>>>
>>>          cross_compile=$(realpath "${download_location}gcc-${crosstool_version}-nolibc/${ct_arch}-${ct_abi}/bin/${ct_arch}-${ct_abi}-")
>>>
>>> Thus it's indeed related to the absence of the toolchain there. It's
>>> just that the way the error is reported (due to set -e) is a bit harsh.
>>
>> Ack. It should not occur with "-p" though.
> 
> Agreed, I was focusing on first experience for users essentially.
> 
>>> What about this ?
>>>
>>>    $ ./run-tests.sh
>>>    No toolchain found in /home/willy/.cache/crosstools/gcc-13.2.0-nolibc/i386-linux.
>>>    Did you install the toolchains or set the correct arch ? Rerun with -h for help.
>>>    Aborting...
>>>
>>> or anything similar, achieved by this patch (warning copy-paste, mangled
>>> indents):
>>>
>>> diff --git a/tools/testing/selftests/nolibc/run-tests.sh b/tools/testing/selftests/nolibc/run-tests.sh
>>> index e7ecda4ae796..0f67e80051dc 100755
>>> --- a/tools/testing/selftests/nolibc/run-tests.sh
>>> +++ b/tools/testing/selftests/nolibc/run-tests.sh
>>> @@ -143,6 +143,13 @@ test_arch() {
>>>          arch=$1
>>>          ct_arch=$(crosstool_arch "$arch")
>>>          ct_abi=$(crosstool_abi "$1")
>>> +
>>> +       if [ ! -d "${download_location}gcc-${crosstool_version}-nolibc/${ct_arch}-${ct_abi}/bin/." ]; then
>>> +               echo "No toolchain found in ${download_location}gcc-${crosstool_version}-nolibc/${ct_arch}-${ct_abi}."
>>> +               echo "Did you install the toolchains or set the correct arch ? Rerun with -h for help."
>>> +               return 1
>>> +       fi
>>> +
>>>          cross_compile=$(realpath "${download_location}gcc-${crosstool_version}-nolibc/${ct_arch}-${ct_abi}/bin/${ct_arch}-${ct_abi}-")
>>>          build_dir="${build_location}/${arch}"
>>>          if [ "$werror" -ne 0 ]; then
>>
>> Looks good.
> 
> OK thanks, I'll try to handle it this week-end if I'm not beaten to
> it. If you or Shuah want to merge it before, feel free to, no offense
> on my side!
> 

Sounds good. My system is back to a good state with the tests after running
./run-tests.sh -p -m user

My guess is my setup was lost when I upgraded my system.

thanks,
-- Shuah




  reply	other threads:[~2024-09-05 23:57 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
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 [this message]
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=e36fb1f5-f370-4806-912e-d9d2f777a1bc@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=paulmck@kernel.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®