# Windows Perl - building Net::Curl

**URL:** <https://travis-ci.community/t/windows-perl-building-net-curl/5150>\
**Category:** Windows\
**Tags:** perl\
**Created:** [September 20, 2019, 3:15pm UTC](https://travis-ci.community/t/windows-perl-building-net-curl/5150 "2019-09-20T15:15:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![FGasper](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/fgasper/32/1883_2.png) [@FGasper](https://travis-ci.community/u/FGasper)\
**Post date:** [September 20, 2019, 3:15pm UTC](https://travis-ci.community/t/windows-perl-building-net-curl/5150/1 "2019-09-20T15:15:10Z")

</div>

[https://travis-ci.org/FGasper/p5-Net-Curl-Promiser/jobs/587349228](https://travis-ci.org/FGasper/p5-Net-Curl-Promiser/jobs/587349228)

^^ I’m trying to test a module that requires [Net::Curl](https://metacpan.org/pod/Net::Curl), but the build keeps failing because apparently Net::Curl can’t build … is the libcurl DLL not installed when I’m forcibly reinstalling curl?

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [September 20, 2019, 3:34pm UTC](https://travis-ci.community/t/windows-perl-building-net-curl/5150/2 "2019-09-20T15:34:33Z")

</div>

Without seeing the package’s build log, it’s impossible to say what specifically is wrong. Try `cpanm -v` and/or `cat`'ing the log file that the build refers to.

As can be seen from [a snapshot of a Windows builder](https://travis-ci.community/t/linking-against-ncurses-no-package-from-chocolately-yet/1030/4), it does have a `libcurl` and its headers installed as a Chocolatey package. Maybe some compiler switches or other envvars are needed for Strawberry Perl to find that library or something else that it needs.

---

<div class="post-metadata">

**Author:** ![FGasper](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/fgasper/32/1883_2.png) [@FGasper](https://travis-ci.community/u/FGasper)\
**Post date:** [September 20, 2019, 9:49pm UTC](https://travis-ci.community/t/windows-perl-building-net-curl/5150/3 "2019-09-20T21:49:49Z")

</div>

@native-api: Thank you; I’ve been trying various things. I realized that that PKG\_CONFIG\_PATH environment variable is empty; that may be what’s going on.

Is there some way to find out where all of the files in the curl chocolatey package are? Some equivalent to `rpm -ql`?

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [September 20, 2019, 11:35pm UTC](https://travis-ci.community/t/windows-perl-building-net-curl/5150/4 "2019-09-20T23:35:48Z")

</div>

> [@FGasper](#):
>
> Is there some way to find out where all of the files in the curl chocolatey package are?

No, there isn’t, since Chocolatey packages wrap stock installers and installation scripts rather than files directly like `rpm`. Package authors however [try to install everything under `%ALLUSERSPROFILE%\chocolatey\bin`, `%ALLUSERSPROFILE%\chocolatey\lib\[Package Name]` and such whenever possible](https://superuser.com/questions/786024/is-there-a-way-to-list-chocolatey-packages-with-their-install-directory) so you can check the snapshot. Of course, you can also install the same package locally and see what changed in the file system.