From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: David Ford <david@linux.com>
Cc: devfs@oss.sgi.com, rgooch@atnf.csiro.au,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] devfsd, compiling on glibc22x
Date: Sun, 28 Jan 2001 07:53:12 +0100 [thread overview]
Message-ID: <3A73C1D8.578AEEE@wanadoo.fr> (raw)
In-Reply-To: <3A7383B2.19DDD006@linux.com>
David Ford wrote:
>
> This patch is simple, defines RTLD_NEXT if not previously defined.
>
> --- devfsd.c.orig Sat Jan 27 18:14:19 2001
> +++ devfsd.c Sat Jan 27 18:15:46 2001
> @@ -165,6 +165,7 @@
> Last updated by Richard Gooch 3-JUL-2000: Added "-C
> /etc/modules.devfs"
> when calling modprobe(8). Fail if a configuration line has EXECUTE
> modprobe.
>
> + Updated by David Ford 27-JAN-2001: Added RTLD_NEXT define
>
> */
> #include <unistd.h>
> @@ -221,6 +222,10 @@
> #define AC_MKNEWCOMPAT 8
> #define AC_RMOLDCOMPAT 9
> #define AC_RMNEWCOMPAT 10
> +
> +#ifndef RTLD_NEXT
> +# define RTLD_NEXT ((void *) -1l)
> +#endif
>
> struct permissions_type
> {
for me :
make CFLAGS='-O2 -I. -D_GNU_SOURCE'
compiles without any patch. is it correct ?
--
------------------------------------------------
Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-28 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 2:28 [PATCH] devfsd, compiling on glibc22x David Ford
2001-01-28 6:53 ` Pierre Rousselet [this message]
2001-01-28 7:27 ` Ulrich Drepper
2001-01-28 10:09 ` David Ford
2001-01-29 2:19 ` Albert D. Cahalan
2001-02-05 6:31 ` Richard Gooch
2001-02-05 6:51 ` Ulrich Drepper
2001-02-05 7:01 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 15:56 Douglas Gilbert
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=3A73C1D8.578AEEE@wanadoo.fr \
--to=pierre.rousselet@wanadoo.fr \
--cc=david@linux.com \
--cc=devfs@oss.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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.