public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Shayne O'Connor" <forums@machinehasnoagenda.com>
To: A list for linux audio users <linux-audio-user@music.columbia.edu>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [linux-audio-user] Problems appling realtime preempt patch to 2.6.12
Date: Wed, 13 Jul 2005 09:29:50 +1000	[thread overview]
Message-ID: <42D4526E.2040409@machinehasnoagenda.com> (raw)
In-Reply-To: <42D42F9A.40806@telus.net>

Iain Duncan wrote:
>>>> yeah, i got this as well ... hasn't seemed to have any noticeable 
>>>> effects, though.
>>>
>>>
>>> Huh? Does that mean the kernel image is built anyway? I was under the 
>>> impression that it meant it didn't finish compiling? Am I confused?
>>
>>
>>
>> If the error was in building a module that you don't use, then it would
>> be harmless.  This seems to be the case.
> 
> 
> Ah, excuse my ignorance please, but does that mean the rest *did* build, 
> or I need to somehow comment out building that module and do it again? 
> And if so, how would I do that? In the kernel makefile?
> 

hmmm ... when i built mine, i didn't get that message until doing:

sudo make modules_install

... it went through the process of installing the modules, and then - 
the very last line - it gave me:

> : undefined reference to `there_is_no_init_MUTEX_LOCKED_for_RT_semaphores' 

and it also gave me the same deal when doing:

sudo make install.

so, unless it compiled all the drivers/modules *before* exiting with 
error, i would try to find out the driver/module that is failing to 
compile, assess whether you need it or not, and try again (using "make 
gconfig").


shayne

           reply	other threads:[~2005-07-12 23:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <42D42F9A.40806@telus.net>]

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=42D4526E.2040409@machinehasnoagenda.com \
    --to=forums@machinehasnoagenda.com \
    --cc=linux-audio-user@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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