linux-kernel - Re: FATAL: kenrel too old

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFLxGvzDvd+jR2Tsv1XVBdfzo9GF5AgPD=wdkUoskyFhLUnj-g@mail.gmail.com>
Date:	Thu, 27 Oct 2011 01:14:53 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	"Hebenstreit, Michael" <michael.hebenstreit@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: FATAL: kenrel too old - message

On Thu, Oct 27, 2011 at 1:04 AM, Hebenstreit, Michael
<michael.hebenstreit@...el.com> wrote:
> Can someone explain me why even an ldd on a dynamic executable gives a "kernel too old"? I understand that linking to a gcc that does not support the kernel causes this problem at runtime, but why does ldd fail? Are there other ways to diagnose this?
>

Because ldd executes the binary to get it's dependencies.
It's just a bash script.

-- 
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/