On Friday 16 August 2002 15:51, Matthew Wilcox wrote:
> -
> The Debian GCC 3.2 Transition Plan
>
> This is a proposal. You will be notified when this is a real plan
>
Nice plan all in all, although I am going to hate the new package names. Some
people talked about av
#include
* Allan Sandfeld Jensen [Mon, Aug 19 2002, 02:58:06PM]:
> libraries are placed under /usr/lib/g++2.95 and the new ones under
> /usr/lib/g++3.1. The defaults are symbolic linked from /usr/lib. We can
> either hack ld.so to search the correct path (using some g++ calling cards)
> or reco
On Saturday 17 August 2002 19:28, you wrote:
>
> I am currently doing this experiment on s390 without uploading of course. I
> have grepped the build logs of about 4000 packages that I have access to
> for g++|c++ and about 900 packages qualified. I am currently rebuilding
> these packages with gcc
Package: g++
Version: 2:2.95.4-14
Severity: normal
g++ doesnt handle specifying a default argument to a specialized
template function which is done like
template
void test(int j = 0);
template <>
void test<1>(int j);
calling test<1>() should work, but instead g++ complains there is no
matching
On Friday 16 August 2002 21:47, Martin v. Loewis wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > How would this work? Would those using gcc-2.95 software have to set an
> > rpath or $LD_LIBRARY_PATH to take advantage of the compat libs? If so,
> > it hardly seems worth the effort; manual
6 matches
Mail list logo
