On 28 Jan 2022 09:36, Jeff Law wrote:
> 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.

i had tried to run the newlib testsuite, but it didn't seem to work out
of the box.  is there some trick/docs i'm missing to make them work ?

> 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

i pushed a fix for this, so retry latest please
https://sourceware.org/pipermail/newlib/2022/019024.html

> 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

i sent+pushed a fix for this
https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;h=580817ec0132265e6dfd0bb19b5deaf6b5866a35

> 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.

if your CI builders are public, point me at them and i can flip through.
i should be able to identify many of the libgloss/newlib ones that were
my fault a bit quicker.
-mike