From: Srikanth Myakam <smyakam@microsoft.com>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "dianders@chromium.org" <dianders@chromium.org>,
Atin Mukherjee <Atin.MUKHERJEE@microsoft.com>
Subject: Linux Next cannot build on Ubuntu 1604 and 1804
Date: Fri, 24 Sep 2021 11:09:52 +0000 [thread overview]
Message-ID: <PU1P153MB0187B57518188FCDB102025CA0A49@PU1P153MB0187.APCP153.PROD.OUTLOOK.COM> (raw)
We have a pipeline to build Linux-next daily on Ubuntu 1604 and the compilation is failing at building "drivers/gpu/drm/drm_edid.c" starting from Sept 15th.
The error text:
drivers/gpu/drm/drm_edid.c:120:16: error: initializer element is not constant
EDID_QUIRK("ACR", 44358, EDID_QUIRK_PREFER_LARGE_60),
^
drivers/gpu/drm/drm_edid.c:120:16: note: (near initialization for 'edid_quirk_list[0].panel_id')
drivers/gpu/drm/drm_edid.c:122:16: error: initializer element is not constant
EDID_QUIRK("API", 0x7602, EDID_QUIRK_PREFER_LARGE_60),
^
drivers/gpu/drm/drm_edid.c:122:16: note: (near initialization for 'edid_quirk_list[1].panel_id')
drivers/gpu/drm/drm_edid.c:125:16: error: initializer element is not constant
EDID_QUIRK("AEO", 0, EDID_QUIRK_FORCE_6BPC),
^
drivers/gpu/drm/drm_edid.c:125:16: note: (near initialization for 'edid_quirk_list[2].panel_id')
drivers/gpu/drm/drm_edid.c:128:16: error: initializer element is not constant
EDID_QUIRK("BOE", 0x78b, EDID_QUIRK_FORCE_6BPC),
....
The issue is observed on below environments:
1. Ubuntu1604, glibc version 2.23-0ubuntu11.3
2. Ubuntu1804, glibc version 2.27-3ubuntu1.2
Seems like it was introduced by patch https://patchwork.freedesktop.org/patch/453876/
-
SrikanthMyakam
next reply other threads:[~2021-09-24 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 11:09 Srikanth Myakam [this message]
2021-09-24 14:01 ` Linux Next cannot build on Ubuntu 1604 and 1804 Doug Anderson
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=PU1P153MB0187B57518188FCDB102025CA0A49@PU1P153MB0187.APCP153.PROD.OUTLOOK.COM \
--to=smyakam@microsoft.com \
--cc=Atin.MUKHERJEE@microsoft.com \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).