mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.14-rc3-rt13 build problem (Invoked `ld.so')
Date: Sat, 8 Oct 2005 16:59:12 -0700	[thread overview]
Message-ID: <5bdc1c8b0510081659j3235063bi49e8251b1e4f7a7c@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0510081524g56a328f9ubad8a73bf6cd60d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2639 bytes --]

Attaching .config

On 10/8/05, Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
>    I've been quietly working here on my xrun issues. They are getting
> better with every kernel. I'm down to just a few a day now. However I
> am pretty reliably able to create at least one the first time I start
> up Firefox and browse the web. For this reason I thought I'd try
> learning to get some latency traces.
>
> 1) I built 2.6.14-rc3-rt13. It ran fine.
>
> 2) I built 2.6.14-rc3-rt13 with 'Debug Preemptible kernel' enabled. I
> get a message boot time warning me that the option is on, but the
> kernel boots and runs fine.
>
> 3) I then tried to 2.6.14-rc3-rt13 again as above but I added
> 'Non-preemptible critical section latency timing'. The compile failed.
> This is what's in my terminal:
>
>   CC      drivers/acpi/utilities/utobject.o
>   CC      drivers/acpi/utilities/utstate.o
>   CC      drivers/acpi/utilities/utmutex.o
>   CC      drivers/acpi/utilities/utcache.o
> Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
> You have invoked `ld.so', the helper program for shared library executables.
> This program usually lives in the file `/lib/ld.so', and special directives
> in executable files using ELF shared libraries tell the system's program
> loader to load the helper program from this file.  This helper program loads
> the shared libraries needed by the program executable, prepares the program
> to run, and runs it.  You may invoke this helper program directly from the
> command line to load and run an ELF executable file; this is like executing
> that file itself, but always uses this helper program from the file you
> specified, instead of the helper program file specified in the executable
> file you run.  This is mostly of use for maintainers to test new versions
> of this helper program; chances are you did not intend to run this program.
>
>   --list                list all dependencies and how they are resolved
>   --verify              verify that given object really is a dynamically linked
>                         object we can handle
>   --library-path PATH   use given PATH instead of content of the environment
>                         variable LD_LIBRARY_PATH
>   --inhibit-rpath LIST  ignore RUNPATH and RPATH information in object names
>                         in LIST
> make[3]: *** [drivers/acpi/utilities/utcache.o] Error 2
> make[2]: *** [drivers/acpi/utilities] Error 2
> make[1]: *** [drivers/acpi] Error 2
> make: *** [drivers] Error 2
> lightning linux #
>
>    Let me know how to proceed.
>
> Thanks,
> Mark
>

[-- Attachment #2: knecht.config-2.6.14-rc3-rt13.bz2 --]
[-- Type: application/x-bzip2, Size: 6526 bytes --]

      reply	other threads:[~2005-10-08 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-08 22:24 Mark Knecht
2005-10-08 23:59 ` Mark Knecht [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=5bdc1c8b0510081659j3235063bi49e8251b1e4f7a7c@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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

all inboxes | Powered by JetHome®