Running suggested example results in: symbol lookup error undefined symbol - Forum - Delft3D Flexible Mesh
Forum
- Home
- 2. Questions and troubleshooting
- 2.1 Questions about the software
- 2.1.1 Compiling the code
- Running suggested example results in: symbol lookup error undefined symbol
Running suggested example results in: symbol lookup error undefined symbol
Ronald Van Nooyen, modified 2 Years ago.
Running suggested example results in: symbol lookup error undefined symbol
Youngling Posts: 4 Join Date: 11/17/22 Recent Posts
On linux after compile. When trying to run the suggested example <myCode>/examples/12_dflowfm/test_data/e100_f02_c02-FriesianInlet_schematic_FM the error message symbol lookup error: <myCode>/build_all/lnx64/bin/../bin/dimr: undefined symbol: __libm_feature_flag_x pops up. Does anyone know what is going on here?
From file size alone it is clear that libimf.so in lnx64/lib is not copied from one of the files in the tree under /opt/intel/oneapi. Could that be the cause?
Found the probable cause: I am compiling netcdf with the intel compilers. Reason: the gnu compiler suite version used in versions 8 or 9 of Redhat clones to build epel packages is not one of those for which the intel compiler suite recognizes the netcdf module file. Going back to the tests for netcdf-c I spotted a failure with the same symbol problem. While researching this I found a website stating that hdf5 needs to be compiled with the same compiler as netcdf. Doing so resolved this particular problem.
From file size alone it is clear that libimf.so in lnx64/lib is not copied from one of the files in the tree under /opt/intel/oneapi. Could that be the cause?
Found the probable cause: I am compiling netcdf with the intel compilers. Reason: the gnu compiler suite version used in versions 8 or 9 of Redhat clones to build epel packages is not one of those for which the intel compiler suite recognizes the netcdf module file. Going back to the tests for netcdf-c I spotted a failure with the same symbol problem. While researching this I found a website stating that hdf5 needs to be compiled with the same compiler as netcdf. Doing so resolved this particular problem.