Jack Howarth <[EMAIL PROTECTED]> writes:
>I think the primary problem debian will have with gcc 3.2 (or
> 3.1.1 for that matter) is dealing with rebuilding glibc under it.
> Because the gcc 3.1 fixed a bug relating to incorrectly linking in
> libgcc symbols into binaries, glibc trunk and glibc
Package: g++-3.0
Version: 1:3.0.4-12
Severity: normal
Alternatives for /usr/bin/c++ are not created/updated when installing g++-3.0.
-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux lappa 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i586
Locale: LANG=C, LC_CTYPE=C
Versions o
Martin,
I think the primary problem debian will have with gcc 3.2 (or
3.1.1 for that matter) is dealing with rebuilding glibc under it.
Because the gcc 3.1 fixed a bug relating to incorrectly linking in
libgcc symbols into binaries, glibc trunk and glibc-2-2-branch have
fixes to address this thr
We can help YOU to develop a new or existing
website or even provide cheaper hosting and domain names.
Remove instructions below.
We are a UK based company who can offer YOU our
considerable experience and expertise in the field of website design, eCommerce
development, all types of web h
When g++ 3.2 becomes the next Debian compiler, it will be necessary to
recompile a lot of packages. Also, it will be necessary to have the
old binary packages, and their shared libraries, coexist.
Is there a specific plan to implement this coexistence? I can think of
the following strategies:
- d
5 matches
Mail list logo