linux-kernel - Re: [RESEND][REGRESSION] um: CONFIG_STATIC

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: <AANLkTilqSSfV3vR-fI1LxrsuSMt_M7_zaeT_xQuNVJL4@mail.gmail.com>
Date:	Fri, 18 Jun 2010 19:50:17 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	akpm@...ux-foundation.org, tabbott@...lice.com,
	linux-kernel@...r.kernel.org, Jeff Dike <jdike@...toit.com>,
	user-mode-linux-devel@...ts.sourceforge.net, stable@...nel.org
Subject: Re: [RESEND][REGRESSION] um: CONFIG_STATIC_LINK=y broken

On Fri, Jun 18, 2010 at 7:17 PM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> On Fri, Jun 18, 2010 at 17:22, richard -rw- weinberger
> <richard.weinberger@...il.com> wrote:
>> On Fri, Jun 18, 2010 at 4:27 PM, Geert Uytterhoeven
>> <geert@...ux-m68k.org> wrote:
>>> On Fri, Jun 18, 2010 at 15:49, richard -rw- weinberger
>>> <richard.weinberger@...il.com> wrote:
>>>> Andrew, Linus, Jeff, ... anyone?
>>>> Please apply this patch.
>>>>
>>>> CONFIG_STATIC_LINK is still broken. :(
>>>
>>> I wanted to verify Tim's patch, but after enabling CONFIG_STATIC_LINK,
>>> it fails to link
>>> (with or without your patch):
>>>
>>
>> BTW: Does CONFIG_STATIC_LINK work for you when you revert commit
>> 5d150a97f9391f5bcd7ba0d59d7a11c3de3cea80 (um: Clean up linker script
>> using standard macros)?
>
> Still the same linking errors ;-(
>

Are you using a non-x86 environment?
Maybe CONFIG_STATIC_LINK is more broken than i thought.

Cheers,
//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/