From: Ian Lance Taylor <ian@zembu.com>
To: jj@sunsite.ms.mff.cuni.cz
Cc: binutils@sourceware.cygnus.com
Subject: Re: [PATCH] Run ld-shared and ld-vers checks on sparc*linux
Date: Mon, 09 Aug 1999 08:00:00 -0000 [thread overview]
Message-ID: <19990809145945.30152.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990809112559.D18264@mff.cuni.cz>
Date: Mon, 9 Aug 1999 11:25:59 +0200
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
I don't wonder why the checks which failed for hjl did not fail for me
(patch below).
The only test which fails then is the load offset check which might be
cured in glibc 2.1.2 and 2.1.90 as it dies on phdrs outside of any mapped
segment, but I haven't checked yet.
1999-08-09 Jakub Jelinek <jj@ultra.linux.cz>
* ld-elfvers/vers.exp: Add sparc*-*-linux*.
* ld-shared/shared.exp: Likewise.
Thanks, I checked in this patch.
The load offset test is indeed expected to fail on glibc before some
2.1 version. I think the fix was checked in on May 6.
Ian
prev parent reply other threads:[~1999-08-09 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-09 2:25 Jakub Jelinek
1999-08-09 8:00 ` Ian Lance Taylor [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=19990809145945.30152.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).