From: Stefan Assmann <sassmann@kpanic.de>
To: backports@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Subject: ckmake build issue with undefined symbol mcount
Date: Mon, 07 Apr 2014 15:57:43 +0200 [thread overview]
Message-ID: <5342AED7.5080505@kpanic.de> (raw)
Tree generated with
./gentree.py --clean --verbose --git-revision next-20140221 /root/linux-next /tmp/next
When running devel/ckmake I see the following
[...]
23 3.7.10 [ LINK ]
24 3.8.13 [ LINK ]
25 3.9.11 [ LINK ]
26 3.10.29 [ LINK ]
27 3.11.10 [ LINK ]
28 3.12.10 [ LINK ]
29 3.13.2 [ LINK ]
30 3.14-rc1 [ LINK ]
Looking at ckmake.log there seems to be a problem with mcount.
Building backport-include/backport/autoconf.h ... done.
/root/ksrc-backports/usr/src/linux-headers-3.7.10-030710-generic/arch/x86/Makefile:103: CONFIG_X86_X32 enabled but no binutils support
CC [M] /tmp/next/.tmp.ckmake/3.7.10/compat/lib-cordic.o
LD [M] /tmp/next/.tmp.ckmake/3.7.10/compat/compat.o
LD [M] /tmp/next/.tmp.ckmake/3.7.10/compat/cordic.o
Building modules, stage 2.
MODPOST 2 modules
WARNING: "mcount" [/tmp/next/.tmp.ckmake/3.7.10/compat/cordic.ko] undefined!
WARNING: "mcount" [/tmp/next/.tmp.ckmake/3.7.10/compat/compat.ko] undefined!
This is also the case for every kernel mentioned above.
Stefan
next reply other threads:[~2014-04-07 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 13:57 Stefan Assmann [this message]
2014-04-08 0:37 ` ckmake build issue with undefined symbol mcount Luis R. Rodriguez
2014-04-08 7:39 ` Stefan Assmann
2014-04-10 7:35 ` Stefan Assmann
2014-04-10 11:14 ` Arend van Spriel
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=5342AED7.5080505@kpanic.de \
--to=sassmann@kpanic.de \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.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.