gintctl does not compile anymore #1

New Issue

Closed

opened 2020-05-28 21:55:17 +02:00 by Darks · 4 comments

Darks commented

2020-05-28 21:55:17 +02:00

gintctl does not compile with fxsdk. See error below

$ make all-cg
sh-elf-gcc -c src/gintctl.c -o build-cg/src/gintctl.c.o -mb -ffreestanding -nostdlib -fstrict-volatile-bitfields -Wall -Wextra -Os -D FXCG50  -m4-nofpu -I include -MMD -MT build-cg/src/gintctl.c.o -MF build-cg/src/gintctl.c.d -MP
src/gintctl.c:5:10: fatal error: gint/syscalls.h: No such file or directory
    5 | #include <gint/syscalls.h>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:118 : build-cg/src/gintctl.c.o] Erreur 1

I'm using gint on branch compat, commit 4485e7f865.

It seems the file syscalls.h has been removed, thus breaking compilation of gintctl.

`gintctl` does not compile with fxsdk. See error below ``` $ make all-cg sh-elf-gcc -c src/gintctl.c -o build-cg/src/gintctl.c.o -mb -ffreestanding -nostdlib -fstrict-volatile-bitfields -Wall -Wextra -Os -D FXCG50 -m4-nofpu -I include -MMD -MT build-cg/src/gintctl.c.o -MF build-cg/src/gintctl.c.d -MP src/gintctl.c:5:10: fatal error: gint/syscalls.h: No such file or directory 5 | #include <gint/syscalls.h> | ^~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:118 : build-cg/src/gintctl.c.o] Erreur 1 ``` I'm using `gint` on branch `compat`, commit 4485e7f865. It seems the file `syscalls.h` has been removed, thus breaking compilation of `gintctl`.

Lephenixnoir commented

2020-05-28 21:57:47 +02:00

Owner

gintctl being the go-to test addin for gint features, you cannot avoid building gint from the dev branch if you're going to use it. ^^

gintctl being the go-to test addin for gint features, you cannot avoid building gint from the `dev` branch if you're going to use it. ^^

Darks referenced this issue

2020-05-28 22:11:11 +02:00

Removed useless <gint/syscall.h> include #2

Darks commented

2020-05-28 22:12:19 +02:00

Author

gintctl being the go-to test addin for gint features, you cannot avoid building gint from the dev branch if you're going to use it. ^^

As the concerned header is also missing in the dev branch, this does not fix the issue.

> gintctl being the go-to test addin for gint features, you cannot avoid building gint from the dev branch if you're going to use it. ^^ As the concerned header is also missing in the `dev` branch, this does not fix the issue.

Lephenixnoir commented

2020-05-28 22:40:03 +02:00

Owner

... eh, I kinda got confused right there. The removal of the syscalls header is not going to change, so you need to go to an earlier version of gint to build this application. I tested the dev/compat change too quickly, sorry.

gintctl is rarely up-to-date because I'm usually testing several features at once and it's only stable once in a while. (Using the Memory dump right now is likely to crash for instance).

I'll make sure to include a README with better instructions next time I push it. I'll keep your PR in the meantime so that it builds on the latest release, thank you.

... eh, I kinda got confused right there. The removal of the syscalls header is not going to change, so you need to go to an *earlier* version of gint to build this application. I tested the dev/compat change too quickly, sorry. gintctl is rarely up-to-date because I'm usually testing several features at once and it's only stable once in a while. (Using the Memory dump right now is likely to crash for instance). I'll make sure to include a README with better instructions next time I push it. I'll keep your PR in the meantime so that it builds on the latest release, thank you.

Lephenixnoir commented

2021-02-05 18:29:08 +01:00

Owner

This was fixed in fda5606c2a (long ago); the header had been removed at some point but had remained in my install tree, evading errors.

This was fixed in https://gitea.planet-casio.com/Lephenixnoir/gintctl/commit/fda5606c2aaa3a3eb16c51f5d3913f1d4bcf563d (long ago); the header had been removed at some point but had remained in my install tree, evading errors.

Lephenixnoir closed this issue

2021-02-05 18:29:10 +01:00

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Lephenixnoir/gintctl#1

No description provided.