From: Andreas Jaeger <aj@suse.de>
To: "H . J . Lu" <hjl@lucon.org>
Cc: GNU C Library <libc-alpha@sources.redhat.com>, linux-mips@oss.sgi.com
Subject: Re: PATCH: Fix <ldsodefs.h> for Linux/mips
Date: Wed, 06 Feb 2002 23:48:42 +0100 [thread overview]
Message-ID: <u8r8nyxm45.fsf@gromit.moeb> (raw)
In-Reply-To: <20020206133113.A29718@lucon.org> ("H . J . Lu"'s message of "Wed, 6 Feb 2002 13:31:13 -0800")
Thanks, I've committed this,
Andreas
"H . J . Lu" <hjl@lucon.org> writes:
> We have been using the wrong <ldsodefs.h> for Linux/mips. Here is a
> patch.
>
>
> H.J.
> ----
> 2002-02-06 H.J. Lu <hjl@gnu.org>
>
> * sysdeps/mips/elf/ldsodefs.h: Make sure the right <ldsodefs.h>
> is included.
>
> --- sysdeps/mips/elf/ldsodefs.h.mips Sat Jul 7 16:46:05 2001
> +++ sysdeps/mips/elf/ldsodefs.h Wed Feb 6 13:25:17 2002
> @@ -22,4 +22,4 @@
>
> #define DL_RO_DYN_SECTION 1
>
> -#include <sysdeps/generic/ldsodefs.h>
> +#include_next <ldsodefs.h>
>
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
prev parent reply other threads:[~2002-02-06 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 21:31 PATCH: Fix <ldsodefs.h> for Linux/mips H . J . Lu
2002-02-06 22:48 ` Andreas Jaeger [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=u8r8nyxm45.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=hjl@lucon.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-mips@oss.sgi.com \
/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