[Top] [All Lists]

Re: glibc 2.1

To: Andreas Jaeger <>, Ulf Carlsson <>
Subject: Re: glibc 2.1
From: Ralf Baechle <>
Date: Thu, 15 Apr 1999 15:07:18 -0700
Cc: Alex deVries <>, SGI Linux <>
In-reply-to: <>; from Andreas Jaeger on Thu, Apr 15, 1999 at 04:53:21PM +0200
References: <> <> <>
On Thu, Apr 15, 1999 at 04:53:21PM +0200, Andreas Jaeger wrote:

> At the end of last year I tried to integrate Ralf's patches into
> glibc 2.1.  A number of patches went into the glibc tree but some
> problems are still open.  Ralf can certainly better comment this from
> the mips side, I'm just a glibc developer without access to any mips
> machine who used a cross compiler:
> - glibc 2.1 needs symbol versioning but there're no binutils for mips
>   that support symbol versioning
> - there're some problems with the way glibc handles PIC which leads to 
>   problems on mips.

Fixed in my patches.

> - the system (mips) dependend part of the dynamic linker has to be
>   updated.

Done in my patches modulo debugging.

I've fixed several problems in H.J. Lu's binutils  Symbol
version is still not working and building GNU libc still results in
amazing amounts of assertion messages in bfd/elf32-mips.c; building
kernels is broken as well.

> - some minor discrepancies between the kernel headers in the official
>   kernel and the glibc headers.  Ralf and I updated most (all?) but
>   somebody should recheck this.
> IMO the first two problems to tackle is to get it running at all,
> meaning to fix the PIC problems (that's already planned by the glibc
> folks for 2.2) and the dynamic linker.  Without symbol versioning you
> loose binary compatibility with older and newer versions of glibc.
> Therefore the binutils have to be fixed to use glibc 2.1.

While that is correct for a production version we probably can temporarily
bump the major version number for development purposes and work on
both binutils and GNU binutils in parallel.

The latest versions I've worked on are GNU libc version 2.0.109 and
binutils  I've put my patches on into

Have fun ;-)


<Prev in Thread] Current Thread [Next in Thread>