FPGA Stratix 10 libsycl.so.5 Not Found

[irpeitzsch]

I am currently trying to run something on the Stratix 10 nodes on the Intel Devcloud, but when I do I get the following error:

error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory

Does anyone know how to fix this?

[DiyaN_Intel]

Hi, 

Thank you for posting in Intel communities.

Could you please share the sample reproducer code so that we can try to find out the issue from our end.

Regards,

Diya

[JVand22]

I've been having the same issue for a few days - the libsycl.so.5 error comes up when running any synthesized S10 design (even those that ran without issue before). I've checked multiple Stratix 10 nodes - s001-n142/n143/n144. Any updates on this?

[DiyaN_Intel · Accepted solution]

Hi ,

We ran mandelbrot sample on DevCloud with the old binary and got a similar error that you got.

The reason is oneAPI is updated to 2023.0 and in this "runtime of oneAPI 2023.0 is not backwards compatible". So, we can’t run the old binaries, in order to run the old binaries we need to rebuild those binaries again.

The workaround to resolve the above error is given in the screenshot below:

If you face any issues please connect back to us. 

If this resolves your issue, make sure to accept this as a solution. This would help others with similar issue. Thank you!

Regards, 

Diya 

[jbick819]

Hello,

Is there a way to use the old runtime for executing older binaries since this new version isn't backwards compatible?

My project works on the previous version of oneAPI and not the 2023.0 update, so I've been strictly using that older version for my project.

Thank you!

[DiyaN_Intel]

Hi, 

To stay with the previous version of oneAPI, you can setvar to the previous release

Source the setvars.sh script to setup the 2022.3 environment by using the below command:

source /glob/development-tools/versions/oneapi/2022.3/inteloneapi/setvars.sh

or

source /glob/development-tools/versions/oneapi/2022.3/inteloneapi/setvars.sh --force

If this resolves your issue, make sure to accept this as a solution. 

This would help others with similar issues. Thank you!

Thanks and Regards, 

Diya

[DiyaN_Intel]

Hi,

Glad to know that your issue is resolved. If you need any further assistance, please post a new question as this thread will no longer be monitored by Intel.

Regards,

Alekhya