From: John Stultz <john.stultz@linaro.org>
To: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: randconfig build error with next-20131216, in drivers/staging/android/ion
Date: Mon, 16 Dec 2013 11:37:29 -0800 [thread overview]
Message-ID: <52AF5679.1090701@linaro.org> (raw)
In-Reply-To: <CA+r1Zhh-ayJRcuApAh_E3ofM3Q=xH3Wo-ZHSdr7rCYd+YAKGaw@mail.gmail.com>
On 12/16/2013 05:53 AM, Jim Davis wrote:
> Building with the attached random configuration file,
>
> drivers/built-in.o: In function `ion_heap_freelist_add':
> (.text+0xf292c): undefined reference to `rt_mutex_lock'
> drivers/built-in.o: In function `ion_heap_freelist_add':
> (.text+0xf2958): undefined reference to `rt_mutex_unlock'
> drivers/built-in.o: In function `ion_heap_freelist_size':
> (.text+0xf2990): undefined reference to `rt_mutex_lock'
> drivers/built-in.o: In function `ion_heap_freelist_size':
> (.text+0xf29a0): undefined reference to `rt_mutex_unlock'
> drivers/built-in.o: In function `ion_heap_deferred_free':
> ion_heap.c:(.text+0xf2a2d): undefined reference to `rt_mutex_lock'
> ion_heap.c:(.text+0xf2a48): undefined reference to `rt_mutex_unlock'
> ion_heap.c:(.text+0xf2a6e): undefined reference to `rt_mutex_unlock'
> drivers/built-in.o: In function `ion_heap_freelist_drain':
> (.text+0xf2ab2): undefined reference to `rt_mutex_lock'
> drivers/built-in.o: In function `ion_heap_freelist_drain':
> (.text+0xf2aed): undefined reference to `rt_mutex_unlock'
> drivers/built-in.o: In function `ion_heap_init_deferred_free':
> (.text+0xf2b7c): undefined reference to `__rt_mutex_init'
> make: *** [vmlinux] Error 1
Thanks for the heads up! I'll chase these down!
-john
prev parent reply other threads:[~2013-12-16 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 13:53 randconfig build error with next-20131216, in drivers/staging/android/ion Jim Davis
2013-12-16 19:37 ` John Stultz [this message]
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=52AF5679.1090701@linaro.org \
--to=john.stultz@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.