From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] sscanf() broken on ia64
Date: Thu, 18 Oct 2001 23:03:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805371@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805369@msgid-missing>
On Thu, 18 Oct 2001 16:50:28 -0500,
"David J. Morse" <david.morse@onebox.com> wrote:
>I'm having a problem with sscanf() on IA-64; it seems to be able to parse
>a string into arguments correctly when whitespace is the delimiter, but
>not "."!
lib/vsprintf.c::vscanf had a bug in handling non-format characters. It
was corrected in 2.4.13-pre3. Try copying lib/vsprintf.c from a
current Linus kernel into your IA64 kernel.
>/* Declare what kind of code we want from the header files */
>#define __KERNEL__ /* We're part of the kernel */
>#define MODULE /* Not a permanent part, though. */
>
>/* Standard headers for LKMs */
>#include <linux/modversions.h>
>#include <linux/module.h>
Unrelated to the scanf problem. Please do not #define those symbols
nor include modversions.h in modules, even sample ones, the symbols and
include should be handled via the command line. That code will break
in kernel 2.5 with my new kernel build system.
prev parent reply other threads:[~2001-10-18 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 21:50 [Linux-ia64] sscanf() broken on ia64 David J. Morse
2001-10-18 23:03 ` Keith Owens [this message]
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=marc-linux-ia64-105590698805371@msgid-missing \
--to=kaos@ocs.com.au \
--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