Opened 3 years ago

Closed 3 years ago

#63921 closed defect (fixed)

php{70,71,74,80}-openssl cannot be built while openssl is active, expected?

Reported by: msbit (Tom Sullivan) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: cjones051073 (Chris Jones)
Port: php

Description

Same error message for each:

Error: phpXX-openssl cannot be built while openssl is active.
Error: Please forcibly deactivate openssl, e.g. by running:
Error: 
Error:     sudo port -f deactivate openssl
Error: 
Error: Then try again. You can reactivate openssl again later.
Error: Failed to configure php80-openssl: openssl is active
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_php/phpXX-openssl/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port php80-openssl failed

I know there has been some movement with openssl3 being added, so I was wondering if this error is expected, or whether php and these packages should instead depend on and build against openssl11?

Change History (9)

comment:1 Changed 3 years ago by jmroot (Joshua Root)

Owner: set to ryandesign
Status: newassigned

comment:2 Changed 3 years ago by cjones051073 (Chris Jones)

These ports have already been updated to use the openssl PG and pegged to version 1.1. The issue is there are bugs in the build configuration that means even though they have been configured to use an alternate install area for openssl 1.1, they still search the primary install prefix *first*. That means if you have the openssl shim port installed, that places sim links to the isolate openssl3 port into the primary prefix, these will still be found, and cause the builds to fail.

I tried my best to figure out how to convince the builds to not do this, but failed, so the second best is to do the above, so at least the user is given instructions how to work around this.

So in short, yes, this is expected, until someone figures out how to fix the builds to not require it.

https://github.com/macports/macports-ports/blob/55fce052aefad06996f45302f7bbc8e3ec011b3a/lang/php/Portfile#L1660

comment:3 Changed 3 years ago by cjones051073 (Chris Jones)

Cc: cjones051073 added

comment:4 Changed 3 years ago by msbit (Tom Sullivan)

👍

comment:5 Changed 3 years ago by cjones051073 (Chris Jones)

I do grant you that having X-openssl unable to build when openssl is activate is on the face of it peculiar. Its just a nuance of how the openssl PG and isolate builds work, but maybe a better warning could be issued in this case...

comment:6 Changed 3 years ago by cjones051073 (Chris Jones)

Resolution: wontfix
Status: assignedclosed

comment:7 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: wontfix
Status: closedreopened

Will fix; working on it.

comment:8 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Has duplicate #64007.

comment:9 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: reopenedclosed

In aa39eadc5f6042613c38e2fac7fbd9814063eecb/macports-ports (master):

php*-openssl: Fix build conflict with openssl

Closes: #63921

Note: See TracTickets for help on using tickets.