[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1907241801320.1791@nanos.tec.linutronix.de>
Date:   Wed, 24 Jul 2019 18:03:41 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Greg KH <gregkh@...uxfoundation.org>
cc:     "H.J. Lu" <hjl.tools@...il.com>,
        Mike Lothian <mike@...eburn.co.uk>,
        Tom Lendacky <thomas.lendacky@....com>, bhe@...hat.com,
        Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>, lijiang@...hat.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to
 be reserved
On Wed, 24 Jul 2019, Greg KH wrote:
> On Wed, Jul 24, 2019 at 05:49:45PM +0200, Thomas Gleixner wrote:
> > > Ok, I dug around and the gold linker is not being used here, only clang
> > > to build the source and GNU ld to link, and I am still seeing this
> > > error.
> > 
> > Odd combo.
> 
> I'm not disagreeing :)
> 
> Wait, does clang link things itself and not need ld?
Nah.
> > > Hm, clang 8 does not cause this error, but clang 9 does.  Let me go poke
> > > the people who are providing this version of clang to see if there's
> > > something they can figure out.
> > 
> > Let me try that with my clang variant. Which version of GNU ld are you
> > using?
> 
> I think it is 2.27:
> $ ./ld --version
> GNU ld (binutils-2.27-44492f8) 2.27.0.20170315
> 
> Which does feel old to me.
> 
> I know 2.32 works fine.
2.31 works fine as well.
> Gotta love old tool-chains :(
Oh yes. /me does archaeology to find a VM with old stuff
Powered by blists - more mailing lists
 
