Mail Archives: djgpp-workers/2001/06/25/02:32:59
On Fri, 22 Jun 2001 lauras AT softhome DOT net wrote:
>
> > Many of poeple who will download gcc-3.0 will not read carefully
> > instructions. It sad of course but it is so. So many can miss note
> > that they should update djdev203.zip. If I'll provide linker script with
> > GCC, we'll avoid related trouble as it's sure GCC will use correct
> > linker script (it will simply not look for lib/djgpp.djl at all)
>
> We must have been talking about different solutions - as I see it, both
> updated djdev203.zip and new gcc30b.zip should provide the updated
> lib/djgpp.djl at the same location. This way it doesn't matter which file
> overwrites the other one. Does it sound better now?
I suggested to temporary change name of linker script and supply the new
one with GCC-3.0. So I make sure the incompatible one from djdev203.zip
will never be used with these binaries of GCC-3.0. As result there is no
need to update djdev203.zip now and there will be no danger of unpacking
archives in wrong order. May be even djdev202.zip (but not
djdev20[01].zip) could be used, but I haven't tested that.
The result of using old djgpp.djl will cause any C++ program which uses
libstdc++ crash and it will be rather difficult for normal user to figure
out what happened. It took initially also for me some time to understand
what happens and how to fix it. If there will be some possibility to be able to
use djgpp.djl from djdev203.zip due to some installation problem, there
will be somebody who will do that (also if we describe it in readme).
As result we'll have to answer related questions why amost every C++
program crashes for somebody
I think we should make binary package more "foolprof" if possible. That
was main intention of hack I used.
Who may have problems with this way:
I guess only those who uses modified linker scripts, but they shall have
to update their scripts anyway. Also I have seen some packages which uses
modified djgpp.djl, but they also should be updated even without such hack
> In another mail you've said that GCC 3.0.1 will be released shortly.
> FYI, everybody not on GCC mailing list - it should happen on 2001.08.01.
I know. Also there are other problems partially not related to GCC itself:
- linker not always demangles function names in error messages
- .comment section in object files cofuses dxegen, as result it doesn't
work unless patched
- allegro-3.9.36 built with default option crashes. It works after
removing -fomit-frame-pointer from options
I have have uploaded gcc-3.0 archives to ftp.delorie.com in previous
Friday. And I also will have no time to do much with gcc in nearest 2
weeks. Maybe it would be best to put archives in v2gnu/betas if
v2gnu is not acceptable. Especially if we may have other minor version
after slightly more than a month
Andris
- Raw text -