sure 😀 Without doing “+x” I will not being able to execute it. Without the dot-slash the error is not any strange to me I try another way. I install this: apt install lib32ncurses5 lib32z1 After doing it the “No

HI. I am running a “fresh” Debian on a 64 bit machine. I try to run the gcc-4.8.4.201803-GNURX-ELF.run file and get “No such file or directory”. That strange error mostly occurs, if the run-binary does not fit to the system.

Dear customer, Building, maintaining, optimizing and enhancing a compiler is a daunting challenge. As a result, we are not able at this moment, due to time-related efforts and various other considerations, to provide detailed and thorough explanations of all issues

I downloaded the gcc-4.8.4.201803-GNURX-ELF.run file from the gcc-renesas.com site and changed the permissions to allow it to execute, but I keep getting the error message “No such file or directory”.  I am on a 64 bit machine running Ubuntu 18.04.2. 

I am also attempting to build for the RX and get the same failure when I build gcc.  I am using Ubuntu 18.04 LTS and would like to either build my own or find a compatible pre-built toolchain for the

Hi Erika, I think it should be -misa=v2, not -mcpu=v2 Please kindly confirm Thank you

Hello, Unfortunately we could not reproduce stalling Extracting RL78 Debug with RL78 1803 toolchain. We have tried with e2studio 7.0, 7.2 both simulator and a R5F104PJ dev board. The extraction process in all cases and with multiple tries completed successfully

The RH850 is the next-generation of devices after V850. There are several cores: G3K 5-stage pipeline, no FPU, no multi-core support (very similar to V850E2S) G3KH 5-stage pipeline, single FPU, multi-core support G3M 7-stage pipeline, double FPU, multi-core support (very

Hello, The known issues for e2studio 7.0 are specified in the link below: https://www2.renesas.eu/_custom/software/ree_eclipse/e2studio7/docs/releasenotes/7.0.0/openissues.htm Unfortunately, we could not find anything referring to the usage of “Smart Configurator” in the known issues above. If you do experience any problems, please give

Hello, Our toolchain is GCC conformant, therefore it uses the standard way to declare interrupt handles, available on all platforms that have GCC compiler support. The first aspect is to declare interrupt handlers by using attribute pragma, eg: void interrupt_prototype(void)