Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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 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 for gtk3
> --->  Fetching distfiles for gtk3
> --->  Attempting to fetch gtk+-3.20.9.tar.xz from 
> http://sea.us.distfiles.macports.org/macports/distfiles/gtk3
> --->  Attempting to fetch gtk+-3.20.9.tar.xz from 
> https://muug.ca/mirror/gnome/sources/gtk+/3.20/
> --->  Verifying checksums for gtk3
>
> --->  Extracting gtk3
> --->  Applying patches to gtk3
> --->  Configuring gtk3
> --->  Building gtk3
> --->  Staging gtk3 into destroot
> --->  Installing gtk3 @3.20.9_0+quartz
> --->  Cleaning gtk3
> --->  Computing dependencies for gtk3
> --->  Deactivating gtk3 @3.20.6_0+quartz
> --->  Cleaning gtk3
> --->  Activating gtk3 @3.20.9_0+quartz
> --->  Cleaning gtk3
> --->  Updating database of binaries
> --->  Scanning binaries for linking errors
> --->  No broken files found. 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 for gtk3
--->  Fetching distfiles for gtk3
--->  Attempting to fetch gtk+-3.20.9.tar.xz from 
http://sea.us.distfiles.macports.org/macports/distfiles/gtk3
--->  Attempting to fetch gtk+-3.20.9.tar.xz from 
https://muug.ca/mirror/gnome/sources/gtk+/3.20/
--->  Verifying checksums for gtk3  
 
--->  Extracting gtk3
--->  Applying patches to gtk3
--->  Configuring gtk3
--->  Building gtk3
--->  Staging gtk3 into destroot
--->  Installing gtk3 @3.20.9_0+quartz
--->  Cleaning gtk3
--->  Computing dependencies for gtk3
--->  Deactivating gtk3 @3.20.6_0+quartz
--->  Cleaning gtk3
--->  Activating gtk3 @3.20.9_0+quartz
--->  Cleaning gtk3
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

LibCxx on older systems toolchain blew up on 10.6 -- and fixed -- WAS Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 don't appear 
(to me) to be able to work. 

But I believe have it fixed now, I think, with one small change in the 
instructions,  and one small change in the ld64 portfile.

I was unable to resuscitate the toolchain after it pulled in ld64 +llvm34, and 
ultimately I had to uninstall the toolchain completely and start over.

The current LibCxxOnOlderSystems instructions are mixed between +llvm37 and 
+llvm38. You can't use +llvm37 or clang-3.7 options because they no longer 
exist in cctools or ld64, so +llvm34 will get pulled back in instead.

The install goes OK if you ignore all the references to +llvm37 or clang-3.7, 
and just insert +llvm38 or clang-3.8 instead.


HOWEVER you can't build ld64 against +llvm38 due to errors in math.h (as Jeremy 
pointed out).

sudo port -v upgrade --enforce-variants ld64 -ld64_97 -ld64_127 -ld64_136 
-ld64_236


As per:



These math errors appear to be fixed on 10.6 by adding this line in the ld64 
portfile -- 

configure.cppflags-append -I${workpath}/dyld-${dyld_version}/include
+configure.cppflags-append -U__STRICT_ANSI__

And then it all installs and appears to be a coherent toolchain that works 
again (with clang-3.8, llvm-3.8).

Best,

Ken



On 2016-08-29, at 1:45 AM, Mojca Miklavec wrote:

> 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 
>> inoperable.
>> 
>> there isn't an llm37 option in the ld64 portfile any longer.
>> 
>> I either have to add one -- or -- reinstall everything
>> 
>> but the  instructions 
>> currently have a mixture of clang-3.7 references and llvm38 references.
> 
> That's partially because it was written when 3.7 made sense (ok, it
> was probably earlier, when 3.5 or 3.6 was there), then 3.8 was
> released, but buggy, so some instructions reverted back to 3.7 ...
> 
>> I thought 3.8 was not yet workable, and so we were to stick with 3.7 -- 
>> maybe this is in transition?
> 
> Probably. Your feedback might help though.
> 
>> Looks like I need to let this all settle down in the portfile evolution for 
>> a bit, and come back in a few days :>
> 
> Jeremy was cleaning up some of these files recently and it's quite
> likely that not all of the changes were heavily tested on 10.5 and
> 10.6.
> 
> As an example, a recently discovered problem on 10.5 has just been
> fixed and more changes have been applied just now. It makes sense to
> open a new ticket for a problem like the one you mentioned. (Actually,
> it also makes sense to upload crash reports and other problems to a
> ticket in Trac. Trac can easily handle a 2 MB file that pastebin is
> refusing.)
> 
> The setup for libc++ has a very small audience / a very small pool of
> testers. Until we set up new build slaves and attract more users,
> problems are to be expected. (Even then it will still be a problem
> because most developers use the latest OS, so there are very often
> very few people able to help.) Most support for old OSes is there
> because those OSes used to be "up-to-date" some time back and
> developers made sure everything was working (at least until new
> software came up that required C++11). The libc++ support came later
> and is constantly evolving due to releases of newer compilers.
> 
> Mojca

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Mojca Miklavec]

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 
> inoperable.
>
> there isn't an llm37 option in the ld64 portfile any longer.
>
> I either have to add one -- or -- reinstall everything
>
> but the  instructions 
> currently have a mixture of clang-3.7 references and llvm38 references.

That's partially because it was written when 3.7 made sense (ok, it
was probably earlier, when 3.5 or 3.6 was there), then 3.8 was
released, but buggy, so some instructions reverted back to 3.7 ...

> I thought 3.8 was not yet workable, and so we were to stick with 3.7 -- maybe 
> this is in transition?

Probably. Your feedback might help though.

> Looks like I need to let this all settle down in the portfile evolution for a 
> bit, and come back in a few days :>

Jeremy was cleaning up some of these files recently and it's quite
likely that not all of the changes were heavily tested on 10.5 and
10.6.

As an example, a recently discovered problem on 10.5 has just been
fixed and more changes have been applied just now. It makes sense to
open a new ticket for a problem like the one you mentioned. (Actually,
it also makes sense to upload crash reports and other problems to a
ticket in Trac. Trac can easily handle a 2 MB file that pastebin is
refusing.)

The setup for libc++ has a very small audience / a very small pool of
testers. Until we set up new build slaves and attract more users,
problems are to be expected. (Even then it will still be a problem
because most developers use the latest OS, so there are very often
very few people able to help.) Most support for old OSes is there
because those OSes used to be "up-to-date" some time back and
developers made sure everything was working (at least until new
software came up that required C++11). The libc++ support came later
and is constantly evolving due to releases of newer compilers.

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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

I either have to add one -- or -- reinstall everything

but the  instructions 
currently have a mixture of clang-3.7 references and llvm38 references.

I thought 3.8 was not yet workable, and so we were to stick with 3.7 -- maybe 
this is in transition?

Looks like I need to let this all settle down in the portfile evolution for a 
bit, and come back in a few days :>

Ken
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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.

... have to do a better fix once I figure out what's happening here. -- K


> 
> and that looks to me like the correct mixture. 
> 
> Ken
> 
> 
> 
> 
> On 2016-08-28, at 7:52 AM, Ken Cunningham wrote:
> 
>> I note that ld64-latest, ld64-136, and cctools were all updated just now.
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 @3.4.2_11
--->  Fetching distfiles for ld64-latest
--->  Verifying checksums for ld64-latest
--->  Extracting ld64-latest
--->  Applying patches to ld64-latest
--->  Configuring ld64-latest
--->  Building ld64-latest
--->  Staging ld64-latest into destroot
--->  Installing ld64-latest @264.3.102_2+llvm34
--->  Computing dependencies for ld64-latest
--->  Deactivating ld64-latest @264.3.102_1+llvm37
--->  Activating ld64-latest @264.3.102_2+llvm34

this is not expected. Maybe this happened to you.

do

$ port -v installed ld64*
The following ports are currently installed:
 ld64 @2_0-ld64_127-ld64_136-ld64_236-ld64_97 (active) platform='darwin 10' 
archs='x86_64'
 ld64 @2_0+ld64_136 platform='darwin 10' archs='x86_64'
 ld64-136 @136_5+llvm34 platform='darwin 10' archs='x86_64'
 ld64-136 @136_5+llvm37-llvm34 (active) platform='darwin 10' archs='x86_64'
 ld64-latest @264.3.102_1+llvm37 platform='darwin 10' archs='x86_64'
 ld64-latest @264.3.102_2+llvm34 (active) platform='darwin 10' archs='x86_64'

and if you get something like what I got above: 

sudo port activate ld64-latest @264.3.102_1+llvm37

$ sudo port activate ld64-latest @264.3.102_1+llvm37
--->  Computing dependencies for ld64-latest
--->  Deactivating ld64-latest @264.3.102_2+llvm34
--->  Activating ld64-latest @264.3.102_1+llvm37

then recheck:

$ port -v installed ld64*
The following ports are currently installed:
 ld64 @2_0-ld64_127-ld64_136-ld64_236-ld64_97 (active) platform='darwin 10' 
archs='x86_64'
 ld64 @2_0+ld64_136 platform='darwin 10' archs='x86_64'
 ld64-136 @136_5+llvm34 platform='darwin 10' archs='x86_64'
 ld64-136 @136_5+llvm37-llvm34 (active) platform='darwin 10' archs='x86_64'
 ld64-latest @264.3.102_1+llvm37 (active) platform='darwin 10' archs='x86_64'
 ld64-latest @264.3.102_2+llvm34 platform='darwin 10' archs='x86_64'


and that looks to me like the correct mixture. 

Ken




On 2016-08-28, at 7:52 AM, Ken Cunningham wrote:

> I note that ld64-latest, ld64-136, and cctools were all updated just now.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 AM, Ken Cunningham wrote:

> 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 have time to create that right now.
> 
> I don't know if you can just uninstall and then reinstall ld64 to "short 
> version"  the reinstall of what appears to be the faulty executable. I would 
> probably try to see if I could do that, myself. I suspect the dependencies 
> might prevent that.
> 
> I think ultimately you're into the reinstall of the tool chain that I 
> described previously to fix the segfaulting ld64.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 have time to create that right now.

I don't know if you can just uninstall and then reinstall ld64 to "short 
version"  the reinstall of what appears to be the faulty executable. I would 
probably try to see if I could do that, myself. I suspect the dependencies 
might prevent that.

I think ultimately you're into the reinstall of the tool chain that I described 
previously to fix the segfaulting ld64.

Having these as binaries that you could install rather than the 6 hour 
compiling process would make it less painful. I usually run it overnight (the 
clang and llvm parts take all the time). I know you have to "build from source" 
for this system at present (lots of talk about the buildbot coming soon, 
though). 

You are coming through some 'real-world' issues that are helpful to figure out 
any inconsistencies in the system. 

I hope this helps,

Ken




On 2016-08-28, at 1:44 AM, Ryan Schmidt wrote:

> 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 macOS does not necessitate 
> reinstalling MacPorts and your ports. However, the issues Mihai noted may 
> require reinstalling the affected ports. I'm not an expert at reading crash 
> logs so I can't say for certain why your crash occurred. I just know that 
> when a crash occurs, you should provide the crash log so that someone who is 
> more familiar might be able to help. 
> 
> 
> 
>>> El 2016-08-27, a las 12:17, Mihai Moldovan escribió:
>>> 
 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 ld64-latest
>>> - ld64-136 was installed with +llvm37, although step 5 and 7 make sure that
>>>  +llvm38 is used
>>> 
>>> The second problem may be explicable by upgrading - earlier versions 
>>> probably
>>> used llvm37 and the llvm38 change is relatively new.
>>> 
>>> Still, your setup is broken/deviates from what is advertised to work on 
>>> 10.6.
>>> That crash is probably a consequence of that.
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ryan Schmidt]

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 macOS does not necessitate 
reinstalling MacPorts and your ports. However, the issues Mihai noted may 
require reinstalling the affected ports. I'm not an expert at reading crash 
logs so I can't say for certain why your crash occurred. I just know that when 
a crash occurs, you should provide the crash log so that someone who is more 
familiar might be able to help. 



>> El 2016-08-27, a las 12:17, Mihai Moldovan escribió:
>> 
>>> 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 ld64-latest
>> - ld64-136 was installed with +llvm37, although step 5 and 7 make sure that
>>   +llvm38 is used
>> 
>> The second problem may be explicable by upgrading - earlier versions probably
>> used llvm37 and the llvm38 change is relatively new.
>> 
>> Still, your setup is broken/deviates from what is advertised to work on 10.6.
>> That crash is probably a consequence of that.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Mihai Moldovan]

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
by Jeremy pretty often and reliable whenever something changes in the toolchain.

I guess it can be implied to check the page now and than to make sure the system
still matches with what is being described on the wiki page and take necessary
measures to sync it up - not necessarily by reinstalling everything blindly, but
abstracting from the information presented.



Mihai



signature.asc
Description: OpenPGP digital signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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, 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 ld64-latest
>  - ld64-136 was installed with +llvm37, although step 5 and 7 make sure that
>+llvm38 is used
> 
> The second problem may be explicable by upgrading - earlier versions probably
> used llvm37 and the llvm38 change is relatively new.
> 
> Still, your setup is broken/deviates from what is advertised to work on 10.6.
> That crash is probably a consequence of that.
> 
> 
> 
> Mihai
> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Mihai Moldovan]

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 ld64-latest
  - ld64-136 was installed with +llvm37, although step 5 and 7 make sure that
+llvm38 is used

The second problem may be explicable by upgrading - earlier versions probably
used llvm37 and the llvm38 change is relatively new.

Still, your setup is broken/deviates from what is advertised to work on 10.6.
That crash is probably a consequence of that.



Mihai




signature.asc
Description: OpenPGP digital signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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]  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, Ryan Schmidt escribió:
>>> 
 
> 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?
 
>>> 
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[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 crash log generated by 
> macOS. It'll be in your DiagnosticReports directory. 
> 
> 
>> 
>> El 2016-08-26, a las 19:24, Ryan Schmidt escribió:
>> 
>>> 
 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?
>>> 
>> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ryan Schmidt]

> 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, Ryan Schmidt escribió:
>> 
>> 
>>> 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?
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ryan Schmidt]

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

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 to 
build and run, you do need to keep your wits about you.

K



On 2016-08-26, at 9:13 AM, Brandon Allbery wrote:

> 
> On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham 
>  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 somewhere along the line is buggy and not using the libcxx 
> settings; when you reset everything you remove that port, and everything is 
> fine until it gets pulled back in and then subsequent builds find it. (If 
> this is happening in clang itself, it could be a build tool that is not 
> compatible.)
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 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 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 much, but compiles without 
>>> segfaulting:
>>> clang hw.c -o hw2
>>> hw.c:5:1: warning: type specifier missing, defaults to 'int' 
>>> [-Wimplicit-int]
>>> main()
>>> ^~~~
>>> 1 warning generated.
>>> 
>>> 
>>> Of course I could re-do the whole LibcXXOnOlderSystems process, but it's a 
>>> bit on the slow and noisy side
>>> 
>>> 
>>> El 2016-08-26, a las 12:13, Brandon Allbery escribió:
>>> 
 
 On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham 
  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 somewhere along the line is buggy and not using the 
 libcxx settings; when you reset everything you remove that port, and 
 everything is fine until it gets pulled back in and then subsequent builds 
 find it. (If this is happening in clang itself, it could be a build tool 
 that is not compatible.)
 
 -- 
 brandon s allbery kf8nh   sine nomine 
 associates
 allber...@gmail.com  
 ballb...@sinenomine.net
 unix, openafs, kerberos, infrastructure, xmonad
 http://sinenomine.net
>>> 
>> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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 hw.c -o hw2
> 
> 
> On 2016-08-26, at 9:39 AM, [ftp83plus] wrote:
> 
>> 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 much, but compiles without 
>> segfaulting:
>> clang hw.c -o hw2
>> hw.c:5:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
>> main()
>> ^~~~
>> 1 warning generated.
>> 
>> 
>> Of course I could re-do the whole LibcXXOnOlderSystems process, but it's a 
>> bit on the slow and noisy side
>> 
>> 
>> El 2016-08-26, a las 12:13, Brandon Allbery escribió:
>> 
>>> 
>>> On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham 
>>>  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 somewhere along the line is buggy and not using the 
>>> libcxx settings; when you reset everything you remove that port, and 
>>> everything is fine until it gets pulled back in and then subsequent builds 
>>> find it. (If this is happening in clang itself, it could be a build tool 
>>> that is not compatible.)
>>> 
>>> -- 
>>> brandon s allbery kf8nh   sine nomine associates
>>> allber...@gmail.com  ballb...@sinenomine.net
>>> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
>> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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 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 much, but compiles without 
> segfaulting:
> clang hw.c -o hw2
> hw.c:5:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
> main()
> ^~~~
> 1 warning generated.
> 
> 
> Of course I could re-do the whole LibcXXOnOlderSystems process, but it's a 
> bit on the slow and noisy side
> 
> 
> El 2016-08-26, a las 12:13, Brandon Allbery escribió:
> 
>> 
>> On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham 
>>  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 somewhere along the line is buggy and not using the 
>> libcxx settings; when you reset everything you remove that port, and 
>> everything is fine until it gets pulled back in and then subsequent builds 
>> find it. (If this is happening in clang itself, it could be a build tool 
>> that is not compatible.)
>> 
>> -- 
>> brandon s allbery kf8nh   sine nomine associates
>> allber...@gmail.com  ballb...@sinenomine.net
>> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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 much, but compiles without 
segfaulting:
clang hw.c -o hw2
hw.c:5:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
main()
^~~~
1 warning generated.


Of course I could re-do the whole LibcXXOnOlderSystems process, but it's a bit 
on the slow and noisy side


El 2016-08-26, a las 12:13, Brandon Allbery escribió:

> 
> On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham 
>  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 somewhere along the line is buggy and not using the libcxx 
> settings; when you reset everything you remove that port, and everything is 
> fine until it gets pulled back in and then subsequent builds find it. (If 
> this is happening in clang itself, it could be a build tool that is not 
> compatible.)
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Brandon Allbery]

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 somewhere along the line is buggy and not using the
libcxx settings; when you reset everything you remove that port, and
everything is fine until it gets pulled back in and then subsequent builds
find it. (If this is happening in clang itself, it could be a build tool
that is not compatible.)

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Lawrence Velázquez]

> 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 mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Brandon Allbery]

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* the segfault so there's some chance of determining
what caused it?

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ken Cunningham]

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, world" app in C to see if it's just clang blowing up. I think you'll 
find it is, and if so, it has nothing to do with gtk specifically.

If you find that it is just a dead clang-3.7 (on that hello, world test), 
here's what I do to fix it:

Although I __do not__ fully understand what inconsistency between tools seems 
to develop in the toolchain that leads to this, in each case (three times now 
in three months) I've resolved it by fully unintstalling all versions of clang, 
llvm, cctools, and ld64 (often having to --follow-dependents to make the 
uninstall happen), resetting the macports.conf and variants.conf back to their 
defaults, and then reinstalling LibCxxOnOlderSystems from the beginning. That 
has fixed the problem in every case, __for me__ .

you need to get it spotless clean, though -- port -v installed clang* llvm* 
cctools* and ld* all have to show nothing. Then the reinstall works and all is 
well, although it's time wasted.

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.

But anyway, that is how I do it.

Ken






On 2016-08-26, at 8:51 AM, [ftp83plus] wrote:

> 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 reason.
> http://pastebin.com/TK81EYnZ
> 
> What is the source of the problem?
> 
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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 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 chopped off everything that would have told us that, and included 
> unrelated stuff following it instead. Please provide a complete main.log; if 
> you have to rebuild it to get one, make sure you "sudo port clean gtk3" first.
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Brandon Allbery]

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 chopped off everything that would have told us that, and included
unrelated stuff following it instead. Please provide a complete main.log;
if you have to rebuild it to get one, make sure you "sudo port clean gtk3"
first.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[[ftp83plus]]

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 reason.
http://pastebin.com/TK81EYnZ

What is the source of the problem?


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users