No rule to make target 'src/frontend/cxx-asttype.def', needed by 'src/frontend/cxx-asttype.c'. Stop.

[bsc-pm]

No rule to make target 'src/frontend/cxx-asttype.def', needed by 'src/frontend/cxx-asttype.c'. Stop.

[rofirrim]

Hi, this is a known issue.

Make sure you have bison, flex and gperf installed in your environment. Then run configure again and then make clean and make.

This should fix this issue.

[bhattacharyasarani]

Hi, thanks for your reply. It was very helpful, but did not solve the problem completely. Hoping you can help me this time as well.

Bison and flex were already installed, I added the installation of gperf.
Now the make progressed a few steps, but stopped with another error.

Pasting the console output for make:

CCBUILD lib/perish.o
CCBUILD lib/tpp.o
CCBUILD lib/tpp
PYTHON src/frontend/cxx-asttype-nodecl.def
TPP src/frontend/cxx-asttype.def
tpp - a tiny preprocessor for mcxx 2.3.0
GEN src/frontend/cxx-asttype.h
GEN src/frontend/cxx-asttype.c
TPP src/frontend/c99.l
tpp - a tiny preprocessor for mcxx 2.3.0
chmod: src/frontend/c99.l: new permissions are r-xrwxrwx, not r-xr-xr-x
make: *** [Makefile:12662: src/frontend/c99.l] Error 1

[rofirrim]

Hi,

src/frontend/c99.l tpp - a tiny preprocessor for mcxx 2.3.0 chmod: src/frontend/c99.l: new permissions are r-xrwxrwx, not r-xr-xr-x make: *** [Makefile:12662: src/frontend/c99.l] Error 1

Not sure what is this problem. Looks like an issue with the umask or maybe the filesystem you are using inside WSL2 does not allow this combination.

[bhattacharyasarani]

Hi, Thanks you were right. It was indeed a problem of wsl2.
I could manage to install both mercurium and nanos6 in a separate environment.

I could see the compilers generated in mcxx/bin folder.
Thanks :)

But this time I have a followup querry as to how to use this.
Because following the example shown in the nanos github page,
I am trying to simply run a hello world code with the following
$mcxx/bin/mcc -c --ompss-2 hello.c
But it shows the following error
"gcc: fatal error: cannot specify ‘-o’ with ‘-c’, ‘-S’ or ‘-E’ with multiple files"

Am I still missing something? Please let me know what you think.

[rofirrim]

Can you run with --v to see how gcc is being invoked by mcc?

[bhattacharyasarani]

Pasting the full message below:

Loading compiler phases for profile 'mcc'
Compiler phases for profile 'mcc' loaded in 0.04 seconds
Compiling file 'omp_exm.c'
gcc -E -D_OMPSS_2=1 -I -include nanos6.h -std=gnu99 -D_MCC -D_MERCURIUM -o /tmp/mcc_zRRk5X omp_exm.c
gcc: fatal error: cannot specify ‘-o’ with ‘-c’, ‘-S’ or ‘-E’ with multiple files
compilation terminated.
Preprocessing failed. Returned code 1
Preprocess failed for file 'omp_exm.c'
Removing temporary filename '/tmp/mcc_zRRk5X'

[rofirrim]

gcc -E -D_OMPSS_2=1 -I -include nanos6.h -std=gnu99 -D_MCC -D_MERCURIUM -o /tmp/mcc_zRRk5X omp_exm.c

This alone -I flag suggests your configuration of Mercurium is not right and doesn't have the right path to nanos6. This is confusing gcc

[bhattacharyasarani]

Hi, thanks so much for the prompt reply.

Okay I understand the problem, because while configuring I did not mention the location to nanos install directory to break the chicken-egg problem mentioned.

But now how do I explicitly link these two? I mean how to make nanos6.h available to mcc compiler?

[bhattacharyasarani]

Hi, I was trying more on this. With the following command,
gcc -E -D_OMPSS_2=1 -I -include nanos6.h -std=gnu99 -D_MCC -D_MERCURIUM -o /tmp/mcc_zRRk5X omp_exm.c
if I remove explicitly -E and provide the path to the nanos6.h directory then this works fine and the new executable is stored in /tmp/mcc_OHggqQ
Now my question is, is there a way to change the generation of these flags, in that case which file should I edit?

[rofirrim]

But now how do I explicitly link these two? I mean how to make nanos6.h available to mcc compiler?

At configure time you have to pass --with-nanos6 as explained here

https://pm.bsc.es/ftp/ompss-2/doc/user-guide/build/index.html#installation-of-mercurium-compiler

Hope this helps.

[bhattacharyasarani]

It works perfectly now.
Thank you so much for being so patient and helpful.