Mail Archives: djgpp-workers/2006/06/16/00:51:28
decker AT dacafe DOT com kirjoitti:
> Hi Andris,
>
>
>> Then perhaps the only way is to write some small tool to generate
>> compiler options while build.
>
> Not so sure about that...
I thought something like in top level Makefile:
gcc.opt:
$(CROSS_GCC) -E -dD -x c /dev/null | awk -f some_script >gcc.opt
some_script would process #define lines generated by GCC preprocessor,
extract version information and output and output options file. I don't
think it would be so complicated. At the same time it would be nice to
get rid also of option -I-, which is deprecated in new GCC versions.
>
>
>> If You are still stuck with gcc-3.3, then at least please update to the
>> latest of gcc-3.3X series (gcc-3.3.6). _environ was added to djgpp-x.djl
>> beginning with DJGPP port of gcc-3.3.5.
>
> Yes, it was me. Well strange - until now I never felt "stuck" with using
> gcc 3.3.2 :) I 'upgraded' to that a couple of years ago and it has worked
> just fine. Perhaps something important like libc should be kept at least a
> few years backward compatible? The occasional DOS developer might not be
> very happy to need to chase every small upgrade as it comes along. We do
> want people to do testing, right:)? That being said, I myself was planning
> soon to upgrade to 4.1.x sometime toward the end of that minor release.
What choise I had when this change were introduced in CVS version of
DJGPP? Perhaps only to add support of for the next release of DJGPP port
of GCC.
About being stuch with gcc-3.3 I thought, that You may have sources,
that may not compile with newer versions without large enough efforts.
In that case upgrade to 3.3.6 should not however be a problem.
Andris
- Raw text -