From: Andreas Jaeger <aj@arthur.rhein-neckar.de>
To: Ulf Carlsson <ulfc@bun.falkenberg.se>
Cc: Alex deVries <adevries@engsoc.carleton.ca>,
SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: glibc 2.1
Date: 15 Apr 1999 16:53:21 +0200 [thread overview]
Message-ID: <u84smi7x5q.fsf@arthur.rhein-neckar.de> (raw)
In-Reply-To: Ulf Carlsson's message of "Thu, 15 Apr 1999 09:10:41 +0200"
>>>>> Ulf Carlsson writes:
Ulf> Hi Alex,
>> Has anyone started work on glibc 2.1 for mips{eb|el}? I'd like to start
>> on a port of Red Hat 6.0 ofor mipseb and mipsel.
Ulf> I tried to do this some time ago, but I never finished it. I have heard that
Ulf> Ralf has done some work here, maybe he can share his work with us. I've tried
Ulf> to persuade him to do this before without any success. I'd like to have these
Ulf> patches as well so that I may continue working with the D word. :-)
Ulf> Well, if we can't get these patches I'd like to help you with the porting work
Ulf> for glibc 2.1.
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.
- the system (mips) dependend part of the dynamic linker has to be
updated.
- 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.
Andreas
--
Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de
next prev parent reply other threads:[~1999-04-15 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 1:39 glibc 2.1 Alex deVries
1999-04-15 7:10 ` Ulf Carlsson
1999-04-15 14:53 ` Andreas Jaeger [this message]
1999-04-15 22:07 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2013-11-21 18:25 Michael Quicquaro
[not found] ` <CAAD-K951DjgTWDXBKACxyimP6j_vM-XN7hh8pFqfU217-6J3bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-22 9:42 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B01A975AA5-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-22 15:57 ` Michael Quicquaro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u84smi7x5q.fsf@arthur.rhein-neckar.de \
--to=aj@arthur.rhein-neckar.de \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ulfc@bun.falkenberg.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.