Re: new egcs debian packages -- testers and porters needed
John Lapeyre writes:
> On Fri, 14 Aug 1998 jdassen@wi.leidenuniv.nl wrote:
>
> jdasse>We don't have a problem with packages requiring differenent versions of
> jdasse>libstdc++ to run. We have problems if we want to have a setup in which we
> jdasse>can compile against different versions of libstdc++.
>
> I can run packages built with g++272 and g++ on the same system.
> But everytime I want to rebuild one, I have to switch the -dev packages.
> (some packages only compile with one or the other) So we are already in
> this situation. Since the libraries have different version numbers, there
> is no problem at runtime. I assume the only problem with the -dev
> packages is headers occupying the same place. Could we just put them in
> subdirs under /usr/include and require compiling with appropriate -I flags
> ? I'm not asking for one more compiler, just if there is ever going to be
> a time when we don't want at least two c++ compilers.
the libapi patch (applied in the egcs-1.1 packages) put the C++
headers in a version specific directory which gets included in the
search path by default. The other problem will be, that you have to
reinstall the egcs compiler as well... I don't think that's a good
solution. Currently the pre egcs-1.1 shows no regressions (to
egcs-1.0.3) on the ix86 architecture and can be used for all cases
where gc272 was used and egcs-1.0.3 didn't work (AFAIK). If this
prooves true, then there would be no need for such a configuration (as
Ray already pointed out).
Matthias
Reply to: