From: Shuah Khan <skhan@linuxfoundation.org>
To: Roman Storozhenko <romeusmeister@gmail.com>,
Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] cpupower: Disable direct build of the 'bench' subproject
Date: Fri, 28 Jun 2024 16:05:37 -0600 [thread overview]
Message-ID: <c1bcd796-033e-4ff1-b610-c7c2f64e0b44@linuxfoundation.org> (raw)
In-Reply-To: <20240626-fix_bench_compilation-v1-1-d039bd5fa551@gmail.com>
On 6/26/24 10:45, Roman Storozhenko wrote:
> Execution of the 'make' command in the 'bench' subfolder causes the
> following error:
>
> $ make O=cpupower/build/ DESTDIR=cpupower/install/ -j8
> " CC " cpupower/build//main.o
> " CC " cpupower/build//parse.o
> /bin/sh: 1: " CC "cpupower/build//system.o
> CC : not found
> make: *** [Makefile:21: cpupower/build//main.o] Error 127
> make: *** Waiting for unfinished jobs....
> /bin/sh: 1: CC : not found
> /bin/sh: 1: CC : not found
> make: *** [Makefile:21: cpupower/build//parse.o] Error 127
> make: *** [Makefile:21: cpupower/build//system.o] Error 127
>
> The makefile uses variables defined in the main project makefile and it
> is not intended to run standalone. The reason is that 'bench' subproject
> depends on the 'libcpupower' library, see the 'compile-bench' target in
> the main makefile.
> Add a check that prevents standalone execution of the 'bench' makefile.
>
> Signed-off-by: Roman Storozhenko <romeusmeister@gmail.com>
> ---
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git/log/?h=cpupower
for Linux 6.11-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2024-06-28 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 16:45 Roman Storozhenko
2024-06-28 22:05 ` Shuah Khan [this message]
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=c1bcd796-033e-4ff1-b610-c7c2f64e0b44@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=romeusmeister@gmail.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.com \
/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®