-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name collision with new UTF8 library, pnetcdf 1.6.1 #372
Comments
|
If pnetcdf is using utf8proc, then it needs to upgrade to the same versions we are using |
That was my thought; I have my hands full tonight but will pretend the relevant functions with nc_ tomorrow before turning back to unravel the issues with #319 on ARM. |
I found this problem as well. |
I was going to drop you a note this morning @wkliao but I'm glad to see you've already addressed this :). Once I get this taken care of I will return to resolving the issues on #319 so that we can finally get that taken care of and start using the latest parallel netcdf! Updating our regression test docker images to the latest Ubuntu has uncovered a handful of issues that needed to be resolved, so it's taken a little bit longer than expected. |
In trying to move our regression testing to newer versions of Ubuntu and the openmpi/mpich libraries, I've encountered a couple issues. The first, we have name collisions between libnetcdf and libpnetcdf, as shown below. These functions are utf8 related and I'm sure come from the adoption of the new utf8 library. I didn't think to check before merging into
master
, and I will refactor the netcdf functions to avoid this collision in the future. It first arose with netCDF but could have occurred in any application which uses the same open-source utf8 implementation.The text was updated successfully, but these errors were encountered: