Re: nds broken by recent patches

On 1/28/2022 3:18 AM, Mike Frysinger wrote:

> np.  if my changes break a target, feel free to kick it up and i'll take a
> look.  shouldn't be too hard as long as the port is healthy and binutils &
> gcc work properly.  just remember to highlight the exact tuple you're using
> so i don't have to try and guess for these esoteric targets.  i tried to use
> nds32-elf here and that doesn't work, so i had to dig through grep output to
> see that nds32le-elf seems to work.
Well, part of the problem is we've got multiple targets failing in many 
different ways.

For example, someone mucked up the compiler for or1k-elf at the same 
time you're doing your refactoring.  Now I've got a patch to fix the 
compiler ICE, *but* I'm also getting a crap-ton of new testsuite 
failures in the testsuite due to missing _init/_fini symbols.  I don't 
know yet if that's a newlib issue or something else mucked up on the 
compiler side.

The h8300-elf port in the last few days has started failing while 
building newlib with:

cp: cannot stat 'libc/crt0.o': No such file or directory

The iq-2000-elf port has started failing building newlib in the last few 
days with:

make[3]: *** No rule to make target 'configure', needed by 
'config.status'.  Stop.
make[3]: Leaving directory 
'/home/jlaw/jenkins/workspace/iq2000-elf/iq2000-elf-obj/newlib/iq2000-elf/libgloss/iq2000'
make[2]: *** [Makefile:132: stmp-bsp] Error 2


And there's others.  Some are definitely on the GCC side (arc failures 
for example) , but having so many things breaking at once is frustrating.

Jeff