public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Anton Blanchard <anton@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Kirill Tkhai <tkhai@yandex.ru>
Subject: New build failures in v3.13-rc1
Date: Sat, 23 Nov 2013 10:40:12 -0800	[thread overview]
Message-ID: <5290F68C.4060900@roeck-us.net> (raw)

Building arm:allmodconfig ... failed
--------------
Error log:
arch/arm/crypto/aesbs-glue.c:13:32: fatal error: crypto/ablk_helper.h: No such file or directory
compilation terminated.
make[1]: *** [arch/arm/crypto/aesbs-glue.o] Error 1

ablk_helper.h only exists in arch/x86/include/asm/crypto/ablk_helper.h,
so I am not entirely sure how this is supposed to work for arm.

Introduced by commit e4e7f10bfc (ARM: add support for bit sliced AES using NEON instructions).
Possibly resolved with the pending crypto update from Herbert Xu.

======================

Building ia64:defconfig ... failed
--------------
Error log:
arch/ia64/kernel/built-in.o: In function `skip_rbs_switch':
(.text+0xef2): undefined reference to `preempt_schedule_irq'

Caused by commit aa0d5326 (ia64: Use preempt_schedule_irq).

Reverting that commit fixes the problem.
Problem is known (https://lkml.org/lkml/2013/11/20/444) and being addressed.

======================

Building powerpc:allmodconfig ... failed
--------------
Error log:
<stdin>:1:0: error: -mcall-aixdesc must be big endian (several)
scripts/gcc-version.sh: line 31: printf: #: invalid number (several)
scripts/mod/empty.c:1:0: error: -mcall-aixdesc must be big endian

make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2

According to Stephen introduced by commit 7c105b63b (powerpc: Add CONFIG_CPU_LITTLE_ENDIAN kernel config option).

Reverting that commit fixes this problem, but unveils another.

drivers/tty/ehv_bytechan.c:363:1: error: type defaults to 'int' in declaration of 'console_initcall' [-Werror=implicit-int]

Not really surprising as console_initcall() is not defined for modules.
I am a bit at loss why this is only seen now, though.

=======================

Building sparc64:allmodconfig ... failed
--------------
Error log:
arch/sparc/kernel/kgdb_64.c: In function 'kgdb_trap':
arch/sparc/kernel/kgdb_64.c:162:7: error: implicit declaration of function 'exception_enter' [-Werror=implicit-function-declaration]
arch/sparc/kernel/kgdb_64.c:176:2: error: implicit declaration of function 'exception_exit' [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
make[2]: *** [arch/sparc/kernel/kgdb_64.o] Error 1

Introduced by commit 812cb83a5 (sparc64: Implement HAVE_CONTEXT_TRACKING).

Reverting that commit fixes the problem.

======================

Building xtensa:allmodconfig ... failed
--------------
Error log:
drivers/built-in.o:(.init.literal+0xd88): undefined reference to `i2c_register_driver'
drivers/built-in.o: In function `sram_probe':
sram.c:(.text+0x58f14): undefined reference to `devm_regmap_init_i2c'
drivers/built-in.o: In function `as3722_i2c_probe':
/opt/buildbot/slave/stable-queue-master/build/drivers/mfd/as3722.c:372: undefined reference to `devm_regmap_init_i2c'
drivers/built-in.o: In function `as3722_i2c_driver_init':
/opt/buildbot/slave/stable-queue-master/build/drivers/mfd/as3722.c:444: undefined reference to `i2c_register_driver'
make: *** [vmlinux] Error 1

A patch fixing this problem is pending (http://lkml.indiana.edu/hypermail/linux/kernel/1311.2/00669.html).

---

Guenter

             reply	other threads:[~2013-11-23 18:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 18:40 Guenter Roeck [this message]
2013-11-23 18:51 ` New build failures in v3.13-rc1 Geert Uytterhoeven
2013-11-23 19:13   ` Guenter Roeck
2013-11-23 20:08     ` Ard Biesheuvel
2013-11-23 20:25       ` Guenter Roeck
2013-11-23 20:12   ` Guenter Roeck
2013-11-23 21:10 ` Benjamin Herrenschmidt
2013-11-23 23:54 ` Kirill Tkhai
2013-12-30 21:03   ` Geert Uytterhoeven

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=5290F68C.4060900@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=anton@samba.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tkhai@yandex.ru \
    --cc=torvalds@linux-foundation.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