Linking curl, lz, and ldl to netCDF

[Stephen J. Butler]

Your project is linking against the static versions of netCDF and hdf5. I
believe the proper solution to your problem is adding -lcurl, -lz, and -ldl
to the linker flags of your project.

On Wed, Sep 23, 2015 at 3:57 PM, Ryan Jamison <ryan.d.jamison at gmail.com>
wrote:

> I'm trying to build a code that requires netCDF and hdf5. I keep getting
> the errors shown in the attached log file. It appears to me there are
> issues with lcurl and lz.
>
>
>
> On Wed, Sep 23, 2015 at 2:40 PM, Ryan Schmidt <ryandesign at macports.org>
> wrote:
>
>>
>> On Sep 23, 2015, at 2:49 PM, Ryan Jamison wrote:
>>
>> > I was wondering how one goes about linking curl (-lcurl), -lz, and -ldl
>> to netCDF that's build through Macports? Thanks,
>>
>> Looks like curl support is added to netcdf by enabling the dap variant.
>> It's on by default so you should already have it, unless you explicitly
>> disabled it.
>>
>> My copy of netcdf is also already linking with libz. I'm not sure if
>> that's because of curl (which itself depends on libz) or for other reasons.
>> Maybe netcdf needs to have a zlib dependency added.
>>
>> My copy of netcdf is not linked with libdl and I don't see a way in the
>> portfile to do that. What would linking with libdl accomplish?
>>
>>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20150923/9a0e31e0/attachment.html>