On Sep 27, 2019, at 06:15, Chris Jones wrote:
> Odd. On my 10.13 machine it returns the versioned SDK. e.g.
On my 10.13 machine it also returns the versioned SDK. But on the buildbot
machines, it returns the unversioned SDK, so apparently it's not that odd and
doesn't indicate a problem.
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 py3
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 wo
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
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
> 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. Bef
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:
>>>
>>> W
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 ma
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
> 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
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 cor
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,
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.
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]
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
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
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:
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
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
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
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
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/Develope
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
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 routi
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 t
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::
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 download
27 matches
Mail list logo
