Bug 226655 - security/p5-Net-SSLeay: compilation fails
Summary: security/p5-Net-SSLeay: compilation fails
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-perl (Nobody)
URL: mat
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-16 13:15 UTC by oz42
Modified: 2018-03-22 14:53 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (perl)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description oz42 2018-03-16 13:15:55 UTC
System is 11.1-RELEASE-p8 amd64.


===>  License OpenSSL accepted by the user
===>   p5-Net-SSLeay-1.85 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by p5-Net-SSLeay-1.85 for building
===>  Extracting for p5-Net-SSLeay-1.85
=> SHA256 Checksum OK for Net-SSLeay-1.85.tar.gz.
===>  Patching for p5-Net-SSLeay-1.85
===>  Applying FreeBSD patches for p5-Net-SSLeay-1.85
===>   p5-Net-SSLeay-1.85 depends on file: /usr/local/lib/libcrypto.so.42 - found
===>   p5-Net-SSLeay-1.85 depends on package: perl5>=5.24<5.25 - found
===>  Configuring for p5-Net-SSLeay-1.85
Unresolvable missing external dependency.
This package requires a C compiler.
NA: Unable to build distribution on this platform.
Can't open Makefile: No such file or directory.
===>  Building for p5-Net-SSLeay-1.85
make[2]: cannot open Makefile.


C compiler is available:

# /usr/bin/cc --version
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
Target: x86_64-unknown-freebsd11.1
Thread model: posix
InstalledDir: /usr/bin
Comment 1 Mathieu Arnold freebsd_committer freebsd_triage 2018-03-22 14:11:55 UTC
I have tried quite a lot of things to try and reproduce this, I cannot seem to find anything. Could you provide your environment, like make.conf, and any other appropriate files you can think of?
Comment 2 oz42 2018-03-22 14:36:41 UTC
Unfortunately I cannot reproduce this behaviour, I just have tried.