> On 19 Dec 2017, at 20:33, Josh Freeman <[email protected]> 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, which is to > use an older version of GNUstep Make. > > However, the workaround is already included in the "16.04, 16.10, & 17.04" > install script at > http://wiki.gnustep.org/index.php/GNUstep_under_Ubuntu_Linux , so did you > happen to make any changes to the script before running it, or perhaps run it > on a machine that already had an earlier GNUstep install? (I just tried the > wiki script on a clean, up-to-date Ubuntu 16.04 VM (32bit) - the only script > change was to set the PROMPT var to 'false' to avoid having to press <Return> > after each build - and the built apps seem to run OK). > > Cheers, > > Josh > > > [1] http://lists.gnu.org/archive/html/discuss-gnustep/2017-04/msg00070.html > [2] http://lists.gnu.org/archive/html/discuss-gnustep/2017-06/msg00026.html
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 -fobjc-nonfragile-abi flag when building nonfragile I've just removed that addition of -fobjc-nonfragile-abi from the current gnustep-base in git, so if gnustep is built for the new runtime with clang (the ng-gnu-gnu library combo) neither make nor base should add ther old flag. _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
