public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cquike at arcor dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29147] getconf: Wrong values for symbolic constants defined in limits.h
Date: Sat, 14 May 2022 23:12:50 +0000	[thread overview]
Message-ID: <bug-29147-131-EQjjTLTvmg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29147-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29147

--- Comment #1 from cquike at arcor dot de ---
BTW, the patch is not to be taken verbatim. Since for those variables there is
no "call" to get the value, some of the code should be rewritten in order not
to be confusing in terms of variable names. A quick possible solution is to
change all appearances of "call" by "source" (sed -i 's/call/source/'
getconf.c).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-05-14 23:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 23:05 [Bug libc/29147] New: " cquike at arcor dot de
2022-05-14 23:05 ` [Bug libc/29147] getconf: " cquike at arcor dot de
2022-05-14 23:12 ` cquike at arcor dot de [this message]
2022-05-18 19:47 ` adhemerval.zanella at linaro dot org
2022-05-23 20:02 ` cquike at arcor dot de
2022-05-23 20:47 ` adhemerval.zanella at linaro dot org
2022-05-24  0:57 ` cquike at arcor dot de
2022-05-24  7:49 ` schwab@linux-m68k.org
2022-05-26 17:22 ` adhemerval.zanella at linaro dot org
2022-05-27 14:31 ` adhemerval.zanella at linaro dot org
2022-07-29 22:10 ` cquike at arcor dot de

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=bug-29147-131-EQjjTLTvmg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).