!CC compilation stalled with BB-xM

Hello

I am running DDE/27 on a BBG-xM with RiscOS 5.22.
I tried to compile the “A Simple C Application Version 2” (Download 4.1) from the tutorial of Steve Fryatt.

This time, I did not forgot to add OSLib32 to the list of libraries ;)

Unfortunatelly, !CC is stalled and never completes… !CC never proposes the save window.

If I introduce a bug into the .c file, !CC detects it and display a trace.

Note: I compiled successfully this script on my OpenPandora with RiscOS 5.23

If anyone has a clue on what could cause the issue… Thank you in advanced.

François

Hello

I tried with a very simple “Hello World” program, and !CC is unable to complete the compilation on my BBG-xM with DDE27…

[code]
#include
#include

int main(int argc, char *argv[]) {
printf(“Hello world!\n”);
return 0;
}
[/code]

What could explain that I have no problem with my OpenPandora, but it stalls on my BBG-xM?

Hope someone will have a clue..

Try a more simple one, as you don’t need args and I don’t understand your includes.

#include <stdio.h>

int main(void) {
    printf("Hello, World!\n");
    return 0;
}

Hi

Includes were stdio.h and stdlib.h

No change… !CC just stalls.

I will try on my Raspberry PI…

No change… !CC just stalls.

Do you have a working directory? C files should be in a C folder and I think and O folder might be needed too.

yes.. I followed the titorial from Steve Fryatt.

yes.. I followed the titorial from Steve Fryatt.Also, on OpenPandora, this works just fine.

yes.. I followed the titorial from Steve Fryatt.Also, on OpenPandora, this works just fine.Regards

yes.. I followed the titorial from Steve Fryatt.Also, on OpenPandora, this works just fine.RegardsFrançois

yes.. I followed the titorial from Steve Fryatt.Also, on OpenPandora, this works just fine.RegardsFrançois

I’m a bit confused by your reply, but okay. I don’t know this “Steve Fryatt” tutorial you speak of, and you didn’t link to it.

The program I posted runs fine on !cc v5.72. Think I’m using DDE27

Assuming that you’re compiling manually via the CC utility on the iconbar, it might be an idea to add b to Features so that the compiler reports that it’s finished its work. Assuming that it then reports this, we can try and narrow the problem down more.

I don’t know this “Steve Fryatt” tutorial you speak of, and you didn’t link to it.

I suspect that it’s this one – I don’t know of any others. Note that it’s a work in progress, unfinished and very possibly a bad programmer’s blog – constructive suggestions for improvements are welcome.

unfinished and very possibly a bad programmer’s blog

Haha. I didn’t know of your site at the time I wrote that, and I wasn’t really thinking of any RO developer at the time either. What sucks is I am a bad programmer, so I doubt I’d accurately identify bad programmer blogs. I do have a few tricks to steer clear so I don’t learn anymore bad habits, though. T.T

Hi all

To summarize, I successfully compile the simple “Hello World” program above on
- Raspberry Pi I Model B, running RC15 with DDE/27 (!CC version 5.72)
- OpenPandora 1Ghz running RiscOS 5.23, with DDE/27 (!CC version 5.27)

But on BeagleBoard-xM, running RiscOS 5.22, with DDE/27, it pathetically failed with !CC stalling (never leaves the ‘Running’ state)…

Really weird!

Could anybody with a BeagleBoard-xM or ARMini and DDE confirms it works gor him/her?

Thank you in advance.

François

Could anybody with a BeagleBoard-xM or ARMini and DDE confirms it works gor him/her?

I can confirm that it works on a Beagleboard xM in DDE 27, because that’s where the tutorial was written…

Did you try turning the Verbose compiler option on as I suggested? What, if anything, did that reveal? Does the compiler think that it’s completed?

Thank you Steve, glad to hear it works on a BGB-xM…
It is currently trying to compile “Hello World” in verbose mode (Features set to ‘b’ )as I type.
In the windows “CC (Running)” this is all what I get is:
Norcroft RISC OS ARM C vsn 5.72 [07 Apr 2016]
SDFS::ARMini.$.Documents.Tutorials.C.chap03_VotrePremierProgramme.c.main: 0 warnings, 0 errors, 0 serious errors

But it is running for ever…

Still running, I can also feel it on the reactivity of my computer…

0 warnings, 0 errors, 0 serious errors

Pretty sure it’s done, then. A little windows pops up to save it. Clicking okay puts it into the working directory.

Hi James,

The window to save the compiled file never shows up, while it does on the radpberry pi and the openpandora.

This issue really drives me nuts…

François.

The window to save the compiled file never shows up, while it does on the radpberry pi and the openpandora.

Maybe mention it in bugs

I do not know, Steve has it working fine on a BeagleBoard-xM too… I suspect some incompatibilities on my side… but i wonder how to identify it without breaking my system…

Regards

F.

I would start with a clean !Boot. I remember strange problems when installing something via PackMan – I think it was called “UnixTools” or something like that. It introduced a lot of aliases for Unix-like commands right inside Predesk (or Tasks?) and subtly ruined DDE.

Another idea would be a broken frontend module – this would also be solved by a clean !Boot.

“UnixTools” or something like that. It introduced a lot of aliases for Unix-like commands right inside Predesk (or Tasks?) and subtly ruined DDE.

!CoreUtils does contain a link alias that ruins a build as described.

*which link will verify that.

Hi Steffen and Dave…
Well spotted! I removed CoreUtils and GCC4 with !PackMan and, after reboot, compilation is now working as expected.

Thank you so much to everybody for your help…

François