date:20190927

I get

Port libgcc is not installed.

Vahid

On Sep 27, 2019, at 7:57 AM, Chris Jones 
mailto:jon...@hep.phy.cam.ac.uk>> wrote:

port contents libgcc

Re: Failed to install libgcc9: no destroot found

I have /opt/local/lib folder but there is no libgcc subfolder there.

Vahid

> On Sep 27, 2019, at 12:32 PM, Piet van Oostrum  wrote:
> 
> Vahid Askarpour  writes:
> 
>> port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
>> 
>> /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
>> 
> Is there anything in /opt/local/lib/libgcc ?
> -- 
> Piet van Oostrum 
> WWW: http://piet.vanoostrum.org/
> PGP key: [8DAE142BE17999C4]

Re: Failed to install libgcc9: no destroot found

port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:

/opt/local/lib/libgcc/libatomic.1.dylib does not exist.

Vahid

On Sep 27, 2019, at 10:02 AM, Piet van Oostrum 
mailto:pie...@vanoostrum.org>> wrote:

port provides /opt/local/lib/libgcc/libatomic.1.dylib

Re: Failed to install libgcc9: no destroot found

2019-09-27 Thread Piet van Oostrum

Vahid Askarpour  writes:

> port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
>
> /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
>
Is there anything in /opt/local/lib/libgcc ?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]

Re: Failed to install libgcc9: no destroot found

Hi,

Sounds like your ports database is corrupted in some way, it is is complaining 
about a file and port that is not actually installed

> On 27 Sep 2019, at 4:37 pm, Vahid Askarpour  wrote:
> 
> I have /opt/local/lib folder but there is no libgcc subfolder there.
> 
> Vahid
> 
>> On Sep 27, 2019, at 12:32 PM, Piet van Oostrum  wrote:
>> 
>> Vahid Askarpour  writes:
>> 
>>> port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
>>> 
>>> /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
>>> 
>> Is there anything in /opt/local/lib/libgcc ?
>> -- 
>> Piet van Oostrum 
>> WWW: http://piet.vanoostrum.org/
>> PGP key: [8DAE142BE17999C4]
>

Re: Failed to install libgcc9: no destroot found

When I upgraded to Majove and installed Xcode 11.1, I ended up with gcc-4.2.1 
and libgcc in /usr/bin and /usr/lib. Before, when I had High Sierra, I was 
running xcrysden with no issues.

Vahid

> On Sep 27, 2019, at 3:58 PM, Chris Jones  wrote:
> 
> Hi,
> 
> Sounds like your ports database is corrupted in some way, it is is 
> complaining about a file and port that is not actually installed
> 
>> On 27 Sep 2019, at 4:37 pm, Vahid Askarpour  wrote:
>> 
>> I have /opt/local/lib folder but there is no libgcc subfolder there.
>> 
>> Vahid
>> 
>>> On Sep 27, 2019, at 12:32 PM, Piet van Oostrum  
>>> wrote:
>>> 
>>> Vahid Askarpour  writes:
>>> 
 port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
 
 /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
 
>>> Is there anything in /opt/local/lib/libgcc ?
>>> -- 
>>> Piet van Oostrum 
>>> WWW: http://piet.vanoostrum.org/
>>> PGP key: [8DAE142BE17999C4]
>> 
>

Re: Failed to install libgcc9: no destroot found




> On 27 Sep 2019, at 9:28 pm, Vahid Askarpour  wrote:
> 
> When I upgraded to Majove and installed Xcode 11.1, I ended up with 
> gcc-4.2.1 and libgcc in /usr/bin and /usr/lib. Before, when I had High 
> Sierra, I was running xcrysden with no issues.

That makes no sense at all. MacOS does not ship gcc, and MacPorts would never 
anything under /usr/

Something is distinctly messed up with your system I suspect...

> 
> Vahid
> 
>> On Sep 27, 2019, at 3:58 PM, Chris Jones  wrote:
>> 
>> Hi,
>> 
>> Sounds like your ports database is corrupted in some way, it is is 
>> complaining about a file and port that is not actually installed
>> 
 On 27 Sep 2019, at 4:37 pm, Vahid Askarpour  wrote:
>>> 
>>> I have /opt/local/lib folder but there is no libgcc subfolder there.
>>> 
>>> Vahid
>>> 
 On Sep 27, 2019, at 12:32 PM, Piet van Oostrum  
 wrote:
 
 Vahid Askarpour  writes:
 
> port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
> 
> /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
> 
 Is there anything in /opt/local/lib/libgcc ?
 -- 
 Piet van Oostrum 
 WWW: http://piet.vanoostrum.org/
 PGP key: [8DAE142BE17999C4]
>>> 
>> 
>

Re: Failed to install libgcc9: no destroot found

Xcode 11 apparently has installed gcc on my Mac. When I check the gcc version, 
I get:

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Vahid

> On Sep 27, 2019, at 5:51 PM, Chris Jones  wrote:
> 
> 
> 
>> On 27 Sep 2019, at 9:28 pm, Vahid Askarpour  wrote:
>> 
>> When I upgraded to Majove and installed Xcode 11.1, I ended up with 
>> gcc-4.2.1 and libgcc in /usr/bin and /usr/lib. Before, when I had High 
>> Sierra, I was running xcrysden with no issues.
> 
> That makes no sense at all. MacOS does not ship gcc, and MacPorts would never 
> anything under /usr/
> 
> Something is distinctly messed up with your system I suspect...
> 
>> 
>> Vahid
>> 
>>> On Sep 27, 2019, at 3:58 PM, Chris Jones  wrote:
>>> 
>>> Hi,
>>> 
>>> Sounds like your ports database is corrupted in some way, it is is 
>>> complaining about a file and port that is not actually installed
>>> 
> On 27 Sep 2019, at 4:37 pm, Vahid Askarpour  wrote:
 
 I have /opt/local/lib folder but there is no libgcc subfolder there.
 
 Vahid
 
> On Sep 27, 2019, at 12:32 PM, Piet van Oostrum  
> wrote:
> 
> Vahid Askarpour  writes:
> 
>> port provides /opt/local/lib/libgcc/libatomic.1.dylib results in:
>> 
>> /opt/local/lib/libgcc/libatomic.1.dylib does not exist.
>> 
> Is there anything in /opt/local/lib/libgcc ?
> -- 
> Piet van Oostrum 
> WWW: http://piet.vanoostrum.org/
> PGP key: [8DAE142BE17999C4]
 
>>> 
>> 
>

Re: Failed to install libgcc9: no destroot found

Perhaps my best course of action is to reinstall the OS, Xcode and then 
MacPorts.

Thank you all for your suggestions.
Vahid

> On Sep 27, 2019, at 6:28 PM, Bill Cole 
>  wrote:
> 
> On 27 Sep 2019, at 16:51, Chris Jones wrote:
> 
>>> On 27 Sep 2019, at 9:28 pm, Vahid Askarpour  wrote:
>>> 
>>> When I upgraded to Majove and installed Xcode 11.1, I ended up with 
>>> gcc-4.2.1 and libgcc in /usr/bin and /usr/lib. Before, when I had High 
>>> Sierra, I was running xcrysden with no issues.
>> 
>> That makes no sense at all. MacOS does not ship gcc,
> 
> What exactly does that sentence mean?
> 
> On my Mojave machine:
> 
> $ /usr/bin/gcc -v
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
> Apple clang version 11.0.0 (clang-1100.0.33.8)
> Target: x86_64-apple-darwin18.7.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 
> It's not technically The Real GCC, but it is an executable binary at 
> /usr/bin/gcc why acts a lot like GCC 4.2.1.
> 
> Also:
> 
> $ ls -l /usr/lib/libgcc*
> lrwxr-xr-x  1 root  wheel  15 Sep 25 08:41 /usr/lib/libgcc_s.1.dylib -> 
> libSystem.dylib
> 
> Which is profoundly "Not Really LibGCC" but it is apparently close enough.
> 
> On High Sierra:
> 
> $ /usr/bin/gcc -v
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 10.0.0 (clang-1000.11.45.5)
> Target: x86_64-apple-darwin17.7.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 
> $ ls -l /usr/lib/libgcc*
> lrwxr-xr-x  1 root  wheel 17 Sep 19  2018 /usr/lib/libgcc_s.1.dylib -> 
> libSystem.B.dylib
> lrwxr-xr-x  1 root  wheel 19 Oct 15  2018 /usr/lib/libgcc_s.10.4.dylib -> 
> libgcc_s.10.5.dylib
> -rwxr-xr-x  1 root  wheel  30948 Oct  6  2017 /usr/lib/libgcc_s.10.5.dylib
> 
> THAT is interesting...
> 
> $ otool -L  /usr/lib/libgcc_s.10.5.dylib
> /usr/lib/libgcc_s.10.5.dylib:
>   /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 
> 795.0.0)
> 
> Oh, OK, not really very interesting, just baroque...
> 
> (El Cap is very similar)
> 
> -- 
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Re: Failed to install libgcc9: no destroot found

You are still getting

:error:activate Failed to activate libgcc9: Image error:
/opt/local/lib/libgcc/libatomic.1.dylib is being used by the active
libgcc port. Please deactivate this port first, or use 'port -f
activate libgcc9' to force the activation.

:debug:activate Error code: registry::image-error
:debug:activate Backtrace: Image error:
/opt/local/lib/libgcc/libatomic.1.dylib is being used by the active
libgcc port. Please deactivate this port first, or use 'port -f
activate libgcc9' to force the activation.

This is not correct. libgcc has not installed anything (other than a
stub readme file) for some time now.

Titan ~/Projects/MacPorts/ports > port contents libgcc
Port libgcc contains:
/opt/local/share/doc/libgcc/README
Titan ~/Projects/MacPorts/ports > cat /opt/local/share/doc/libgcc/README
libgcc runtime is provided by libgcc9
Titan ~/Projects/MacPorts/ports >

If your ports are really up to date, I cannot explain why you see.

what do you get with

port contents libgcc ?

Chris

On 27/09/2019 11:42 am, Vahid Askarpour wrote:
I followed the steps you outlined with no problem. Here is the terminal
output:

VahidAskarpour:~> sudo port uninstall libgcc
Password:
VahidAskarpour:~> sudo port selfupdate
---> Updating MacPorts base sources using rsync
MacPorts base version 2.6.0 installed,
MacPorts base version 2.6.0 downloaded.
---> Updating the ports tree
---> MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you
should run

port upgrade outdated
VahidAskarpour:~> sudo port sync
---> Updating the ports tree
VahidAskarpour:~> sudo port upgrade outdated
Nothing to upgrade.
---> Scanning binaries for linking errors
---> No broken files found.
---> No broken ports found.

However, when I tried to install xcrysden, I got the same error. Here is
the terminal output:

VahidAskarpour:~> sudo port install xcrysden
---> Computing dependencies for xcrysden
The following dependencies will be installed:
libgcc
libgcc9
Continue? [Y/n]: y
---> Installing libgcc9 @9.2.0_0
Error: Failed to install libgcc9: no destroot found
at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot
Error:
See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/main.log
for details.

Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xcrysden failed

I have attached the log file which is similar to the one I posted yesterday.

Thanks,
Vahid

On Sep 26, 2019, at 9:49 PM, Chris Jones > wrote:

sudo port upgrade outdated

py36-pyqt5 Failed to determine details of Qt installation.

I filed a ticket on this issue already and included a logfile for it, but I
thought there's no harm in asking the mailing list for a quick solution...

I upgraded to macports 2.6.0 today. During a routine upgrade of my
ports, the py36-pyqt5 port failed to configure, possibly due to a
problem with the recent XCode 11 upgrade...?

>From logfile:

Error: Failed to determine the detail of your Qt installation. Try again
using
the --verbose flag to see more detail about the problem.
Querying qmake about your Qt installation...
Determining the details of your Qt installation...
/opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk cfgtest_QtCore.pro
Project ERROR: Could not resolve SDK Path for 'macosx10.14' using
--show-sdk-path


This is the first time something like this has happened. No problems before
the XCode 11 upgrade.

I upgraded to XCode 11 a few days ago, and as someone else pointed out,
XCode removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk.
What I did to try and resolve it was create a MacOSX10.14.sdk symlink.
Is py36-pyqt5 one of those ports that has a hard-coded path to the 10.14
SDK, and somehow isn't fooled by the symlink I created or something?

Re: py36-pyqt5 Failed to determine details of Qt installation.


what does

xcrun --show-sdk-path

give you ?

On 27/09/2019 12:04 pm, Carlo Tambuatco wrote:
I filed a ticket on this issue already and included a logfile for it, 
but I thought there's no harm in asking the mailing list for a quick 
solution...


I upgraded to macports 2.6.0 today. During a routine upgrade of my
ports, the py36-pyqt5 port failed to configure, possibly due to a
problem with the recent XCode 11 upgrade...?

 From logfile:

Error: Failed to determine the detail of your Qt installation. Try again 
using

the --verbose flag to see more detail about the problem.
Querying qmake about your Qt installation...
Determining the details of your Qt installation...
/opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk cfgtest_QtCore.pro
Project ERROR: Could not resolve SDK Path for 'macosx10.14' using 
--show-sdk-path



This is the first time something like this has happened. No problems 
before the XCode 11 upgrade.


I upgraded to XCode 11 a few days ago, and as someone else pointed out, 
XCode removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk.

What I did to try and resolve it was create a MacOSX10.14.sdk symlink.
Is py36-pyqt5 one of those ports that has a hard-coded path to the 10.14 
SDK, and somehow isn't fooled by the symlink I created or something?

Re: py36-pyqt5 Failed to determine details of Qt installation.

On Fri, Sep 27, 2019 at 7:07 AM Chris Jones 
wrote:

> what does
>
> xcrun --show-sdk-path
>
> give you ?
>
>
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk


> On 27/09/2019 12:04 pm, Carlo Tambuatco wrote:
> > I filed a ticket on this issue already and included a logfile for it,
> > but I thought there's no harm in asking the mailing list for a quick
> > solution...
> >
> > I upgraded to macports 2.6.0 today. During a routine upgrade of my
> > ports, the py36-pyqt5 port failed to configure, possibly due to a
> > problem with the recent XCode 11 upgrade...?
> >
> >  From logfile:
> >
> > Error: Failed to determine the detail of your Qt installation. Try again
> > using
> > the --verbose flag to see more detail about the problem.
> > Querying qmake about your Qt installation...
> > Determining the details of your Qt installation...
> > /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk cfgtest_QtCore.pro
> > Project ERROR: Could not resolve SDK Path for 'macosx10.14' using
> > --show-sdk-path
> >
> >
> > This is the first time something like this has happened. No problems
> > before the XCode 11 upgrade.
> >
> > I upgraded to XCode 11 a few days ago, and as someone else pointed out,
> > XCode removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk.
> > What I did to try and resolve it was create a MacOSX10.14.sdk symlink.
> > Is py36-pyqt5 one of those ports that has a hard-coded path to the 10.14
> > SDK, and somehow isn't fooled by the symlink I created or something?
> >
> >
>

Re: py36-pyqt5 Failed to determine details of Qt installation.




Odd. On my 10.13 machine it returns the versioned SDK. e.g.

Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
Titan ~/Projects/MacPorts/ports > ls 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs

MacOSX.sdk  MacOSX10.14.sdk
Titan ~/Projects/MacPorts/ports > ls -lth 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs

total 0
drwxr-xr-x  7 root  wheel   224B 30 Oct  2018 MacOSX.sdk
lrwxr-xr-x  1 root  wheel10B 17 Sep  2018 MacOSX10.14.sdk -> MacOSX.sdk

( so yes, Xcode 10 here also only has 'macOS release + 1' SDK )

what does

ls -lth 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs 



give for you ?

Chris

On 27/09/2019 12:11 pm, Carlo Tambuatco wrote:
On Fri, Sep 27, 2019 at 7:07 AM Chris Jones > wrote:


what does

xcrun --show-sdk-path

give you ?


/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk

On 27/09/2019 12:04 pm, Carlo Tambuatco wrote:
 > I filed a ticket on this issue already and included a logfile for
it,
 > but I thought there's no harm in asking the mailing list for a quick
 > solution...
 >
 > I upgraded to macports 2.6.0 today. During a routine upgrade of my
 > ports, the py36-pyqt5 port failed to configure, possibly due to a
 > problem with the recent XCode 11 upgrade...?
 >
 >  From logfile:
 >
 > Error: Failed to determine the detail of your Qt installation.
Try again
 > using
 > the --verbose flag to see more detail about the problem.
 > Querying qmake about your Qt installation...
 > Determining the details of your Qt installation...
 > /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk
cfgtest_QtCore.pro
 > Project ERROR: Could not resolve SDK Path for 'macosx10.14' using
 > --show-sdk-path
 >
 >
 > This is the first time something like this has happened. No problems
 > before the XCode 11 upgrade.
 >
 > I upgraded to XCode 11 a few days ago, and as someone else
pointed out,
 > XCode removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk.
 > What I did to try and resolve it was create a MacOSX10.14.sdk
symlink.
 > Is py36-pyqt5 one of those ports that has a hard-coded path to
the 10.14
 > SDK, and somehow isn't fooled by the symlink I created or something?
 >
 >

Re: py36-pyqt5 Failed to determine details of Qt installation.

On Fri, Sep 27, 2019 at 7:15 AM Chris Jones 
wrote:

>
> Odd. On my 10.13 machine it returns the versioned SDK. e.g.
>
> Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
> Titan ~/Projects/MacPorts/ports > ls
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
> MacOSX.sdk  MacOSX10.14.sdk
> Titan ~/Projects/MacPorts/ports > ls -lth
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
> total 0
> drwxr-xr-x  7 root  wheel   224B 30 Oct  2018 MacOSX.sdk
> lrwxr-xr-x  1 root  wheel10B 17 Sep  2018 MacOSX10.14.sdk -> MacOSX.sdk
>
> ( so yes, Xcode 10 here also only has 'macOS release + 1' SDK )
>
> what does
>
> ls -lth
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
>
>
>
> give for you ?
>
> Chris
>
>
total 0
lrwxr-xr-x  1 root wheel  10 Sep 24 13:59 MacOSX10.14.sdk -> MacOSX.sdk/
drwxr-xr-x 10 root wheel 320 Sep 24 13:58 MacOSX.sdk/
lrwxr-xr-x  1 root wheel  10 Sep 21 10:12 MacOSX10.15.sdk -> MacOSX.sdk/
drwxr-xr-x  4 root wheel 128 Aug 30 02:47 DriverKit19.0.sdk/

The MacOSX10.15.sdk symlink was created by the XCode 11 upgrade.
The MacOSX10.14.sdk symlink was created by me to resolve some macports
issues.

I'm at my wits end with this. Is there some problem with the py36-pyqt5
port finding the
correct sdk?


On 27/09/2019 12:11 pm, Carlo Tambuatco wrote:
> > On Fri, Sep 27, 2019 at 7:07 AM Chris Jones  > > wrote:
> >
> > what does
> >
> > xcrun --show-sdk-path
> >
> > give you ?
> >
> >
> >
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
> >
> > On 27/09/2019 12:04 pm, Carlo Tambuatco wrote:
> >  > I filed a ticket on this issue already and included a logfile for
> > it,
> >  > but I thought there's no harm in asking the mailing list for a
> quick
> >  > solution...
> >  >
> >  > I upgraded to macports 2.6.0 today. During a routine upgrade of my
> >  > ports, the py36-pyqt5 port failed to configure, possibly due to a
> >  > problem with the recent XCode 11 upgrade...?
> >  >
> >  >  From logfile:
> >  >
> >  > Error: Failed to determine the detail of your Qt installation.
> > Try again
> >  > using
> >  > the --verbose flag to see more detail about the problem.
> >  > Querying qmake about your Qt installation...
> >  > Determining the details of your Qt installation...
> >  > /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk
> > cfgtest_QtCore.pro
> >  > Project ERROR: Could not resolve SDK Path for 'macosx10.14' using
> >  > --show-sdk-path
> >  >
> >  >
> >  > This is the first time something like this has happened. No
> problems
> >  > before the XCode 11 upgrade.
> >  >
> >  > I upgraded to XCode 11 a few days ago, and as someone else
> > pointed out,
> >  > XCode removed the MacOS10.14.sdk and replaced it with
> MacOS10.15.sdk.
> >  > What I did to try and resolve it was create a MacOSX10.14.sdk
> > symlink.
> >  > Is py36-pyqt5 one of those ports that has a hard-coded path to
> > the 10.14
> >  > SDK, and somehow isn't fooled by the symlink I created or
> something?
> >  >
> >  >
> >
>

Re: py36-pyqt5 Failed to determine details of Qt installation.




I'm at my wits end with this. Is there some problem with the py36-pyqt5 
port finding the

correct sdk?


I have no idea, but if I where you I would simplify things by first 
working out why xcrun --show-sdk-path is not giving you the versioned 
SDK path. My bet is whatever the port is doing its related to that


Chris

Re: py36-pyqt5 Failed to determine details of Qt installation.

Yeah possibly...but I just ran

xcrun --show-sdk-version

and got something weird:

2019-09-27 07:31:54.372 xcodebuild[33648:5774543] [MT] DVTSDK: Warning: SDK
path collision for path
'':
SDK with name 'macosx10.15' being superseded by SDK with 'macosx10.15'.
10.15

Is this a problem?


On Fri, Sep 27, 2019 at 7:26 AM Chris Jones 
wrote:

>
> > I'm at my wits end with this. Is there some problem with the py36-pyqt5
> > port finding the
> > correct sdk?
>
> I have no idea, but if I where you I would simplify things by first
> working out why xcrun --show-sdk-path is not giving you the versioned
> SDK path. My bet is whatever the port is doing its related to that
>
> Chris
>

Re: Failed to install libgcc9: no destroot found

I followed the steps you outlined with no problem. Here is the terminal output:

The ports tree has been updated. To upgrade your installed ports, you should run
port upgrade outdated
VahidAskarpour:~> sudo port sync
---> Updating the ports tree
VahidAskarpour:~> sudo port upgrade outdated
Nothing to upgrade.
---> Scanning binaries for linking errors
---> No broken files found.
---> No broken ports found.

However, when I tried to install xcrysden, I got the same error. Here is the
terminal output:

VahidAskarpour:~> sudo port install xcrysden
---> Computing dependencies for xcrysden
The following dependencies will be installed:
libgcc
libgcc9
Continue? [Y/n]: y
---> Installing libgcc9 @9.2.0_0
Error: Failed to install libgcc9: no destroot found at:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xcrysden failed

I have attached the log file which is similar to the one I posted yesterday.

Thanks,
Vahid

On Sep 26, 2019, at 9:49 PM, Chris Jones
mailto:jon...@hep.phy.cam.ac.uk>> wrote:

sudo port upgrade outdated

main.log
Description: main.log

Re: py36-pyqt5 Failed to determine details of Qt installation.

doesn't look ideal

On 27/09/2019 12:35 pm, Carlo Tambuatco wrote:

Yeah possibly...but I just ran

xcrun --show-sdk-version

and got something weird:

2019-09-27 07:31:54.372 xcodebuild[33648:5774543] [MT] DVTSDK: Warning: 
SDK path collision for path 
'': 
SDK with name 'macosx10.15' being superseded by SDK with 'macosx10.15'.

10.15

Is this a problem?

On Fri, Sep 27, 2019 at 7:26 AM Chris Jones > wrote:

 > I'm at my wits end with this. Is there some problem with the
py36-pyqt5
 > port finding the
 > correct sdk?

I have no idea, but if I where you I would simplify things by first
working out why xcrun --show-sdk-path is not giving you the versioned
SDK path. My bet is whatever the port is doing its related to that

Chris

Re: Failed to install libgcc9: no destroot found




> On 27 Sep 2019, at 10:29 pm, Bill Cole 
>  wrote:
> 
> On 27 Sep 2019, at 16:51, Chris Jones wrote:
> 
 On 27 Sep 2019, at 9:28 pm, Vahid Askarpour  wrote:
>>> 
>>> When I upgraded to Majove and installed Xcode 11.1, I ended up with 
>>> gcc-4.2.1 and libgcc in /usr/bin and /usr/lib. Before, when I had High 
>>> Sierra, I was running xcrysden with no issues.
>> 
>> That makes no sense at all. MacOS does not ship gcc,
> 
> What exactly does that sentence mean?

MacOS pretends to ship gcc, but as you mail below shows these are just sym 
links to clang. 
Apple hasn’t shipped and OS really with gcc for some time.

Chris
> 
> On my Mojave machine:
> 
> $ /usr/bin/gcc -v
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
> Apple clang version 11.0.0 (clang-1100.0.33.8)
> Target: x86_64-apple-darwin18.7.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 
> It's not technically The Real GCC, but it is an executable binary at 
> /usr/bin/gcc why acts a lot like GCC 4.2.1.
> 
> Also:
> 
> $ ls -l /usr/lib/libgcc*
> lrwxr-xr-x  1 root  wheel  15 Sep 25 08:41 /usr/lib/libgcc_s.1.dylib -> 
> libSystem.dylib
> 
> Which is profoundly "Not Really LibGCC" but it is apparently close enough.
> 
> On High Sierra:
> 
> $ /usr/bin/gcc -v
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 10.0.0 (clang-1000.11.45.5)
> Target: x86_64-apple-darwin17.7.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 
> $ ls -l /usr/lib/libgcc*
> lrwxr-xr-x  1 root  wheel 17 Sep 19  2018 /usr/lib/libgcc_s.1.dylib -> 
> libSystem.B.dylib
> lrwxr-xr-x  1 root  wheel 19 Oct 15  2018 /usr/lib/libgcc_s.10.4.dylib -> 
> libgcc_s.10.5.dylib
> -rwxr-xr-x  1 root  wheel  30948 Oct  6  2017 /usr/lib/libgcc_s.10.5.dylib
> 
> THAT is interesting...
> 
> $ otool -L  /usr/lib/libgcc_s.10.5.dylib
> /usr/lib/libgcc_s.10.5.dylib:
>/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 
> 795.0.0)
> 
> Oh, OK, not really very interesting, just baroque...
> 
> (El Cap is very similar)
> 
> -- 
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire

Re: Failed to install libgcc9: no destroot found


Reinstalling the os is probably not necessary. I would start with just wiping 
macports and reinstalling that from scratch.

https://guide.macports.org/chunked/installing.macports.uninstalling.html

> On 28 Sep 2019, at 1:03 am, Vahid Askarpour  wrote:
> 
> Perhaps my best course of action is to reinstall the OS, Xcode and then 
> MacPorts.
> 
> Thank you all for your suggestions.
> Vahid
> 
>> On Sep 27, 2019, at 6:28 PM, Bill Cole 
>>  wrote:
>> 
>> On 27 Sep 2019, at 16:51, Chris Jones wrote:
>> 
> On 27 Sep 2019, at 9:28 pm, Vahid Askarpour  wrote:
> 
> When I upgraded to Majove and installed Xcode 11.1, I ended up with 
> gcc-4.2.1 and libgcc in /usr/bin and /usr/lib. Before, when I had High 
> Sierra, I was running xcrysden with no issues.
>>> 
>>> That makes no sense at all. MacOS does not ship gcc,
>> 
>> What exactly does that sentence mean?
>> 
>> On my Mojave machine:
>> 
>> $ /usr/bin/gcc -v
>> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
>> --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
>> Apple clang version 11.0.0 (clang-1100.0.33.8)
>> Target: x86_64-apple-darwin18.7.0
>> Thread model: posix
>> InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>> 
>> It's not technically The Real GCC, but it is an executable binary at 
>> /usr/bin/gcc why acts a lot like GCC 4.2.1.
>> 
>> Also:
>> 
>> $ ls -l /usr/lib/libgcc*
>> lrwxr-xr-x  1 root  wheel  15 Sep 25 08:41 /usr/lib/libgcc_s.1.dylib -> 
>> libSystem.dylib
>> 
>> Which is profoundly "Not Really LibGCC" but it is apparently close enough.
>> 
>> On High Sierra:
>> 
>> $ /usr/bin/gcc -v
>> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
>> --with-gxx-include-dir=/usr/include/c++/4.2.1
>> Apple LLVM version 10.0.0 (clang-1000.11.45.5)
>> Target: x86_64-apple-darwin17.7.0
>> Thread model: posix
>> InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>> 
>> $ ls -l /usr/lib/libgcc*
>> lrwxr-xr-x  1 root  wheel 17 Sep 19  2018 /usr/lib/libgcc_s.1.dylib -> 
>> libSystem.B.dylib
>> lrwxr-xr-x  1 root  wheel 19 Oct 15  2018 /usr/lib/libgcc_s.10.4.dylib 
>> -> libgcc_s.10.5.dylib
>> -rwxr-xr-x  1 root  wheel  30948 Oct  6  2017 /usr/lib/libgcc_s.10.5.dylib
>> 
>> THAT is interesting...
>> 
>> $ otool -L  /usr/lib/libgcc_s.10.5.dylib
>> /usr/lib/libgcc_s.10.5.dylib:
>>/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 
>> 795.0.0)
>> 
>> Oh, OK, not really very interesting, just baroque...
>> 
>> (El Cap is very similar)
>> 
>> -- 
>> Bill Cole
>> b...@scconsult.com or billc...@apache.org
>> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
>> Not Currently Available For Hire
>

Re: py36-pyqt5 Failed to determine details of Qt installation.

On Sep 27, 2019, at 06:04, Carlo Tambuatco wrote:

> I filed a ticket on this issue already and included a logfile for it, but I 
> thought there's no harm in asking the mailing list for a quick solution...
> 
> I upgraded to macports 2.6.0 today. During a routine upgrade of my 
> ports, the py36-pyqt5 port failed to configure, possibly due to a 
> problem with the recent XCode 11 upgrade...?
> 
> From logfile:
> 
> Error: Failed to determine the detail of your Qt installation. Try again using
> the --verbose flag to see more detail about the problem.
> Querying qmake about your Qt installation...
> Determining the details of your Qt installation...
> /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk cfgtest_QtCore.pro
> Project ERROR: Could not resolve SDK Path for 'macosx10.14' using 
> --show-sdk-path
> 
> 
> This is the first time something like this has happened. No problems before 
> the XCode 11 upgrade.
> 
> I upgraded to XCode 11 a few days ago, and as someone else pointed out, XCode 
> removed the MacOS10.14.sdk and replaced it with MacOS10.15.sdk. 
> What I did to try and resolve it was create a MacOSX10.14.sdk symlink. 
> Is py36-pyqt5 one of those ports that has a hard-coded path to the 10.14 SDK, 
> and somehow isn't fooled by the symlink I created or something?

We are discovering, due to the Xcode 11 upgrade, just how many places in 
MacPorts the path to the 10.14 SDK got baked into files where we didn't mean 
for it to be. There are many other mailing list threads and tickets being filed 
with us about this. Until this is all ironed out, your simplest course of 
action would be to uninstall Xcode 11 and reinstall Xcode 10.

I cannot advocate creating a MacOSX10.14.sdk symlink. The 10.14 and 10.15 SDK 
are not the same thing. Subverting the system into believing they are can only 
cause you problems down the road.

Re: Failed to install libgcc9: no destroot found




On Sep 27, 2019, at 05:42, Vahid Askarpour wrote:

> Error: Failed to install libgcc9: no destroot found at: 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot

Please see:

https://trac.macports.org/wiki/ProblemHotlist#nodestrootfound

Re: Failed to install libgcc9: no destroot found

On Sep 27, 2019, at 13:58, Chris Jones wrote:

> Sounds like your ports database is corrupted in some way, it is is 
> complaining about a file and port that is not actually installed

I don't think I've ever heard of corruption like that happening before. I'm not 
sure that's possible. I would not jump to recommending uninstalling or 
reinstalling anything at this point.

Perhaps you're getting confused by the fact that the main.log file that's been 
attached in this thread contains several attempts. It might be helpful to look 
just at the last attempt. You can find each attempt by searching through the 
logfile for "version:1". It might also be useful for the user to "sudo port 
clean" the affected port before trying again, to ensure that the prior 
incomplete attempts are not interfering.

Re: py36-pyqt5 Failed to determine details of Qt installation.