Hi Jonathan,
Thank you for the reply. Here are the errors that I see in that file. I
am not sure where to get that `schedule.h` file.
"configure:4460: $? = 0
configure:4449: gcc -V >&5
gcc: error: unrecognized command-line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:4460: $? = 1
configure:4449: gcc -qversion >&5
gcc: error: unrecognized command-line option '-qversion'; did you mean
'--version'?
gcc: fatal error: no input files
compilation terminated.
configure:4460: $? = 1
...
configure:8492: checking for isl 0.15 or later
checking for isl 0.15 or later... configure:8505: gcc -o conftest -g
-O2 -I/gmp-6.2.1/output/include
-I/mpfr-1.2.1
/output/include -I/mpc-1.2.1/output/include -I/gmp-6.2.1/output/include
-I/mpc-1.2.1/output/include -I/mpfr-1.2.1/
output/include -L/gmp-6.2.1/output/lib -Wl,--rpath=/gmp-6.2.1/output/lib
-L/mpc-1.2.1/output/lib -Wl,--rpath=/mpc-
1.2.1/output/lib -L/mpfr-1.2.1/output/lib
-Wl,--rpath=/mpfr-1.2.1/output/lib -lisl -L/gmp-6.2.1/output/lib -L/mpf
r-1.2.1/output/lib -L/mpc-1.2.1/output/lib -lmpc -lmpfr -lgmp conftest.c
-lgmp -lmpc -lmpfr -lisl -lgmp >&5
conftest.c:10:10: fatal error: isl/schedule.h: No such file or directory
10 | #include <isl/schedule.h>
| ^~~~~~~~~~~~~~~~
compilation terminated.
configure:8505: $? = 1"
I have also attached a sanitized `config.log`
Regards,
J
On Tue, Sep 13, 2022 at 7:37 AM Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
wrote:
> On Tue, 13 Sept 2022 at 14:43, Jerome Yanga via Gcc-help
> <gcc-help@xxxxxxxxxxx> wrote:
> >
> > Hello. I attempted to compile gcc but it failed with an error that is
> > unknown to me.
> >
> > Help.
> >
> > "checking whether the C compiler works... no
> >
> > configure: error: in
> > `/data/rock3/wine/builds/gcc-12.2.0/x86_64-pc-linux-gnu/libgomp':
> >
> > configure: error: C compiler cannot create executables
> >
> > See `config.log' for more details
>
> Did you do this?
>
> The error was in a sub-directory, so you want to check
> /data/rock3/wine/builds/gcc-12.2.0/x86_64-pc-linux-gnu/libgomp/config.log
>
> There will be lots of errors in that file, because the configure
> script tries lots of things that aren't all expected to work. You need
> to look for the problem that occurs just before it logs the "cannot
> create executables" message.
>
Attachment:
config.log
Description: Binary data
