All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Javier Martinez Canillas <javierm@redhat.com>,
	Borislav Petkov <bp@suse.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org
Subject: linux-next: build failure due to the drm tree
Date: Mon, 26 Jul 2021 22:36:00 +0100	[thread overview]
Message-ID: <20210726213600.4054-1-broonie@kernel.org> (raw)

Hi all,

Today's -next fails to build an arm64 allnoconfig:

aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: in function `sysfb_init':
sysfb.c:(.init.text+0xc): undefined reference to `screen_info'
aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `screen_info' which may bind externally can not be used when making a shared object; recompile with -fPIC
sysfb.c:(.init.text+0xc): dangerous relocation: unsupported relocation
aarch64-none-linux-gnu-ld: sysfb.c:(.init.text+0x10): undefined reference to `screen_info'
make[1]: *** [/tmp/next/build/Makefile:1276: vmlinux] Error 1

Caused by

  d391c58271072d0b0f ("drivers/firmware: move x86 Generic System Framebuffers support")

or one of the related commits.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Javier Martinez Canillas <javierm@redhat.com>,
	Borislav Petkov <bp@suse.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org
Subject: linux-next: build failure due to the drm tree
Date: Mon, 26 Jul 2021 22:36:00 +0100	[thread overview]
Message-ID: <20210726213600.4054-1-broonie@kernel.org> (raw)

Hi all,

Today's -next fails to build an arm64 allnoconfig:

aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: in function `sysfb_init':
sysfb.c:(.init.text+0xc): undefined reference to `screen_info'
aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `screen_info' which may bind externally can not be used when making a shared object; recompile with -fPIC
sysfb.c:(.init.text+0xc): dangerous relocation: unsupported relocation
aarch64-none-linux-gnu-ld: sysfb.c:(.init.text+0x10): undefined reference to `screen_info'
make[1]: *** [/tmp/next/build/Makefile:1276: vmlinux] Error 1

Caused by

  d391c58271072d0b0f ("drivers/firmware: move x86 Generic System Framebuffers support")

or one of the related commits.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Javier Martinez Canillas <javierm@redhat.com>,
	Borislav Petkov <bp@suse.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: dri-devel@lists.freedesktop.org,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failure due to the drm tree
Date: Mon, 26 Jul 2021 22:36:00 +0100	[thread overview]
Message-ID: <20210726213600.4054-1-broonie@kernel.org> (raw)

Hi all,

Today's -next fails to build an arm64 allnoconfig:

aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: in function `sysfb_init':
sysfb.c:(.init.text+0xc): undefined reference to `screen_info'
aarch64-none-linux-gnu-ld: drivers/firmware/sysfb.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `screen_info' which may bind externally can not be used when making a shared object; recompile with -fPIC
sysfb.c:(.init.text+0xc): dangerous relocation: unsupported relocation
aarch64-none-linux-gnu-ld: sysfb.c:(.init.text+0x10): undefined reference to `screen_info'
make[1]: *** [/tmp/next/build/Makefile:1276: vmlinux] Error 1

Caused by

  d391c58271072d0b0f ("drivers/firmware: move x86 Generic System Framebuffers support")

or one of the related commits.

             reply	other threads:[~2021-07-26 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 21:36 Mark Brown [this message]
2021-07-26 21:36 ` linux-next: build failure due to the drm tree Mark Brown
2021-07-26 21:36 ` Mark Brown
2021-07-26 22:08 ` Javier Martinez Canillas
2021-07-26 22:08   ` Javier Martinez Canillas
2021-07-26 22:08   ` Javier Martinez Canillas

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=20210726213600.4054-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=bp@suse.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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.