Mail Archives: djgpp-workers/2001/08/21/07:44:28
On 12 Jul 2001, at 21:58, Eli Zaretskii wrote:
> > From: pavenis AT lanet DOT lv
> > Date: Thu, 12 Jul 2001 18:48:35 +0300
> >
> > Builtin script from bnu2112b.zip seems to be compatible with gcc-3.0
> > (all seems to work if I remove -Tdjgpp-x.djl from specs). Anyway
> > problem like:
> > All my C++ programs crashes and GDB shows nonsense
> > when I'm trying to debug this problem. All worked Ok with
> > gcc-2.95.X
> > is too serious to be simply ignored.
>
> Sorry, I don't understand: is the built-in script _compatible_ with
> GCC 3.0, or is it _incompatible_? If it is compatible, how come the
> programs crash?
Perhaps we should return to this question:
Builtin script from binutils-2.11.2 is compatible with gcc-3.0.X, but it's
not so with the builtin script from binutils-2.11. I haven't verified
current CVS sources (2.11.90) of binutils though.
Anyway I think we'll find enough users who will not read instructions
and will try to use binutils-2.11 or earlier versions:
- with 2.7, 2.8 and 2.9 one will get assembler or linker errors. It's not
difficult to diagnose remotelly and
- with 2.10.X , 2.11 we'll get C++ applications crashing unless linker
script compatible with gcc-3.0.X will be used. 2.10 may have
other problems, but linker or assembler errors are easier to
diagnose remotelly rather than crashes
- with 2.11.2 all should be Ok
As result I suggest to include linker script from 2.11.2 in gcc301b.zip to
avoid problems with binutils-2.11 similary as I did with gcc30b.zip
which now is in v2gnu/alphas. As this is in gcc version specific
directory it's not dangerous to drop it at any time in future
simultanously with modifying specs not to use linker script supplied
with gcc
I still think that it's best to keep linker script identical with one from
latest DJGPP release of binutils in gcc binary archive for some time
(perhaps not very long).
Andris
- Raw text -