All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Timur Kristóf" <timur.kristof@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Leo Li <sunpeng.li@amd.com>, David Airlie <airlied@gmail.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next-20251029 - build error in amdgpu
Date: Sat, 01 Nov 2025 20:59:41 -0400	[thread overview]
Message-ID: <1296761.1762045181@turing-police> (raw)
In-Reply-To: <32ed124e9d603cad950c4836c7a14a3ba8bc2068.camel@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 738 bytes --]

On Thu, 30 Oct 2025 19:05:30 +0100, Timur Kristóf said:

> Can you say how to reproduce that?
> I use the same version of GCC but it hasn't given me any warning or
> error for that patch.

Upon further testing, 

[/usr/src/linux-next] make 

is sufficient on my system. Turns out that it errors out even without W=1. My
next guess was that it had to do with -Werror, which would cause warnings to
be treated as errors, but my .config has

# CONFIG_WERROR is not set
# CONFIG_DRM_WERROR is not set
# CONFIG_DRM_AMDGPU_WERROR is not set

Do you perhaps have patches in your tree that aren't in next-20251029?

I wonder if Fedora's build of gcc 15.2.1 is different somehow from the
build you're using....


\0\0\0\0\0\0\0\0

  reply	other threads:[~2025-11-03  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 17:20 linux-next-20251029 - build error in amdgpu Valdis Klētnieks
2025-10-30 18:05 ` Timur Kristóf
2025-11-02  0:59   ` Valdis Klētnieks [this message]
2025-11-02  9:27     ` Timur Kristóf
2025-11-06  2:34       ` Amit Dhingra
2025-11-06  2:40         ` Timur Kristóf
2025-11-06  3:24           ` Amit Dhingra
2025-11-06  3:29             ` Timur Kristóf
2025-11-06  3:32               ` Amit Dhingra
2025-11-06  3:31             ` Valdis Klētnieks
2025-11-06  3:18         ` Valdis Klētnieks
2025-11-06 14:02           ` Kees Cook
2025-11-06 23:49             ` Bill Wendling
2025-11-08 15:10             ` Valdis Klētnieks

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=1296761.1762045181@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunpeng.li@amd.com \
    --cc=timur.kristof@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.