Running suggested example results in: symbol lookup error undefined symbol https://dlt-acc.firelay.cloud/en/c/message_boards/find_thread?p_l_id=4041874&threadId=5559696 2026-05-12T16:53:11Z 2026-05-12T16:53:11Z Ronald Van Nooyen https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&messageId=5559695 2023-01-11T07:47:01Z 2023-01-09T12:27:19Z

On linux after compile. When trying to run the suggested example &lt;myCode&gt;/examples/12_dflowfm/test_data/e100_f02_c02-FriesianInlet_schematic_FM the error message symbol lookup error: &lt;myCode&gt;/build_all/lnx64/bin/../bin/dimr: undefined symbol: __libm_feature_flag_x pops up. Does anyone know what is going on here?<br />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?<br /><br />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.

Ronald Van Nooyen 2023-01-09T12:27:19Z