Opened 4 years ago

Last modified 4 years ago

#61517 closed defect

php70: error: too few arguments to function call, expected 3, have 2 — at Version 2

Reported by: HuabinLee (李先生) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: catalina bigsur Cc:
Port: php70

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I updated the system MacOS Big Sur, installed the latest version of port for Big Sur, and then tried to install php70, and found an error:

---> Installing php_ select @1.0_0
---> Activating php_ select @1.0_0
---> Cleaning php_ select
---> Fetching archive for php70
---> Attempting to fetch php70-7.0.33_ 3+ libedit.darwin_ 20.x86_ 64.tbz2 from https://pek.cn.packages.macports.org/macports/packages/php70
---> Attempting to fetch php70-7.0.33_ 3+ libedit.darwin_ 20.x86_ 64.tbz2 from https://nue.de.packages.macports.org/php70
---> Attempting to fetch php70-7.0.33_ 3+ libedit.darwin_ 20.x86_ 64.tbz2 from https://packages.macports.org/php70
---> Building php70
Error: Failed to build php70: command execution failed
Error: See /opt/local/var/macports/logs/_ opt_ local_ var_ macports_ sources_ rsync.macports.org_ macports_ release_ tarballs_ ports_ lang_ php/php70/ main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port php70 failed

Please help me

Change History (3)

Changed 4 years ago by HuabinLee (李先生)

Attachment: main.log added

comment:1 Changed 4 years ago by HuabinLee (李先生)

Description: modified (diff)

comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Keywords: catalina bigsur added
Milestone: MacPorts Future
Port: port install removed
Priority: HighNormal
Summary: macOS Big Sur - Failed to build php70: command execution failedphp70: error: too few arguments to function call, expected 3, have 2

Duplicate of #60988. Sorry, php is not compatible with macOS Big Sur yet. php73 and php74 are closer to being compatible than php72 and earlier, but even they won't work yet because of #61464.

Note: See TracTickets for help on using tickets.