-
Notifications
You must be signed in to change notification settings - Fork 76
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
Always link to $Config{libs} on cygwin #353
Conversation
The cygwin failures look like they're because the system perl includes -lnsl in libs (and several others):
but a fresh build doesn't include them:
(miniperl because of the issue this PR is fixing.) |
Yeah, that's on me, I'll fix the cygwin actions to pull in nsl |
Also, I was in doubt on wether to use libs or perllibs. I suspect the latter is more appropriate, but both are not very well defined. |
That means that everyone else will have to do that as well, which appears to be a problem. |
The most recent versions of the perl Cygwin package have all had this -lnsl issue. Because of this, I have not been able to build any Perl module that uses XS code. However, if I build perl on Cygwin from source, I don't run into this issue. I am really at the edge of my knowledge her, but could this be a Cygwin problem rather than a perl problem? During Cygwin installation, the nsl package is not a prerequisite for the perl package, so I have no nsl library in my /lib directory on Cygwin. |
if libnsl is present during perl's build, it will be included in the list of wanted libraries. So if perl was build with libnsl laying around (as cygwin apparently does), it now needs to be around when extensions are build (which is rather unfortunate). I think we need a different fix for this problem. |
This is intended to fix Perl/perl5#17805
WIP because it needs testing. @pjacklam would you be able to do that?