| Summary: | audio/logitechmediaserver: build IO::Socket::SSL so plugins work (e.g. RadioParadise) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | hartzell | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Some People | CC: | ports | ||||
| Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ports) |
||||
| Version: | Latest | ||||||
| Hardware: | amd64 | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
hartzell
2019-02-03 19:44:44 UTC
This hangs for me running the SSL tests; rm -f blib/arch/auto/Net/SSLeay/SSLeay.so LD_RUN_PATH="/usr/lib" cc -shared -L/usr -L/usr/lib -L/usr/local/lib/perl5/5.28/mach/CORE -lperl -L/usr/local/lib -fstack-protector-strong SSLeay.o -o blib/arch/auto/Net/SSLeay/SSLeay.so \ -L/usr -L/usr/lib -lssl -lcrypto -lz \ chmod 755 blib/arch/auto/Net/SSLeay/SSLeay.so Skip blib/lib/Net/SSLeay/Handle.pm (unchanged) Skip blib/lib/Net/SSLeay.pm (unchanged) Skip blib/lib/Net/SSLeay.pod (unchanged) PERL_DL_NONLAZY=1 "/usr/local/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/local/*.t t/handle/local/*.t t/handle/local/05_use.t ................ ok t/local/01_pod.t ....................... skipped: Test::Pod 1.00 required for testing POD t/local/02_pod_coverage.t .............. skipped: these tests are for only for release candidate testing. Enable with RELEASE_TESTING=1 t/local/03_use.t ....................... ok t/local/04_basic.t ..................... ok t/local/05_passwd_cb.t ................. ok t/local/06_tcpecho.t ................... ok t/local/07_sslecho.t ................... 1/78 ^Cgmake[2]: *** [Makefile:984: test_dynamic] Interrupt *** Signal 2 *** Signal 2 @Mark -- thanks for taking it for a test drive. It works for me(tm). I'm using it in a FreeNAS 11.2 jail on amd64. Can you tell me more about your test environment? It looks like that test is starting up a test service listening on 127.0.0.1 and then talking to it. Is there any firewalling or ... in place that would get in the way of that? g. I had a quick look - the test seems to assume localhost is equivalent to 127.0.0.1 (which it may not be in an ipv6 world), so it might be as simple as that. It's a pain to test because it seems to overwrite the files every build. I'd need to spend more time. I'm also on a VM, FreeBSD 12 running on KVM/Qemu on my Linux box. I can maybe try on bare metal FreeBSD another time. Adding SSL out of the box is definitely something we should do though. Let me know how I can help. I haven't tried it on a DO droplet, but it should work (famous last words...). If you like, I can give it a run there, or an AWS instance. Are you running an IPv6 system? Is there anything in your KVM setup that would prevent a loop-back style test from working (are all ports available by default?)? g. This patch does not work with FreeBSD 12 and perl5.30. I believe that the version of IO:Socket::SSL in the vendor tree is simply too far out of date to be worth bothering with.
PiCorePlayer pulls in the OS version as a dependency, and I've changed my personal port to add:
```
RUN_DEPENDS=ca_root_nss>0:security/ca_root_nss \
p5-IO-Socket-SSL>0:security/p5-IO-Socket-SSL
```
which seems to make things happy and is way simpler.
|