[Bug ada/116147] ADA Cross Compiler for ARM does not build
dldudley at gmail dot com
gcc-bugzilla@gcc.gnu.org
Wed Jul 31 17:30:32 GMT 2024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116147
--- Comment #14 from David Dudley <dldudley at gmail dot com> ---
OK, have the problems with the native compiler worked out. Configuration
problem on the host computer.
Now, it's building the native compiler using the new compiler with no problem.
This is planned to be a compiler for a "bare metal" system. Is there a way I
can disable the library for the cross compiler from being generated with
support for 'files', which I don't have on a bare metal machine?
The compiler fails with:
--------------------------------------------
In file included from /opt/arm-rtems6-eabi/include/dirent.h:39,
from adaint.h:43,
from adadecode.c:37:
/opt/arm-rtems6-eabi/include/sys/dirent.h:10:2: error: #error "<dirent.h> not
supported"
10 | #error "<dirent.h> not supported"
| ^~~~~
/opt/arm-rtems6-eabi/include/dirent.h:48:16: error: unknown type name ‘DIR’
48 | int dirfd(DIR *);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:51:21: error: unknown type name ‘DIR’
51 | int fdclosedir(DIR *);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:53:1: error: unknown type name ‘DIR’
53 | DIR *opendir(const char *);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:54:1: error: unknown type name ‘DIR’
54 | DIR *fdopendir(int);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:56:18: error: unknown type name ‘DIR’
56 | readdir(DIR *);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:58:20: error: unknown type name ‘DIR’
58 | int readdir_r(DIR *__restrict, struct dirent *__restrict,
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:61:20: error: unknown type name ‘DIR’
61 | void rewinddir(DIR *);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:72:18: error: unknown type name ‘DIR’
72 | void seekdir(DIR *, long);
| ^~~
/opt/arm-rtems6-eabi/include/dirent.h:73:18: error: unknown type name ‘DIR’
73 | long telldir(DIR *);
| ^~~
-----------------------------------------------
which makes perfect sense, since there is no file system.
Any suggestions (other than 'forget about it')?
David
More information about the Gcc-bugs
mailing list