- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My GitHub Actions started to fail recently, I believe it is related to the update to 2022.3. On my local system, I get
/usr/bin/ld: /usr/lib64/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib64/crt1.o: in function `_start':
/build/glibc/src/glibc/csu/../sysdeps/x86_64/start.S:103: undefined reference to `main'
when invoking mpicc -cc=icx or mpicc -cc=icc
2022.1 works.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thank you for posting on intel Communities.
Could you please provide us with Sample reproducer and steps to reproduce the issue, so that we can investigate more on your issue from our end?
Thanks,
Priyanshu.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I made a mistake when trying to reproduce the error.
I noticed it when compiling PETSc on Linux 5.19.13:
wget https://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.18.0.tar.gz
tar -xf petsc-3.18.0.tar.gz
cd petsc-3.18.0
./configure --with-fc=mpiifort --with-cc='mpiicc -cc=icc' --with-cxx='mpiicpc -cxx=icpc'
the problem is that --with-cc='mpiicc -cc=icc' gives a warning which confuses the configure script.
using
./configure --with-fc=mpiifort --with-cc='mpiicc -cc=icc -diag-disable=10441' --with-cxx='mpiicpc -cxx=icpc -diag-disable=10441'.
solves this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Glad to know that your issue is resolved. Thanks for sharing the solution with us.
If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.
Thanks,
Priyanshu.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page