On 02/02/24 at 09:57am, Simon Horman wrote:
> On Fri, Feb 02, 2024 at 12:16:38PM +0800, Baoquan He wrote:
> > On 02/02/24 at 11:01am, Coiby Xu wrote:
> > > Hi,
> > >
> > > FYI, before this patch, Michel already sent "[PATCH] Fix building on
> > > x86_64
> > > with binutils 2.41" to address the
On Fri, Feb 02, 2024 at 12:16:38PM +0800, Baoquan He wrote:
> On 02/02/24 at 11:01am, Coiby Xu wrote:
> > Hi,
> >
> > FYI, before this patch, Michel already sent "[PATCH] Fix building on x86_64
> > with binutils 2.41" to address the same issue. Currently I almost know
> > nothing about
> >
On 02/02/24 at 11:01am, Coiby Xu wrote:
> Hi,
>
> FYI, before this patch, Michel already sent "[PATCH] Fix building on x86_64
> with binutils 2.41" to address the same issue. Currently I almost know
> nothing about
> assembly but Michel's patch seems to be more complete because two more
> files
Hi,
FYI, before this patch, Michel already sent
"[PATCH] Fix building on x86_64 with binutils 2.41"
to address the same issue. Currently I almost know nothing about
assembly but Michel's patch seems to be more complete because two more
files are touched.
On Wed, Jan 31, 2024 at 07:04:57PM
`binutils-2.42` introduced stricter checks on what `.arch` can be used
in 64-bit mode and started failing the build as:
$ as-2.42 --64 -o entry32-16-debug.o entry32-16-debug.s
purgatory/arch/i386/entry32-16-debug.S: Assembler messages:
purgatory/arch/i386/entry32-16-debug.S:28: Error:
On 01/31/24 at 10:05am, Sergei Trofimovich wrote:
> `binutils-2.42` introduced stricter checks on what `.arch` can be used
> in 64-bit mode and started failing the build as:
>
> $ as-2.42 --64 -o entry32-16-debug.o entry32-16-debug.s
> purgatory/arch/i386/entry32-16-debug.S: Assembler
