[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEJqkgidhy8da14tkYD7OgUyOzGho43znP+g543_YDHjgRMQSQ@mail.gmail.com>
Date: Fri, 6 Jul 2018 19:31:21 +0200
From: Gabriel C <nix.or.die@...il.com>
To: "Kirill A. Shutemov" <kirill@...temov.name>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Benjamin Gilbert <bgilbert@...hat.com>,
linux-x86_64@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
bero@...dev.ch, Andi Kleen <ak@...ux.intel.com>,
Michal Marek <michal.lkml@...kovi.net>
Subject: Re: 4.17.x won't boot due to "x86/boot/compressed/64: Handle 5-level
paging boot if kernel is above 4G"
2018-07-06 18:33 GMT+02:00 Kirill A. Shutemov <kirill@...temov.name>:
> On Fri, Jul 06, 2018 at 04:39:28PM +0200, Gabriel C wrote:
>> > If not, we do not need to think about that case.
>> > Just say "Do not do that".
>>
>> I am sorry but I have a hard time to get your logic here.
>>
>> You are saying : the *env* variable LDFLAGS as well passing
>> LDFLAGS to make , which your build allows should not be use
>> because is for 'internal usage' .. ?
>
> Environment variables do not override make variables. Only passing varible
> assignment as make argument will do this.
>
Still .. When the build system allows to do 'make FOO=bar' and you know
when using that things will break , the build system should be fixed.
Powered by blists - more mailing lists