I've added a package objc-3.3.31.tar.gz at https://sourceforge.net/projects/objc.
The configure script has been updated to do a test on ANSI C tentative definitions
(which was called the postlink test in the past).
The update on the configure script now tests for this new situation for GCC 10+,
it first tests for the original ANSI C specification for tentative definitions
(which is still supported by gcc10+ if you enable -fcommon but that is not the default),
and then it also tests for the gcc10+ case when it defaults to -fno-common,
and enables the old (regular) non-postlink case for automatic runtime initialisation even in the case.
So for gcc, automatic runtime initialisation is selected in both -fcommon and -fno-common.
Most UNIX compilers anyway select automatic runtime initialisation by default.
The postlink case also works on UNIX and can be enabled by configure --with-postlink.
The postlink case is/was the only option on some C compilers like the Watcom C compiler
See the Portable Object Compiler manual for a full discussion on the issue.
There is also a new objc-bootstrap-3.3.31.tar.gz package.
I've also noticed that on some recent bison implementations,
the compiler does not compile using YACC='bison -y -d',
however YACC=byacc is recommended and a solution/workaround in those cases.
Because bison fixes may happen in the future I'm not looking into supporting bison "per se";
bison has worked and sometimes still works,
YACC=yacc on the Solaris OS still works (that is using the original AT&T derived original yacc).
Regards,
David Stes
|
