From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Build problem smbfs/file.c
Date: Sun, 14 Mar 2004 14:15:15 -0000 [thread overview]
Message-ID: <405468F3.13851.28874B86@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0403131452150.2749-100000@cola.local>
> > PARANOIA("%s/%s validation failed, error=%zd\n"
> >
> > Ummm. I removed the `z' from error=%zd\n" - it appears to be rogue,
> > but what do I know ;)
>
> I think someone meant to change my %d into a %Zd, like in smb_file_read.
> Or not, since my gcc's understand them both.
>
> Compiler version?
I installed the recommended kernel GCC as per the docs:
[root@Linux233 linux-2.6.1]# gcc -v
Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-
gnu/2.95.3/specs
gcc version 2.95.3 20010315 (release)
OK, after some research it is a GCC problem - but I need to ask why
this is now become a problem.
Googling, Andrew Morton pulled this up in the lkml found here:
http://lkml.org/lkml/2003/7/7/225
Now, I am a bit worried if the lower case version `z' is to be used,
that it will be a bit of a problem if there are lots of files using
it.
Also, although GCC reports this as a warning, it also seems to say "I
don't know what this is, so am ignoring it" sort of thing?
Or am I PARANOIA...
Thanks,
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next prev parent reply other threads:[~2004-03-14 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 13:29 Build problem smbfs/file.c Nick Warne
2004-03-13 14:10 ` Urban Widmark
2004-03-14 14:15 ` Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-13 14:05 Nick Warne
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=405468F3.13851.28874B86@localhost \
--to=nick@ukfsn.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.