Opened 2 years ago
Last modified 7 days ago
#68874 new defect
cmake-1.1 portgroup: can't read "cmake._archflag_vars": no such variable
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | cooljeanius (Eric Gallager) | |
| Port: | cmake |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I tried to include the cmake 1.1 portgroup in a variant. This failed at configure time:
DEBUG: Executing proc-pre-org.macports.configure-configure-0
DEBUG: CPPFLAGS="-I/opt/local/include" inserted into CFLAGS="-Os -DNDEBUG -I/opt/local/include" CXXFLAGS="-Os -DNDEBUG -I/opt/local/include -stdlib=libc++"
(using ccache)
DEBUG: Executing proc-pre-org.macports.configure-configure-1
Error: Failed to configure tea: can't read "cmake._archflag_vars": no such variable
I could work around the problem by using:
global cmake._archflag_vars
before including the cmake 1.1 portgroup.
Change History (4)
comment:1 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Summary: | cmake portgroup: Error: Failed to configure tea: can't read "cmake._archflag_vars": no such variable → cmake portgroup: can't read "cmake._archflag_vars": no such variable |
comment:2 Changed 2 years ago by jmroot (Joshua Root)
The PortGroup mechanism was designed to be used at the top of a Portfile, not in a variant. This is one of the things that happens if you don't do that (because variants create a proc).
comment:3 Changed 23 months ago by kencu (Ken)
| Summary: | cmake portgroup: can't read "cmake._archflag_vars": no such variable → cmake-1.1 portgroup: can't read "cmake._archflag_vars": no such variable |
|---|
comment:4 Changed 7 days ago by cooljeanius (Eric Gallager)
| Cc: | cooljeanius added |
|---|
Note: See
TracTickets for help on using
tickets.

Similar problem with the qmake5 portgroup in #68875.