Morning, Nick.
Thanks for your help. I have submitted a (possible) bug report for
that config project. If nothing else it would be nice to satisfy my
curiosity and know what the purpose of that particular coalescence is
for.
Cheers,
Pete Restall
On Tue, 2023-11-14 at 13:38 +, Nick Clifton
Hi Pete,
I believe it's the target normalisation in
config.sub (line 1055) that does it:
mips3*-*)
cpu=mips64
;;
Interesting...
That doesn't seem quite right to me but I don't know much about
binutils to know what the rationale is for that transfor
Afternoon, Nick. Thanks for getting back to me.
On Tue, 2023-11-14 at 12:28 +, Nick Clifton wrote:
> Hi Pete,
>
> > I've been attempting to build a cross-compiler for a MIPS32
> > microcontroller (specifically an M14KE) and I've been running into
> > problems that appear to stem from binutil
Hi Pete,
I've been attempting to build a cross-compiler for a MIPS32
microcontroller (specifically an M14KE) and I've been running into
problems that appear to stem from binutils silently coalescing 'mips32'
into 'mips64'.
What specifically are these problems ?
All configurations of the binut
Good Evening,
I've been attempting to build a cross-compiler for a MIPS32
microcontroller (specifically an M14KE) and I've been running into
problems that appear to stem from binutils silently coalescing 'mips32'
into 'mips64'.
The simplest reproduction is to extract binutils-2.41.tar.gz and then
