public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] testsuite: stdlib/isomac.c: fix REQUIREMENTS
Date: Mon,  8 May 2023 14:00:57 +0000 (GMT)	[thread overview]
Message-ID: <20230508140057.C80603858D32@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=cea74a4a24c36202309e8254f1f938e2166488f3

commit cea74a4a24c36202309e8254f1f938e2166488f3
Author: наб <nabijaczleweli@nabijaczleweli.xyz>
Date:   Thu May 4 22:25:57 2023 +0200

    testsuite: stdlib/isomac.c: fix REQUIREMENTS
    
    All of the mentioned variables are gone. gcc is just the default and
    argv[1] can be used instead. /usr/include isn't hard-coded and you can
    pass argv[2] with -I... to adjust.
    
    Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>

Diff:
---
 stdlib/isomac.c | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/stdlib/isomac.c b/stdlib/isomac.c
index 3a6009d988..a371bb2593 100644
--- a/stdlib/isomac.c
+++ b/stdlib/isomac.c
@@ -45,14 +45,11 @@
    compiler compiles some other language than Standard C.
 
    REQUIREMENTS:
-     This program calls gcc to get the list of defined macros. If you
+     This program calls ${1-gcc} to get the list of defined macros. If you
      don't have gcc you're probably out of luck unless your compiler or
-     preprocessor has something similar to gcc's -dM option. Tune
-     PRINT_MACROS in this case. This program assumes headers are found
-     under /usr/include and that there is a writable /tmp directory.
-     Tune SYSTEM_INCLUDE if your system differs.
-     #define BROKEN_SYSTEM if system(NULL) bombs -- one more violation
-     of ISO C, by the way.
+     preprocessor has something similar to gcc's -dM option. This program
+     assumes headers are found in the default search path (pass -I... in
+     $2 if this is not the case) and that there is a writable /tmp directory.
 
    OUTPUT:
      Each header file name is printed, followed by illegal macro names

                 reply	other threads:[~2023-05-08 14:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230508140057.C80603858D32@sourceware.org \
    --to=carlos@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /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).