Re: Failed to install libgcc9: no destroot found

[Vahid Askarpour]

I tried the advices from Ryan and Chris, cleaning the ports and reinstalling 
Macport without reinstalling the OS. This time, the installation of xcrysden 
was complete, no errors and xcrysden is working fine. In my earlier attempts, I 
did not clean the ports and this might be the key factor. 

Many thanks for all your comments.

Vahid

> On Sep 28, 2019, at 12:10 AM, Ryan Schmidt  wrote:
> 
> 
> 
> 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: Failed to install libgcc9: no destroot found

[Ryan Schmidt]

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: Failed to install libgcc9: no destroot found

[Ryan Schmidt]

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

[Chris Jones]

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: Failed to install libgcc9: no destroot found

[Chris Jones]

> 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

[Vahid Askarpour]

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

[Vahid Askarpour]

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

[Chris Jones]

> 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

[Vahid Askarpour]

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

[Chris Jones]

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

[Vahid Askarpour]

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

[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

[Vahid Askarpour]

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

[Vahid Askarpour]

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

[Piet van Oostrum]

Chris Jones  writes:

> 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.

But could it have been installed by some other libgcc* port? Like libgcc8?
What does 'port provides /opt/local/lib/libgcc/libatomic.1.dylib' say?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]

Re: Failed to install libgcc9: no destroot found

[Chris Jones]

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

Re: Failed to install libgcc9: no destroot found

[Vahid Askarpour]

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 
mailto:jon...@hep.phy.cam.ac.uk>> wrote:

sudo port upgrade outdated



main.log
Description: main.log

Re: Failed to install libgcc9: no destroot found

[Chris Jones]

From your log file

nfo:activate x ./opt/local/include/gcc/c++/decimal/decimal.h
: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.

That is your problem. 

Do not though do what it says. The only way you can have this problem is if 
your libgcc port is very very out of date... try (force) removing it

sudo port uninstall libgcc

Say yes to the do you really want to do this question. Then

sudo port selfupdate
sudo port sync
sudo port upgrade outdated

Chris

> On 27 Sep 2019, at 1:42 am, Vahid Askarpour  wrote:
> 
> I am attempting to install xcrysden on Mojave 10.14.6 with Xcode 11.1. I get 
> the following error:
> 
> --->  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 main.log file. Any suggestions would be appreciated.
> 
> Thank you,
> Vahid
> 
>