failure to get gcc9 running

[Hans Goedbloed]

​

Hi,



I have upgraded my mid 2014 MacBook Pro to macOS 10.14 (Mojave) and installed 
macports and, next, tried to install gcc9. This resulted in an endless series 
of failures to activate ports, one after the other. At last, I took the recent 
advise to Ryan Schmidt (Nov. 2) of a similar problem to clean all ports:"sudo 
port clean all". This looked to bring me somewhat further, up the point that 
the procedure appeared to hang and the Mac fan made an enormous noise, and 
again it resulted in errors:


--

[/Users/hansgoedbloed]$sudo port install gcc9

Password:

---> Computing dependencies for gcc9

---> Cleaning gcc9

---> Updating database of binaries

---> Scanning binaries for linking errors

---> Found 9 broken files, matching files to ports

---> Found 4 broken ports, determining rebuild order

You can always run 'port rev-upgrade' again to fix errors.

The following ports will be rebuilt:

 cmake @3.15.5

 readline @8.0.000

 gdbm @1.18.1

 llvm-8.0 @8.0.1

Continue? [Y/n]: y

---> Computing dependencies for cmake

---> Cleaning cmake

---> Computing dependencies for readline

---> Cleaning readline

---> Computing dependencies for gdbm

---> Cleaning gdbm

Warning: No port perl5.8 found in the index.

---> Computing dependencies for llvm-8.0

---> Cleaning llvm-8.0

---> Scanning binaries for linking errors

---> Found 9 broken files, matching files to ports

---> Found 4 broken ports, determining rebuild order

---> Rebuilding in order

cmake @3.15.5

 readline @8.0.000

gdbm @1.18.1

llvm-8.0 @8.0.1

Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.

Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.

---> Computing dependencies for cmake

---> Fetching distfiles for cmake

---> Attempting to fetch cmake-3.15.5.tar.gz from 
https://distfiles.macports.org/cmake

---> Verifying checksums for cmake

---> Extracting cmake

---> Applying patches to cmake

---> Configuring cmake

---> Building cmake

---> Staging cmake into destroot

---> Deactivating cmake @3.15.5_0

---> Cleaning cmake

---> Uninstalling cmake @3.15.5_0

---> Cleaning cmake

Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.

Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.

---> Computing dependencies for cmake

---> Installing cmake @3.15.5_0

---> Activating cmake @3.15.5_0

---> Cleaning cmake

Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.

Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.

---> Computing dependencies for readline

---> Fetching distfiles for readline

---> Attempting to fetch readline-8.0.tar.gz from 
https://distfiles.macports.org/readline

---> Verifying checksums for readline

---> Extracting readline

---> Applying patches to readline

---> Configuring readline

---> Building readline

---> Staging readline into destroot

---> Unable to uninstall readline @8.0.000_0, the following ports depend on it:

--->   gdbm @1.18.1_1

Warning: Uninstall forced.  Proceeding despite dependencies.

---> Deactivating readline @8.0.000_0

---> Cleaning readline

---> Uninstalling readline @8.0.000_0

---> Cleaning readline

Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.

Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.

---> Computing dependencies for readline

---> Installing readline @8.0.000_0

---> Activating readline @8.0.000_0

---> Cleaning readline

Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.

Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.

---> Computing dependencies for gdbm

---> Fetching distfiles for gdbm

---> Attempting to fetch gdbm-1.18.1.tar.gz from 
https://distfiles.macports.org/gdbm

---> Verifying checksums for gdbm

---> Extracting gdbm

---> Applying patches to gdbm

---> Configuring gdbm

Error: Failed to configure gdbm, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/work/gdbm-1.18.1/config.log

Error: Failed to configure gdbm: configure failure: command execution failed

Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/main.log
 for details.

Error: rev-upgrade failed: Error rebuilding gdbm

Error: Follow https://guide.macports.org/#project.tickets to report a bug.

--


Then I took the advise to "install SDK as part 

Re: qt5-qt3d complains about system assimp missing

[Ryan Schmidt]

On Nov 4, 2019, at 14:25, Michael A. Leonetti wrote:

> My qt5 installation keeps complaining about missing linking files so I am 
> trying to reinstall and qt5-q3d complains about missing system-assimp.
> 
> Is there a variant I'm missing that I can disable?
> 
>> :debug:configure 
>> SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk'
>> :info:configure Executing:  cd 
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5"
>>  && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- 
>> -system-assimp
>> :debug:configure system:  cd 
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5"
>>  && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- 
>> -system-assimp
>> :info:configure Running configuration tests...
>> :info:configure Done running configuration tests.
>> :info:configure Configure summary:
>> :info:configure Qt 3D:
>> :info:configure   Assimp . yes
>> :info:configure   System Assimp .. no
>> :info:configure   Output Qt3D Job traces . no
>> :info:configure   Output Qt3D GL traces .. no
>> :info:configure   Use SSE2 instructions .. yes
>> :info:configure   Use AVX2 instructions .. no
>> :info:configure   Aspects:
>> :info:configure Render aspect  yes
>> :info:configure Input aspect . yes
>> :info:configure Logic aspect . yes
>> :info:configure Animation aspect . yes
>> :info:configure Extras aspect  yes
>> :info:configure Qt 3D Renderers:
>> :info:configure   OpenGL Renderer  yes
>> :info:configure Qt 3D GeometryLoaders:
>> :info:configure   Autodesk FBX ... no
>> :info:configure ERROR: Feature 'system-assimp' was enabled, but the 
>> pre-condition 'features.assimp && libs.assimp' failed.
>> :info:configure Check config.log for details.
>> :info:configure Command failed:  cd 
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5"
>>  && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- 
>> -system-assimp
>> :info:configure Exit code: 3

Looks like qt5-qt3d just requires assimp. Sounds like you should file a bug 
report and attach the full logs. qt5-qt3d does declare a dependency on assimp, 
so we would need to see the logs to know why qt3-qt3d thinks it's not there.

Re: failure to get gcc9 running

[Christopher Jones]

> 
> --->  Computing dependencies for gdbm
> --->  Fetching distfiles for gdbm
> --->  Verifying checksums for gdbm
> --->  Extracting gdbm
> --->  Applying patches to gdbm
> --->  Configuring gdbm
> Error: Failed to configure gdbm, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/work/gdbm-1.18.1/config.log
> Error: Failed to configure gdbm: configure failure: command execution failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/main.log
>  for details.
> Error: rev-upgrade failed: Error rebuilding gdbm
> Error: Follow https://guide.macports.org/#project.tickets 
>  to report a bug.
> --​
> 
> It all leads me nowhere. Was it a mistake to upgrade to macOS 1014 for this 
> MacBook? It all worked nicely before with the Fortran compiler g95. However, 
> that does not work anymore with the new system, so I had to download gcc9. 
> Gave me this enormous sequence of errors which I do not know how to fix. I 
> will greatly appreciate assistance on this. 

gcc9 works just fine on 10.14 so whatever you did to get into the state above, 
it is not normal. 

A few comments.

- Did you *really* correctly follow the migration instructions at

https://trac.macports.org/wiki/Migration 


? 

as I am not sure how you could get into such a mess if you had. Did you really 
remove *all* ports in order to reinstall them ?

- When you get errors like those above, you have to look into the log file that 
is referenced. e.g.

> Error: Failed to configure gdbm, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/work/gdbm-1.18.1/config.log

so, what does that log say ?

Honestly, the simplest solution might be to start again, as if you are doing an 
OS migration. So follow the instructions above, making sure to remove 
everything.

I would also suggest *not* just blinding reinstalling everything you previously 
had, so once you get to a point where you have an empty vanilla MacPOrts 
installation, please just run

> sudo port sync
> sudo port install gcc9

that, should work just fine. Then you can go from there adding what else you 
want.

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: failure to get gcc9 running

[Ryan Schmidt]

On Nov 4, 2019, at 10:12, Hans Goedbloed wrote:
​
> [/Users/hansgoedbloed]$sudo port install gcc9
> Password:
> ---> Computing dependencies for gcc9
> ---> Cleaning gcc9

First things first: this shows that gcc9 was already successfully installed 
before you ran this command.


> ---> Updating database of binaries
> ---> Scanning binaries for linking errors
> ---> Found 9 broken files, matching files to ports
> ---> Found 4 broken ports, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt:
>  cmake @3.15.5
>  readline @8.0.000
>  gdbm @1.18.1
>  llvm-8.0 @8.0.1
> Continue? [Y/n]: y


After any port install or upgrade, MacPorts checks all installed ports for 
linking errors. It found some on your system. We would need to see the output 
of "sudo port -d rev-upgrade" to know specifically what problems were found 
with those ports.


> Warning: No port perl5.8 found in the index.

perl5.8 was removed a long time ago. The current version is perl5.30. Nothing 
in MacPorts should be referencing perl5.8 anymore. (I found one port that was; 
I filed a ticket: https://trac.macports.org/ticket/59600)

Do you perhaps have any local Portfiles (check your 
/opt/local/etc/macports/sources.conf file) that might be very old and out of 
date?


> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.

I see below that you did run this command. Good.


> ---> Computing dependencies for cmake
> ---> Fetching distfiles for cmake
> ---> Attempting to fetch cmake-3.15.5.tar.gz from 
> https://distfiles.macports.org/cmake
> ---> Verifying checksums for cmake
>  
> ---> Extracting cmake
> ---> Applying patches to cmake
> ---> Configuring cmake
> ---> Building cmake
> ---> Staging cmake into destroot
> ---> Deactivating cmake @3.15.5_0
> ---> Cleaning cmake
> ---> Uninstalling cmake @3.15.5_0
> ---> Cleaning cmake
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> ---> Computing dependencies for cmake
> ---> Installing cmake @3.15.5_0
> ---> Activating cmake @3.15.5_0
> ---> Cleaning cmake
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> ---> Computing dependencies for readline
> ---> Fetching distfiles for readline
> ---> Attempting to fetch readline-8.0.tar.gz from 
> https://distfiles.macports.org/readline
> ---> Verifying checksums for readline
> ---> Extracting readline
> ---> Applying patches to readline
> ---> Configuring readline
> ---> Building readline
> ---> Staging readline into destroot
> ---> Unable to uninstall readline @8.0.000_0, the following ports depend on 
> it:
> --->   gdbm @1.18.1_1
> Warning: Uninstall forced.  Proceeding despite dependencies.
> ---> Deactivating readline @8.0.000_0
> ---> Cleaning readline
> ---> Uninstalling readline @8.0.000_0
> ---> Cleaning readline
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> ---> Computing dependencies for readline
> ---> Installing readline @8.0.000_0
> ---> Activating readline @8.0.000_0
> ---> Cleaning readline

Whatever the problem with cmake and readline was, MacPorts successfully rebuilt 
them so they are no longer broken.


> ---> Computing dependencies for gdbm
> ---> Fetching distfiles for gdbm
> ---> Attempting to fetch gdbm-1.18.1.tar.gz from 
> https://distfiles.macports.org/gdbm
> ---> Verifying checksums for gdbm
> ---> Extracting gdbm
> ---> Applying patches to gdbm
> ---> Configuring gdbm
> Error: Failed to configure gdbm, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/work/gdbm-1.18.1/config.log
> Error: Failed to configure gdbm: configure failure: command execution failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/main.log
>  for details.

We would need to see the contents of those two logfiles to know why this failed 
and what to do about it.


> Was it a mistake to upgrade to macOS 1014 for this MacBook?

As far as MacPorts goes, it should work fine.

Re: postgresql83-server - Further Woes

[Michael Newman via macports-users]

The only solution offered by the developer of DetectX was to tell DetectX to 
ignore changes to macports plist files. 

That seems to defeat the purpose of DetectX. 

DetectX is supposed to warn you of possible nefarious changes to your system. 
Choosing to ignore a possible problem is no solution.

> On Nov 4, 2019, at 21:29, Ryan Schmidt  wrote:
> 
> Well MacPorts isn't the program that's complaining, DetectX is. So I'd ask 
> the developer of DetectX.

Re: failure to get gcc9 running

[Peter Homann]

There's also lots of messages in there that suggest you don't have the
10.14 SDK, which may mean Xcode hasn't yet been updated on your system.

I got my system in quite a tangle recently when Catalina finally got
beyond beta, but the uninstall/reinstall approach worked best for
getting it right again.

Peter.

On 5/11/19 05:49, Ryan Schmidt wrote:
>
> On Nov 4, 2019, at 10:12, Hans Goedbloed wrote:
> ​
>> [/Users/hansgoedbloed]$sudo port install gcc9
>> Password:
>> ---> Computing dependencies for gcc9
>> ---> Cleaning gcc9
> First things first: this shows that gcc9 was already successfully installed 
> before you ran this command.
>
>
>> ---> Updating database of binaries
>> ---> Scanning binaries for linking errors
>> ---> Found 9 broken files, matching files to ports
>> ---> Found 4 broken ports, determining rebuild order
>> You can always run 'port rev-upgrade' again to fix errors.
>> The following ports will be rebuilt:
>>  cmake @3.15.5
>>  readline @8.0.000
>>  gdbm @1.18.1
>>  llvm-8.0 @8.0.1
>> Continue? [Y/n]: y
>
> After any port install or upgrade, MacPorts checks all installed ports for 
> linking errors. It found some on your system. We would need to see the output 
> of "sudo port -d rev-upgrade" to know specifically what problems were found 
> with those ports.
>
>
>> Warning: No port perl5.8 found in the index.
> perl5.8 was removed a long time ago. The current version is perl5.30. Nothing 
> in MacPorts should be referencing perl5.8 anymore. (I found one port that 
> was; I filed a ticket: https://trac.macports.org/ticket/59600)
>
> Do you perhaps have any local Portfiles (check your 
> /opt/local/etc/macports/sources.conf file) that might be very old and out of 
> date?
>
>
>> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
>> build correctly.
>> Warning: You can install it as part of the Xcode Command Line Tools package 
>> by running `xcode-select --install'.
> I see below that you did run this command. Good.
>
>
>> ---> Computing dependencies for cmake
>> ---> Fetching distfiles for cmake
>> ---> Attempting to fetch cmake-3.15.5.tar.gz from 
>> https://distfiles.macports.org/cmake
>> ---> Verifying checksums for cmake   
>>   
>> ---> Extracting cmake
>> ---> Applying patches to cmake
>> ---> Configuring cmake
>> ---> Building cmake
>> ---> Staging cmake into destroot
>> ---> Deactivating cmake @3.15.5_0
>> ---> Cleaning cmake
>> ---> Uninstalling cmake @3.15.5_0
>> ---> Cleaning cmake
>> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
>> build correctly.
>> Warning: You can install it as part of the Xcode Command Line Tools package 
>> by running `xcode-select --install'.
>> ---> Computing dependencies for cmake
>> ---> Installing cmake @3.15.5_0
>> ---> Activating cmake @3.15.5_0
>> ---> Cleaning cmake
>> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
>> build correctly.
>> Warning: You can install it as part of the Xcode Command Line Tools package 
>> by running `xcode-select --install'.
>> ---> Computing dependencies for readline
>> ---> Fetching distfiles for readline
>> ---> Attempting to fetch readline-8.0.tar.gz from 
>> https://distfiles.macports.org/readline
>> ---> Verifying checksums for readline
>> ---> Extracting readline
>> ---> Applying patches to readline
>> ---> Configuring readline
>> ---> Building readline
>> ---> Staging readline into destroot
>> ---> Unable to uninstall readline @8.0.000_0, the following ports depend on 
>> it:
>> --->   gdbm @1.18.1_1
>> Warning: Uninstall forced.  Proceeding despite dependencies.
>> ---> Deactivating readline @8.0.000_0
>> ---> Cleaning readline
>> ---> Uninstalling readline @8.0.000_0
>> ---> Cleaning readline
>> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
>> build correctly.
>> Warning: You can install it as part of the Xcode Command Line Tools package 
>> by running `xcode-select --install'.
>> ---> Computing dependencies for readline
>> ---> Installing readline @8.0.000_0
>> ---> Activating readline @8.0.000_0
>> ---> Cleaning readline
> Whatever the problem with cmake and readline was, MacPorts successfully 
> rebuilt them so they are no longer broken.
>
>
>> ---> Computing dependencies for gdbm
>> ---> Fetching distfiles for gdbm
>> ---> Attempting to fetch gdbm-1.18.1.tar.gz from 
>> https://distfiles.macports.org/gdbm
>> ---> Verifying checksums for gdbm
>> ---> Extracting gdbm
>> ---> Applying patches to gdbm
>> ---> Configuring gdbm
>> Error: Failed to configure gdbm, consult 
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/work/gdbm-1.18.1/config.log
>> Error: Failed to configure gdbm: configure failure: command execution failed
>> Error: See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_gdbm/gdbm/main.log

qt5-qt3d complains about system assimp missing

[Michael A. Leonetti]

I just upgraded to Catalina (so many regrets).

My qt5 installation keeps complaining about missing linking files so I 
am trying to reinstall and qt5-q3d complains about missing system-assimp.


Is there a variant I'm missing that I can disable?

:debug:configure 
SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk'
:info:configure Executing:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5" 
&& /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang 
-- -system-assimp
:debug:configure system:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5" 
&& /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang 
-- -system-assimp

:info:configure Running configuration tests...
:info:configure Done running configuration tests.
:info:configure Configure summary:
:info:configure Qt 3D:
:info:configure   Assimp . yes
:info:configure   System Assimp .. no
:info:configure   Output Qt3D Job traces . no
:info:configure   Output Qt3D GL traces .. no
:info:configure   Use SSE2 instructions .. yes
:info:configure   Use AVX2 instructions .. no
:info:configure   Aspects:
:info:configure Render aspect  yes
:info:configure Input aspect . yes
:info:configure Logic aspect . yes
:info:configure Animation aspect . yes
:info:configure Extras aspect  yes
:info:configure Qt 3D Renderers:
:info:configure   OpenGL Renderer  yes
:info:configure Qt 3D GeometryLoaders:
:info:configure   Autodesk FBX ... no
:info:configure ERROR: Feature 'system-assimp' was enabled, but the 
pre-condition 'features.assimp && libs.assimp' failed.

:info:configure Check config.log for details.
:info:configure Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5" 
&& /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang 
-- -system-assimp

:info:configure Exit code: 3


--
Michael A. Leonetti
As warm as green tea

Re: qt5-qt3d complains about system assimp missing

[Michael A. Leonetti]

Did exactly this for ticket #59601.

Michael A. Leonetti
As warm as green tea

On 11/4/19 3:59 PM, Ryan Schmidt wrote:

On Nov 4, 2019, at 14:25, Michael A. Leonetti wrote:


My qt5 installation keeps complaining about missing linking files so I am 
trying to reinstall and qt5-q3d complains about missing system-assimp.

Is there a variant I'm missing that I can disable?


:debug:configure 
SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk'
:info:configure Executing:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5"
 && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- -system-assimp
:debug:configure system:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5"
 && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- -system-assimp
:info:configure Running configuration tests...
:info:configure Done running configuration tests.
:info:configure Configure summary:
:info:configure Qt 3D:
:info:configure   Assimp . yes
:info:configure   System Assimp .. no
:info:configure   Output Qt3D Job traces . no
:info:configure   Output Qt3D GL traces .. no
:info:configure   Use SSE2 instructions .. yes
:info:configure   Use AVX2 instructions .. no
:info:configure   Aspects:
:info:configure Render aspect  yes
:info:configure Input aspect . yes
:info:configure Logic aspect . yes
:info:configure Animation aspect . yes
:info:configure Extras aspect  yes
:info:configure Qt 3D Renderers:
:info:configure   OpenGL Renderer  yes
:info:configure Qt 3D GeometryLoaders:
:info:configure   Autodesk FBX ... no
:info:configure ERROR: Feature 'system-assimp' was enabled, but the pre-condition 
'features.assimp && libs.assimp' failed.
:info:configure Check config.log for details.
:info:configure Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qt3d/work/qt3d-everywhere-src-5.12.5"
 && /opt/local/libexec/qt5/bin/qmake PREFIX=/opt/local -spec macx-clang -- -system-assimp
:info:configure Exit code: 3

Looks like qt5-qt3d just requires assimp. Sounds like you should file a bug 
report and attach the full logs. qt5-qt3d does declare a dependency on assimp, 
so we would need to see the logs to know why qt3-qt3d thinks it's not there.

Re: postgresql83-server - Further Woes

[Bill Cole]

On 4 Nov 2019, at 17:22, Michael Newman via macports-users wrote:

The only solution offered by the developer of DetectX was to tell 
DetectX to ignore changes to macports plist files.


That seems to defeat the purpose of DetectX.

DetectX is supposed to warn you of possible nefarious changes to your 
system. Choosing to ignore a possible problem is no solution.


There is no rational explanation for the DetectX claim that the 
postgresql83-server launchd plist is changing repeatedly. That file is 
gone: you removed the port. Unless you are repeatedly installing and 
uninstalling the postgresql83-server port, that file IS NOT flashing in 
and out of existence.


I don't use DetectX so I can't say for sure, but it seems to me that 
this behavior is consistent with it having a saved state of some sort 
against which it is comparing the current state. In other words: DetectX 
remembers that the postgresql83-server plist was there before, and sees 
that it isn't there now.


If that is a correct guess about how DetectX works, then there should be 
some way to update the saved state to accommodate the disappearance of a 
file without permanently ignoring a whole class of similarly situated 
files.




--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)