From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: linux-next: build failure after merge of the arm tree
Date: Thu, 3 Mar 2011 01:13:35 +1100 [thread overview]
Message-ID: <20110303011335.7a8dc21a.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
Hi Russell,
After merging the final tree, the linux-next 20110228 build (lots of arm
configs) failed like this:
stat: cannot stat `arch/arm/boot/compressed/../Image': No such file or directory
gcc-4.4.0-nolibc/arm-linux/bin/arm-linux-ld:--defsym _image_size=: syntax error
Presumably caused by commit d239b1dc093d551046a909920b5310c1d1e308c1
("ARM: 6746/1: remove the 4x expansion presumption while decompressing
the kernel").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-03-02 14:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 14:13 Stephen Rothwell [this message]
2011-03-02 15:55 ` linux-next: build failure after merge of the arm tree Nicolas Pitre
2014-04-10 1:35 Stephen Rothwell
2015-05-29 1:09 Stephen Rothwell
2017-04-20 22:40 Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 8:12 ` Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-06-14 19:23 ` Mason
2017-04-21 11:27 ` Mason
2020-01-19 21:24 Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin
2021-10-25 23:25 Stephen Rothwell
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
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=20110303011335.7a8dc21a.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=rmk@arm.linux.org.uk \
/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).