On 19 Jun 2017, at 23:43, Josh Freeman wrote:
>
> The segmentation fault happens after Base sets the value of an NSThread
> ivar, because the memory location it writes to overlaps the area in memory
> where GUI expects to find a different ivar, due to the
-Matt
--
Sent from my iPhone 6S Plus
> On Jun 19, 2017, at 18:43, Josh Freeman
> wrote:
>
>
> * Removed 'ninja' package from install requirements (package no longer exists
> in 17.04 - probably wasn't the correct package anyways; 'ninja' package was a
>
> On 19 Jun 2017, at 11:11, Richard Frith-Macdonald
> wrote:
>
>
>> On 19 Jun 2017, at 10:10, David Chisnall wrote:
>>
>> On 24 Apr 2017, at 09:57, Richard Frith-Macdonald
>> wrote:
>>>
> On 19 Jun 2017, at 10:10, David Chisnall wrote:
>
> On 24 Apr 2017, at 09:57, Richard Frith-Macdonald
> wrote:
>>
>> Setting variables in make is fairly straightforward, but I think only you
>> (and clang geeks) understand how
On 24 Apr 2017, at 09:57, Richard Frith-Macdonald
wrote:
>
> Setting variables in make is fairly straightforward, but I think only you
> (and clang geeks) understand how these flags are actually supposed to work.
>
> How are you supposed to turn use
Hi folks,
Just wanted to let you know this issue appears to remain unresolved. Today I
checked out and built all sources from the git repo under Ubuntu 16.04. The
simple GUI test[1] built with a Makefile and run with openapp ./GUItest.app
segfaults.
(But it runs fine if I compile it by hand
I can confirm that for a successful GNUstep build on Ubuntu 16.04, it is
sufficient to check out the older version of GNUstep Make -- no need to check
out older versions of the other repositories.
openapp ./GUITest worked without crashing.
Patryk
On Apr 23, 2017, at 04:22 PM, Josh
> On 24 Apr 2017, at 08:42, David Chisnall wrote:
>
> -fobjc-nonfragile-abi has been a deprecated flag for 2-3 years. Please can
> someone who understands GNUstep Make fix the build system to use
> -fobjc-runtime= instead?
The build system already uses -fobjc-runtime= ...
-fobjc-nonfragile-abi has been a deprecated flag for 2-3 years. Please can
someone who understands GNUstep Make fix the build system to use
-fobjc-runtime= instead?
David
> On 23 Apr 2017, at 23:34, Josh Freeman wrote:
>
> Turns out the issue is with the
Sorry, the git checkout command for workaround #2 in my previous
message is missing "master" at the end:
git checkout `git rev-list -1 --first-parent --before=2017-04-06`
should be:
git checkout `git rev-list -1 --first-parent --before=2017-04-06 master`
On Apr 23, 2017, at 6:34 PM, Josh
Turns out the issue is with the placement of the objc-nonfragile-
abi build flag in common.make, line 670: For some reason, the affected
distros (seen so far on: Ubuntu 16.04, Mint 18.1, Debian Jessie;
32bit, perhaps 64bit?) will build base & gui with mismatched and/or
broken ABIs if
Thank you Josh,
this was an excellent analysis. Did you try to unset GNUSTEP_BASE_LIBRARY in
NSGraphicsContext.m? That should switch to the other code path that won’t use
internal structures from base.
As for the problem with the NSThread ivars. What has changed on your test
system? Do you
Hi Bertrand,
Thanks for the info! I'm seeing the same issue - after making a
clean GNUstep install from the trunk, any app built from it segfaults
immediately, always in the same location: +[NSGraphicsContext
setCurrentContext:]. This is on two different virtual machines, one
with
Sorry for the mistake, I didn't send the correct script (missing the
i386 architecture option). Here it is again.
Bertrand
Le 23/04/2017 à 03:23, Bertrand Gmail a écrit :
Hi, Yan
I've spent several hours trying to reinstall again and again with
clang, objc2, blocks and so on.
And yes,
Hi, Yan
I've spent several hours trying to reinstall again and again with clang,
objc2, blocks and so on.
And yes, it's a real pain. But I've got now something that seems to be
finally running.
First of all, regarding your initial question on adding the 386
architecture on debian Jessie ;
Sorry, this is the point where I have to drop out. Perhaps David has time to
take over? For this reason I send this mail again to the mailing list. That way
you will get the best support available.
What you are getting is a mismatch between the available Objective-C runtimes.
What I could
16 matches
Mail list logo