Gordon Sadler <[EMAIL PROTECTED]> writes:
> Basically, "glibc will have to be updated for GCC 3.0"
It will have to be updated anyway. There are some serious problems
with exception handling. Recompiling glibc will result in a libc.so
that doesn't export __frame_start_for. This means that excep
Gordon Sadler <[EMAIL PROTECTED]> writes:
> Basically, "glibc will have to be updated for GCC 3.0"
It will have to be updated anyway. There are some serious problems
with exception handling. Recompiling glibc will result in a libc.so
that doesn't export __frame_start_for. This means that exce
On Mon, Jun 04, 2001 at 02:07:41AM -0400, Ben Collins wrote:
> On Sun, Jun 03, 2001 at 04:19:21PM -0500, Gordon Sadler wrote:
> > I've conducted some tests building glibc-2.2.3+nis patch with gcc-2.95-4
> > from Debian unstable and some local builds of gcc-3.0. After reading
> > some archives of th
On Sun, Jun 03, 2001 at 04:19:21PM -0500, Gordon Sadler wrote:
> I've conducted some tests building glibc-2.2.3+nis patch with gcc-2.95-4
> from Debian unstable and some local builds of gcc-3.0. After reading
> some archives of the glibc mailing lists, I discovered some oddities on
> the build proc
On Mon, Jun 04, 2001 at 02:07:41AM -0400, Ben Collins wrote:
> On Sun, Jun 03, 2001 at 04:19:21PM -0500, Gordon Sadler wrote:
> > I've conducted some tests building glibc-2.2.3+nis patch with gcc-2.95-4
> > from Debian unstable and some local builds of gcc-3.0. After reading
> > some archives of t
On Sun, Jun 03, 2001 at 04:19:21PM -0500, Gordon Sadler wrote:
> I've conducted some tests building glibc-2.2.3+nis patch with gcc-2.95-4
> from Debian unstable and some local builds of gcc-3.0. After reading
> some archives of the glibc mailing lists, I discovered some oddities on
> the build pro
I've conducted some tests building glibc-2.2.3+nis patch with gcc-2.95-4
from Debian unstable and some local builds of gcc-3.0. After reading
some archives of the glibc mailing lists, I discovered some oddities on
the build process.
glibc uses `gcc -print-file-name=cpp` while building parts of the
I've conducted some tests building glibc-2.2.3+nis patch with gcc-2.95-4
from Debian unstable and some local builds of gcc-3.0. After reading
some archives of the glibc mailing lists, I discovered some oddities on
the build process.
glibc uses `gcc -print-file-name=cpp` while building parts of th
8 matches
Mail list logo