From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Catalin Marinas <catalin.marinas@arm•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Russell King <linux@arm•linux.org.uk>,
Ard Biesheuvel <ard.biesheuvel@linaro•org>
Subject: linux-next: build failure after merge of the arm64 tree
Date: Fri, 27 Mar 2015 11:15:31 +1100 [thread overview]
Message-ID: <20150327111531.702b331f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Hi Catalin,
Yesterday's linux-next overnight builds (most arm builds) failed like
this:
./arch/arm/kernel/vmlinux.lds:677: undefined symbol `__hyp_idmap_size' referenced in expression
See, for example,
http://kisskb.ellerman.id.au/kisskb/buildresult/12391163/ . Have a look
at http://kisskb.ellerman.id.au/kisskb/head/8631/ to see the full
carnage :-(
This has been happening for a couple of days and then before that we got:
/opt/cross/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld:./arch/arm/kernel/vmlinux.lds:544: syntax error
We are using gcc 4.6.3 and binutils 2.22 to do these builds.
I have reverted
12eb3e833961 ARM: kvm: assert on HYP section boundaries not actual code size
e60a1fec44a2 ARM: kvm: implement replacement for ld's LOG2CEIL()
06f75a1f6200 ARM, arm64: kvm: get rid of the bounce page
from linux-next today. Please address this ASAP.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-03-27 0:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 0:15 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-21 23:41 linux-next: build failure after merge of the arm64 tree Stephen Rothwell
2022-11-22 4:17 ` Jiucheng Xu
2022-11-22 4:52 ` Stephen Rothwell
2022-11-15 22:04 Stephen Rothwell
2022-11-15 23:52 ` Besar Wicaksono
2022-11-16 10:49 ` Suzuki K Poulose
2019-08-06 23:50 Stephen Rothwell
2019-08-07 2:34 ` Peter Collingbourne
2019-08-07 11:46 ` Will Deacon
2019-08-07 14:43 ` Masahiro Yamada
2019-08-07 15:25 ` Will Deacon
2019-08-07 16:33 ` Peter Collingbourne
2019-08-07 23:43 ` Stephen Rothwell
2019-08-16 4:52 ` Michael Ellerman
2019-08-16 17:27 ` Will Deacon
2019-08-20 7:27 ` Michael Ellerman
2012-09-17 1:24 Stephen Rothwell
2012-09-17 8:41 ` Catalin Marinas
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=20150327111531.702b331f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ard.biesheuvel@linaro$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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