From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Justin Carlson <carlson@sibyte.com>, linux-mips@oss.sgi.com
Subject: Re: GDB 5 for mips-linux/Shared library loading with new binutils/glibc
Date: Sat, 27 Jan 2001 11:01:06 -0800 [thread overview]
Message-ID: <20010127110106.F867@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010127084850.29150E-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Sat, Jan 27, 2001 at 09:01:47AM +0100
On Sat, Jan 27, 2001 at 09:01:47AM +0100, Maciej W. Rozycki wrote:
> I've contributed all patches I've written myself. Unfortunately, most of
> the code needed for gdb 5.0 to run on MIPS was taken from the 4.x CVS at
> oss.sgi.com. As such it is required all authors of patches have to have
> their copyright assigned to FSF before committing them to the gdb CVS.
>
> I've asked people to resolve ownership of the code here some time ago,
> but it seems nobody is really interested in getting this code into
> official gdb, sigh...
The only people who have contributed amounts of code large enough for the
FSF to requires an assignment are David Miller (davem@redhat.com) and
myself. I've already signed an assignment with the FSF and I'm also sure
David has. I btw. cannot remember having seen any mail from you regarding
copyright assignments of GDB.
> > However, ld.so seems to know nothing about relocating shared library with a
> > non-zero shared library base address, which causes dynamically linked
> > stuff to crash spectacularly.
>
> Does it? Please provide more details. All of my system (linux 2.4.0,
> glibc 2.2.1) is dynamically linked and it works fine.
I don't know what you look at - ld.so fails to handle libraries which are
not linked to 0x5fffe000 ...
> > binutils we're using is from CVS as of about Dec 17th. Glibc is also a
> > snapshot from about the same time.
>
> Glibc should be fine as is although you might consider getting the 2.2.1
> release. You may try to check if patches from my binutils package (also
> available at the mentioned site) solve certain or all of your problems.
> The patches have been proposed for an inclusion in the upcoming binutils
> 2.11 release -- I hope they will finally get there.
Ulf?
Ralf
next prev parent reply other threads:[~2001-01-28 2:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 1:40 GDB 5 for mips-linux/Shared library loading with new binutils/glibc Justin Carlson
2001-01-27 8:01 ` Maciej W. Rozycki
2001-01-27 19:01 ` Ralf Baechle [this message]
2001-01-28 11:55 ` Andreas Jaeger
2001-02-09 0:31 ` Kevin D. Kissell
2001-02-09 0:31 ` Kevin D. Kissell
2001-02-09 2:00 ` Ralf Baechle
2001-02-09 2:00 ` Ralf Baechle
2001-01-29 15:34 ` Maciej W. Rozycki
2001-01-27 19:11 ` Ralf Baechle
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=20010127110106.F867@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=carlson@sibyte.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox