Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#53105 closed defect (fixed)

qt5-qtbase @5.6.2: configure fails due to invalid compiler *clang*

Reported by: mndavidoff (Monte Davidoff) Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: jeremyhu (Jeremy Huddleston Sequoia), dbevans (David B. Evans), majoc-at-astro (majoc-at-astro), gnw3, BSeppke (Benjamin Seppke), eborisch (Eric A. Borisch)
Port: qt5-qtbase poppler

Description

I get the following error when trying to install qt5-qtbase.

$ sudo port -vs install qt5-qtbase
...
--->  Configuring qt5-qtbase
Error: org.macports.configure for port qt5-qtbase returned: Invalid value for configure.compiler: *clang*

This problem might be related to f892d8b.

Attachments (1)

main.log.gz (4.8 KB) - added by mndavidoff (Monte Davidoff) 2 years ago.

Download all attachments as: .zip

Change History (15)

Changed 2 years ago by mndavidoff (Monte Davidoff)

Attachment: main.log.gz added

comment:1 Changed 2 years ago by BSeppke (Benjamin Seppke)

This error occurs for me (MacPorts 2.3.5, Mac OS X Sierra 10.12.2, XCode 8.2 (8C38)) for opencv, too. Seems, that any port with that *clang* setting cannot be build, since that compiler cannot be found.

Since this is more a system than a port dependent issue it should be fixed rather soon and gain high priority.

comment:2 Changed 2 years ago by dbevans (David B. Evans)

Port: poppler added

This error applies to any port using PortGroup qt5. For instance, poppler-qt5 now fails in a similar fashion.

As previously stated, appears to have been introduced by the use of

compiler.whitelist *clang*

in f892d8b.

Last edited 2 years ago by dbevans (David B. Evans) (previous) (diff)

comment:3 Changed 2 years ago by dbevans (David B. Evans)

Cc: dbevans added

comment:4 Changed 2 years ago by majoc-at-astro (majoc-at-astro)

Cc: majoc-at-astro added

comment:5 Changed 2 years ago by gnw3

Cc: gnw3 added

comment:6 Changed 2 years ago by BSeppke (Benjamin Seppke)

Cc: BSeppke added

comment:7 Changed 2 years ago by eborisch (Eric A. Borisch)

Cc: eborisch added

comment:8 Changed 2 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Owner: set to MarcusCalhoun-Lopez
Resolution: fixed
Status: newclosed

comment:9 Changed 2 years ago by jmroot (Joshua Root)

Cc: jeremyhu added; mcalhoun@… jeremyhu@… removed

comment:10 Changed 2 years ago by jmroot (Joshua Root)

In d028ea23/macports-ports:

Achieve the intent of f892d8b

Globs can be used in the blacklist, so blacklist all the gccs, which
is the same as whitelisting all the clangs, since those are the only
two kinds of compiler in compiler.fallback.

See: #53105

comment:11 Changed 2 years ago by RJVB (René Bertin)

Isn't blacklisting all gcc compilers something that should only be done on 10.9 and up which have sufficient C++11 support in clang?

I know that building with gcc isn't supported officially as a substitute for doing a libc++ conversion, but is that a reason to make it impossible?

comment:12 Changed 2 years ago by jeremyhu (Jeremy Huddleston Sequoia)

It's odd that port lint caught that compiler.whitelist clang was not valid but did not catch that compiler.whitelist *clang* was not valid. Any idea why that is?

comment:13 Changed 2 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

comment:14 Changed 2 years ago by jmroot (Joshua Root)

In 761cbc0b/macports-ports:

Achieve the intent of f892d8b

Globs can be used in the blacklist, so blacklist all the gccs, which
is the same as whitelisting all the clangs, since those are the only
two kinds of compiler in compiler.fallback.

See: #53105

Note: See TracTickets for help on using tickets.