public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: Pierre Rousselet <pierre.rousselet@wanadoo.fr>,
	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 10:09:44 +0000	[thread overview]
Message-ID: <3A73EFE8.3FB7BEC0@linux.com> (raw)
In-Reply-To: <3A7383B2.19DDD006@linux.com> <3A73C1D8.578AEEE@wanadoo.fr> <m3wvbgnnk3.fsf@otr.mynet.cygnus.com>

Ulrich Drepper wrote:

> Pierre Rousselet <pierre.rousselet@wanadoo.fr> writes:
>
> > for me :
> > make CFLAGS='-O2 -I. -D_GNU_SOURCE'
> > compiles without any patch. is it correct ?
>
> Yes.  RTLD_NEXT is not in any standard, it's an extension available
> via -D_GNU_SOURCE.

Ok, how about we all tag Richard until he adds that to the makefile?  :)

-d

--
  There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
  The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum



-
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/

  reply	other threads:[~2001-01-28 10:10 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
2001-01-28  7:27   ` Ulrich Drepper
2001-01-28 10:09     ` David Ford [this message]
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=3A73EFE8.3FB7BEC0@linux.com \
    --to=david@linux.com \
    --cc=devfs@oss.sgi.com \
    --cc=drepper@cygnus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.rousselet@wanadoo.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox