From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Ingo Molnar <mingo@elte.hu>
Cc: Paul Mundt <lethal@linux-sh.org>,
linux-next@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: sh build failure
Date: Fri, 20 Mar 2009 14:24:13 -0400 [thread overview]
Message-ID: <20090320182413.GB1847@Krystal> (raw)
In-Reply-To: <20090320110602.86351a91.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
* Stephen Rothwell (sfr@canb.auug.org.au) wrote:
> Hi Paul,
>
> Yesterday's linux-next build of sh allmodconfig failed like this:
>
> kernel/built-in.o: In function `disable_all_kprobes':
> kernel/kprobes.c:1382: undefined reference to `text_mutex'
> kernel/built-in.o: In function `__unregister_kprobe_top':
> kernel/kprobes.c:773: undefined reference to `text_mutex'
> kernel/built-in.o: In function `register_kprobe':
> kernel/kprobes.c:724: undefined reference to `text_mutex'
>
> Introduced by commit 4460fdad85becd569f11501ad5b91814814335ff ("tracing,
> Text Edit Lock - kprobes architecture independent support") from the
> tracing tree. text_mutex is defined in mm/memory.c which is only built
> if CONFIG_MMU is defined, which is not true for sh allmodconfig.
Hrm, so we should move the text_mutex in a obj-y file. It's not clear to
me which of mm/Makefile would be the best choice :
obj-y := bootmem.o filemap.o mempool.o oom_kill.o fadvise.o \
maccess.o page_alloc.o page-writeback.o pdflush.o \
readahead.o swap.o truncate.o vmscan.o shmem.o \
prio_tree.o util.o mmzone.o vmstat.o backing-dev.o \
page_isolation.o mm_init.o $(mmu-y)
Or maybe we add a new file, or put this in kernel/*.c. Suggestions ?
Mathieu
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-03-20 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 0:06 linux-next: sh build failure Stephen Rothwell
2009-03-20 18:24 ` Mathieu Desnoyers [this message]
2009-03-20 18:34 ` Ingo Molnar
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=20090320182413.GB1847@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=hpa@zytor.com \
--cc=lethal@linux-sh.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.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 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).