Hi again!
It shouldn't be needed to build GDB separately or to specify the -m32 flags. Not sure why you have to do that.
It was in the document you sent, especially some warning about sh-elf-run not working on 64-bit hosts. Guess that's solved by now.
I've just tried the following configure lines: (...)
Thanks, this flow worked for me as well. I'm now running the tests; quite a few fail, all C++. I'll have to control for without/with my change, try a few architectures, and report back. (Wow it's slow.)
There is some activity on the software side which mainly stems from folks using old parts and systems. I'd say the biggest activity is now people hammering on Sega 32X (SH2), Saturn (SH2) and Dreamcast (SH4), but I might be biased here.
I come from a community that works on CASIO graphing calculators. CASIO is still producing new models with SH4AL-DSP cores (SH7305), including some this year and next year. Seeing the latest updates they don't seem to have any intention to change it anytime soon either. Not a large community (I'd say a few dozen rotating people a year) but still there.
From what I know it started during the earlier cygwin days in the 90s, originally contracted by Hitachi to complement their own in-house C compiler and also to allow sh-linux to happen at some point. It was entertained by Renesas for a while through further contracted support work but eventually they have abandoned it. STmicro was also a licensee of the SH4 CPU for their TV set top boxes and had a few guys submitting patches now and then for a while. But the whole thing basically went on life support about 10 years ago.
Thanks for the insight. It's quite telling that things are still working after 10 years of "life support". :-)
Sébastien