From: Grant Grundler <grundler@parisc-linux.org>
To: linux-ia64@vger.kernel.org
Subject: man clone on ia64 incomplete/wrong
Date: Fri, 29 Dec 2006 17:55:16 +0000 [thread overview]
Message-ID: <20061229175516.GA32589@colo.lackof.org> (raw)
Hi,
Helge Deller recently posted a Linux Test Project test failure
on the parisc-linux mailing list:
http://lists.parisc-linux.org/pipermail/parisc-linux/2006-December/031030.html
I took the code snippet he posted and tried to compile/run that
on x86 (no problems) and ia64 (undefined reference to `clone').
This is a "known problem". Email thread from 2003:
http://marc.theaimsgroup.com/?l=linux-ia64&m\x105778639326638&w=2
The LTP test case was fixed but not the clone man page.
When I was surprised by the link error, first thing I did was
"man clone" and got the impression there was a bug in ia64 user
space support. But Helge spared me the digging around and pointed
me at the clone2 code in the original test case.
Anyone working for Intel/HP/Hitachi/SGI/et al care enough to fix
the man page as well?
This would be a good "student" or "intern" task if someone is
looking to contribute to linux without having to know too much.
Basically just need to add a reference to "clone2" and indicate
which architectures do not support clone(2).
thanks,
grant
reply other threads:[~2006-12-29 17:55 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=20061229175516.GA32589@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-ia64@vger.kernel.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