Re: new egcs debian packages -- testers and porters needed
John Lapeyre writes:
>
> When might a newer egcs become part of the distribution? Is it
> possible to put a snaphot in slink under yet another name ?
I would like to wait until the egcs-1.1 prerelease. I am uncertain if
another name will be necessary. C, Fortran 77 and Objective-C should
be compatible, Pascal is new. C++ might be a problem. The interface to
libstdc++ changed and it's not possible to compile and link files with
egcs-1.1, which want to use the old libstdc++2.8.
Is it really necessary to keep three different compiler versions?
(I see, that's necessary to keep gcc27 to compile the kernel, but this
will change with 2.2 very soon (?))
We will have this problem again, if a new libstdc++ will be integrated
in egcs-1.2 ...
> I have one package that only compiles under g++ from 2.7, or from the
> egcc snapshot in experiemental , but not from hamm's standard g++ . I
> have another that will only compile under the one from experimental .
> There may be others as well, I haven't had time yet to check.
Did you check the one from master.debian.org:~doko/ ? This should be
the newest one. If this one doesn`t work as well, you have a last
chance to recompile this version with the Haifa scheduler enabled
(--enable-haifa for configure). If this fails as well, you should
submit a bug report to egcs-bugs@cygnus.com.
Technically, it's possible to build egcs packages which can coexist.
The "only" thing that must be done is to separate out the info files
in separate packages which conflict with each other. man pages and
compiler drivers could be alternatives. (and as long as you use the
"normal" options you can call other compiler versions from the same
driver i.e. gcc -V 2.91.53). But is this something we really want?
Well, to switch the default C compiler for slink could be just another
release goal ;-)
Reply to: