From: Nix <nix@esperi.demon.co.uk>
To: Cong <vo.chi.cong@is.titech.ac.jp>
Cc: gcc-help@gcc.gnu.org
Subject: Re: how to get the number of CPUs?
Date: Sat, 13 Jul 2002 08:00:00 -0000 [thread overview]
Message-ID: <87adovr90l.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20020707.132410.39168269.vo.chi.cong@is.titech.ac.jp>
On Sun, 7 Jul 2002, Cong yowled:
> Thank you, your code works for me!
>
> But, when I do man sysconf on Linux, it show no infomation
> about _SC_NPROCESSORS_CONF as manpage on Solaris do. However, looking
> at <unistd.h>, they're there!
The manpage is not the canonical information source for the GNU C
library.
Try `info libc processor resources', or
`info libc --index-search=_SC_NPROCESSORS_CONF'.
--
`There's something satisfying about killing JWZ over and over again.'
-- 1i, personal communication
next prev parent reply other threads:[~2002-07-13 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D6C01F7@whale.softwire.co.uk>
2002-07-04 5:52 ` Rupert Wood
2002-07-06 21:24 ` Cong
2002-07-13 8:00 ` Nix [this message]
2002-07-04 13:11 Dockeen
[not found] <1025766825.11142.ezmlm@gcc.gnu.org>
2002-07-04 4:45 ` Cong
2002-07-04 5:30 ` Bharathi S
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=87adovr90l.fsf@amaterasu.srvr.nix \
--to=nix@esperi.demon.co.uk \
--cc=gcc-help@gcc.gnu.org \
--cc=vo.chi.cong@is.titech.ac.jp \
/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).