Thank you all for taking a look inside this, and keeping Snow Leopard alive. It
worked now thanks to instructions provided.
Pat
El 2016-08-29, a las 09:41, Ken Cunningham escribió:
> FYI - the gtk3 upgrade does ultimately proceed normally on 10.6, once the
> LibCxxOnOlderSystems toolchain is
FYI - the gtk3 upgrade does ultimately proceed normally on 10.6, once the
LibCxxOnOlderSystems toolchain is repaired, per the separate instructions I
posted.
The problem was not with gtk specifically, but the toolchain it appears.
Ken
$ sudo port upgrade gtk3
---> Computing dependencies
Thanks for the info. I realize it's a small audience, and I'm happy to help,
and in fact, don't mind plugging away at it when I have some time. No wonder
the OP had trouble though. The toolchain blew up with the last updates to
cctools and ld64, and the current instructions and state of things
On 28 August 2016 at 23:21, Ken Cunningham wrote:
> OK - I see what happened.
>
> All traces of llvm37 have been from the new ld64 portfile.
>
> and so when the porfile saw my requested +llvm37, it saw that as no llvm
> variant, and defaulted to llvm34. And now my toolchain is looking pretty
>
OK - I see what happened.
All traces of llvm37 have been from the new ld64 portfile.
and so when the porfile saw my requested +llvm37, it saw that as no llvm
variant, and defaulted to llvm34. And now my toolchain is looking pretty
inoperable.
there isn't an llm37 option in the ld64 portfile
No - that doesn't work either...pulls in old ld64 version
then when you try to fix it, you get
$ sudo port upgrade --enforce-variants ld64-latest +llmv37 -llvm34
Error: Your platform cannot be configured without LTO support in ld64. Please
enable one of the llvmXX variants, and try again.
Sorry for all the emails one after another, but I noted that updating cctools
and llvm this morning somehow called back ld64-latest @264.3.102_2+llvm34,
which is not the right one. You need ld64-latest @264.3.102_1+llvm37.
---> Dependencies to be installed: llvm-3.4
---> Activating llvm-3.4
I note that ld64-latest, ld64-136, and cctools were all updated just now.
I sense the omnipresence of jeremy in the background somewhere, Obiwan...
Perhaps in hopes of saving your processor time you might just try updating
those ports and try your gtk3 install again?
K
On 2016-08-28, at 7:40
I'll try later this afternoon to update my own gtk3 on the same system and let
you know what happens.
Looks like it might be just your ld64* port that is dysfunctional - I suppose
we could make up an example that tests the linker, like we did for clang, and
see if that segfaults. Sorry I don't
On Aug 27, 2016, at 12:41, [ftp83plus] wrote:
>
> So, after reinstalling Mac OS X as I did to get out of the startup crash as I
> did, even if ports stayed in place, I should re-perform the
> LibcxxOnOlderSystems steps?
In general, no, reinstalling the same version of
On 27.08.2016 07:41 PM, [ftp83plus] wrote:
> So, after reinstalling Mac OS X as I did to get out of the startup crash as I
> did, even if ports stayed in place, I should re-perform the
> LibcxxOnOlderSystems steps?
These instructions aren't meant to be static. Instead, they are getting updated
So, after reinstalling Mac OS X as I did to get out of the startup crash as I
did, even if ports stayed in place, I should re-perform the
LibcxxOnOlderSystems steps?
Pat
El 2016-08-27, a las 12:17, Mihai Moldovan escribió:
> On 27.08.2016 04:00 PM, [ftp83plus] wrote:
>> Crash log,
On 27.08.2016 04:00 PM, [ftp83plus] wrote:
> Crash log, approximately when gtk3 segfaulted:
>
> http://pastebin.com/bzuez8Xp
In there, I see two things that look weird:
- you're using ld64-136, although step 8 and 9 of the LibcxxOnOlderSystems
guide explicitly says to switch to
Crash log, approximately when gtk3 segfaulted:
http://pastebin.com/bzuez8Xp
El 2016-08-27, a las 02:20, [ftp83plus] escribió:
> Oh, and what is this file, specifically? Not sure
>
> El 2016-08-27, a las 02:09, Ryan Schmidt escribió:
>
>>
>>
>> On Aug 27, 2016, at 00:45, [ftp83plus]
Oh, and what is this file, specifically? Not sure
El 2016-08-27, a las 02:09, Ryan Schmidt escribió:
>
>
> On Aug 27, 2016, at 00:45, [ftp83plus] wrote:
>
>> See attached:
>>
>> Link:
>> http://ovh.to/jgFHoPk
>
> That's the main.log generated by MacPorts. I meant the
> On Aug 27, 2016, at 00:45, [ftp83plus] wrote:
>
> See attached:
>
> Link:
> http://ovh.to/jgFHoPk
That's the main.log generated by MacPorts. I meant the crash log generated by
macOS. It'll be in your DiagnosticReports directory.
>
>> El 2016-08-26, a las 19:24,
> On Aug 26, 2016, at 10:51 AM, [ftp83plus] wrote:
>
> Knowing that a Segmentation fault doesn't mean much, I cleaned gtk3 at
> attempted a rebuild, but it still segfaults for some reason.
Could you attach the crash log?
___
It's going to be something like that.
I've also seen a few executables at times that are linked to both -libc++ and
to -libstdc++, and you just know that can't be a good thing. (Probably exactly
what you're suggesting.)
No doubt, although this libc++ upgrade enables quite a bit more software
Nope - your clang-3.7 is working, it appears.
Thanks for checking.
??
K
On 2016-08-26, at 10:08 AM, [ftp83plus] wrote:
> Here it the output: http://pastebin.com/JJ4iUjPU
>
> El 2016-08-26, a las 12:55, Ken Cunningham escribió:
>
>> Hmm.
>>
>> Would you mind test compiling your hello
Here it the output: http://pastebin.com/JJ4iUjPU
El 2016-08-26, a las 12:55, Ken Cunningham escribió:
> Hmm.
>
> Would you mind test compiling your hello world program like this, and see
> what happens? (This is the specific clang you're segfaulting). -- Ken
>
> /opt/local/bin/clang-mp-3.7 -v
Hmm.
Would you mind test compiling your hello world program like this, and see what
happens? (This is the specific clang you're segfaulting). -- Ken
/opt/local/bin/clang-mp-3.7 -v hw.c -o hw2
On 2016-08-26, at 9:39 AM, [ftp83plus] wrote:
> Complete main.log for failure to upgrade gtk3, after
Complete main.log for failure to upgrade gtk3, after the first clean-up with
"port clean gtk3": http://ovh.to/jgFHoPk
However, maybe it's worthy of note that previous ports upgraded as part of the
"upgrade outdated" operation didn't threw any error.
My sample "Hello world" program does not do
On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> There must be a more elegant answer / way to do this, though. And there
> must be some explanation for what happens to cause this -- but I don't know
> what it is at present.
Possibly some port
> On Aug 26, 2016, at 12:01 PM, [ftp83plus] wrote:
>
> This log is truncated because Pastebin doesn't accept its large size for free
> users. How would I post that?
https://trac.macports.org/newticket
vq
___
macports-users
On Fri, Aug 26, 2016 at 12:01 PM, [ftp83plus] wrote:
> This log is truncated because Pastebin doesn't accept its large size for
> free users. How would I post that?
>
Dropbox?
If you really can't do anything else, can you at least include some 20 or
so lines from *before*
Yikes. Clang is segfaulting on you again, eh? Do I assume you're still using
the libc++ upgrade for older systems on snow leopard? This has happened to me a
couple of times, as you know from previous discussions.
Try writing up and running just a simple clang compilation on a five-line
"hello,
This log is truncated because Pastebin doesn't accept its large size for free
users. How would I post that?
El 2016-08-26, a las 11:56, Brandon Allbery escribió:
>
> On Fri, Aug 26, 2016 at 11:51 AM, [ftp83plus] wrote:
> Knowing that a Segmentation fault doesn't mean
On Fri, Aug 26, 2016 at 11:51 AM, [ftp83plus] wrote:
> Knowing that a Segmentation fault doesn't mean much, I cleaned gtk3 at
> attempted a rebuild, but it still segfaults for some reason.
> http://pastebin.com/TK81EYnZ
>
>
> What is the source of the problem?
>
You
Hello there,
just encountered this issue when gtk3 tried to rebuild as part of an upgrade
outdated operation:
Relevant extract of main.log: http://pastebin.com/KL0kKinG
Knowing that a Segmentation fault doesn't mean much, I cleaned gtk3 at
attempted a rebuild, but it still segfaults for some
29 matches
Mail list logo