From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: FWD: [PATCH] glibc fix for /lib/ld.so.1 (with attachments this time)
Date: Wed, 26 Mar 2003 23:12:40 -0500 [thread overview]
Message-ID: <20030327041240.GB18299@systemhalted> (raw)
In-Reply-To: <1048737294.8659.55.camel@beavis.ybsoft.com>
Ryan,
> Finally tracked down the glibc problem (with help from tausq and others
> :)). I have attached the changelog entry, and the dpatch. I am
> assuming you will push it upstream Carlos?
Looks good. It looks like the only real way to solve this since ia64 and
powerpc64 have similar entry.h macro's.
> This is why the ENTRY_POINT macro is uglier than really necessary.
Not any uglier than the ia64 and powerpc64 macro's that do similar
things ;)
Thank you very much for working on this! :)
c.
prev parent reply other threads:[~2003-03-27 4:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 3:54 [parisc-linux] FWD: [PATCH] glibc fix for /lib/ld.so.1 (with attachments this time) Ryan Bradetich
2003-03-27 4:12 ` Carlos O'Donell [this message]
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=20030327041240.GB18299@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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