mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kernel Build System <linux-kbuild@vger.kernel.org>
Cc: Sami Tolvanen <samitolvanen@google.com>,
	Kees Cook <keescook@chromium.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Xu Zhen <xuzhen@fastmail.com>
Subject: Fwd: Incorrect thinlto cache directory path in Makefile
Date: Sat, 11 May 2024 18:18:38 +0700	[thread overview]
Message-ID: <Zj9UDiAHqX3noTsy@archie.me> (raw)

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

Hi,

Xu Zhen <xuzhen@fastmail.com> reported on Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=218825) thinlto build directory problem (especially on
DKMS modules). He wrote:

> In Makefile, the ld flag `--thinlto-cache-dir' is set to
> `$(extmod_prefix).thinlto-cache'. But at that time, the variable extmod_prefix
> had not been assigned yet. Therefore, the thinlto cache dir is always created
> in the current directory.
> 
> Even worse, the cache dir cannot be deleted when executing `make clean'. This
> is because its path was written as `$(KBUILD_EXTMOD)/.thinlto-cache' in the
> clean: target.
> 
> Some users have been troubled by it: https://github.com/dell/dkms/issues/292
> 
> This bug was introduced by commit dc5723b02e523b2c4a68667f7e28c65018f7202f

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2024-05-11 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 11:18 Bagas Sanjaya [this message]
2024-05-12 13:04 ` Masahiro Yamada
2024-05-12 13:14   ` Masahiro Yamada

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=Zj9UDiAHqX3noTsy@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=xuzhen@fastmail.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®