> On 29 Dec 2017, at 05:56, Josh Freeman wrote:
> When using the nonfragile ABI, the compiler emits code that calculates ivar
> offsets using global variables - there's a global for each ivar, using the
> naming convention:
>
> On 29 Dec 2017, at 05:56, Josh Freeman wrote:
>
>
> On Dec 28, 2017, at 9:25 AM, Richard Frith-Macdonald wrote:
>
>>> On 28 Dec 2017, at 14:00, Fred Kiefer wrote:
>>> First a thank you to both Josh and Richard for gathering so much
>>>
On Dec 28, 2017, at 9:25 AM, Richard Frith-Macdonald wrote:
On 28 Dec 2017, at 14:00, Fred Kiefer wrote:
First a thank you to both Josh and Richard for gathering so much
information on this issue and to Richard for the quick workaround.
I hope this lets simple GNUstep
> On 28 Dec 2017, at 14:00, Fred Kiefer wrote:
>
>
>
>> Am 23.12.2017 um 12:15 schrieb Richard Frith-Macdonald
>> :
>>> On 23 Dec 2017, at 09:42, Richard Frith-Macdonald
>>> wrote:
> Am 23.12.2017 um 12:15 schrieb Richard Frith-Macdonald
> :
>> On 23 Dec 2017, at 09:42, Richard Frith-Macdonald
>> wrote:
>>> On 23 Dec 2017, at 09:32, Richard Frith-Macdonald
>>>
FYI - I did recompile everything using the April 2017 "makefiles" commit
(all with clang) and it all works fine.
On Wed, Dec 20, 2017 at 6:16 AM, Richard Frith-Macdonald <
richard.frith-macdon...@theengagehub.com> wrote:
>
>
> > On 19 Dec 2017, at 20:33, Josh Freeman
> On 23 Dec 2017, at 09:42, Richard Frith-Macdonald
> wrote:
>
>
>
>> On 23 Dec 2017, at 09:32, Richard Frith-Macdonald
>> wrote:
>>
>>
>> So the difference between the offsets in the runtime (correct)
> On 23 Dec 2017, at 09:32, Richard Frith-Macdonald
> wrote:
>
>
> So the difference between the offsets in the runtime (correct) and the
> compiler (wrong) was 16 bytes, with the runtime thinking the strruct size was
> 32 and trhe compiler
> On 23 Dec 2017, at 05:19, Josh Freeman wrote:
>
> On Dec 22, 2017, at 10:05 AM, Richard Frith-Macdonald wrote:
>
>> I think that's a possible indication of a bug in the compiler/runtime
>> nonfragile API support; it looks as if there may be an inconsistency
On Dec 22, 2017, at 10:05 AM, Richard Frith-Macdonald wrote:
I think that's a possible indication of a bug in the compiler/
runtime nonfragile API support; it looks as if there may be an
inconsistency in calculating the size of a structure used as an ivar.
After more testing, here's
> On 22 Dec 2017, at 15:05, Richard Frith-Macdonald
> wrote:
>
>
> I then checked that both NSThread.m and NSGraphicsContext.m were compiled by
> clang with -D_NONFRAGILE_ABI=1 and -fobjc-runtime=gnustep-1.8
>
> On a hunch, I looked at the ivar
> On 21 Dec 2017, at 23:01, Ivan Vučica wrote:
>
> On Thu, Dec 21, 2017 at 7:53 PM, Richard Frith-Macdonald
> wrote:
> >>> gnustep-make has been using -fobjc-runtime= rather than
> >>> -fobjc-nonfragile-abi for quita long time, but
On Thu, Dec 21, 2017 at 11:01 PM, Ivan Vučica wrote:
> On Thu, Dec 21, 2017 at 7:53 PM, Richard Frith-Macdonald <
> richard.frith-macdon...@theengagehub.com> wrote:
> >> Compiling file GSConcreteValue.m ...
> >> In file included from In file included from In file included from
>
On Thu, Dec 21, 2017 at 7:53 PM, Richard Frith-Macdonald <
richard.frith-macdon...@theengagehub.com> wrote:
>>> gnustep-make has been using -fobjc-runtime= rather than
-fobjc-nonfragile-abi for quita long time, but I just found that the
gnustep-base configure script was still adding the obsolete
> On 21 Dec 2017, at 19:03, Josh Freeman wrote:
>
>
> On Dec 20, 2017, at 9:16 AM, Richard Frith-Macdonald wrote:
>
>>> On 19 Dec 2017, at 20:33, Josh Freeman
>>> wrote:
>>>
>>> Hi Tom,
>>>
>>> This appears to be the same
On Dec 20, 2017, at 9:16 AM, Richard Frith-Macdonald wrote:
On 19 Dec 2017, at 20:33, Josh Freeman wrote:
Hi Tom,
This appears to be the same issue as the Base/GUI ivar-offset
mismatch that was discussed back in April [1] & June [2].
While the issue
> On 19 Dec 2017, at 20:33, Josh Freeman wrote:
>
> Hi Tom,
>
> This appears to be the same issue as the Base/GUI ivar-offset mismatch that
> was discussed back in April [1] & June [2].
>
> While the issue still hasn't been fixed, there is a workaround,
Hi Tom,
This appears to be the same issue as the Base/GUI ivar-offset
mismatch that was discussed back in April [1] & June [2].
While the issue still hasn't been fixed, there is a workaround,
which is to use an older version of GNUstep Make.
However, the workaround is already
It may be obvious, but I suppose you rebuilt all four apps too?
uto, 19. pro 2017. u 14:29 Tom Sheffler napisao je:
> I've installed GNUstep on Ubuntu16. The installation was performed
> according to this guide for Ubuntu:
>
I've installed GNUstep on Ubuntu16. The installation was performed
according to this guide for Ubuntu:
http://wiki.gnustep.org/index.php/GNUstep_under_Ubuntu_Linux and it went as
smoothly as possible.
The four GS Applications named above all fail in the same way. Here is a
backtrace running
20 matches
Mail list logo