mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: drepper@cygnus.com
Cc: pierre.rousselet@wanadoo.fr (Pierre Rousselet),
	david@linux.com (David Ford),
	devfs@oss.sgi.com, rgooch@atnf.csiro.au,
	linux-kernel@vger.kernel.org (LKML)
Subject: Re: [PATCH] devfsd, compiling on glibc22x
Date: Sun, 28 Jan 2001 21:19:12 -0500 (EST)	[thread overview]
Message-ID: <200101290219.f0T2JCF439854@saturn.cs.uml.edu> (raw)
In-Reply-To: <m3wvbgnnk3.fsf@otr.mynet.cygnus.com> from "Ulrich Drepper" at Jan 27, 2001 11:27:56 PM

Ulrich Drepper writes:
> 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.

This isn't a HURD feature.
This isn't even a C library feature.
This is a Linux feature.

So the _GNU_SOURCE thing is just plain wrong. Quit trying to
rename the OS.

Since there are so many standards to choose from, putting all features
into the default would be most obvious. Else what, pure C89 maybe?
Dang new-fangled standards might break something. Normal UNIX systems
don't make developers jump through hoops to get access to stuff; they
instead provide clean namespaces upon request.


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

  parent reply	other threads:[~2001-01-29  2:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28  2:28 David Ford
2001-01-28  6:53 ` Pierre Rousselet
2001-01-28  7:27   ` Ulrich Drepper
2001-01-28 10:09     ` David Ford
2001-01-29  2:19     ` Albert D. Cahalan [this message]
2001-02-05  6:31   ` Richard Gooch
2001-02-05  6:51     ` Ulrich Drepper
2001-02-05  7:01     ` Richard Gooch
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=200101290219.f0T2JCF439854@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=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
all inboxes | Powered by JetHome®