From: Wol's lists <antlists@youngman.org.uk>
To: Michael Fritscher <michael@fritscher.net>, linux-raid@vger.kernel.org
Subject: Re: [OT] C programming problem
Date: Wed, 7 Feb 2018 20:22:01 +0000 [thread overview]
Message-ID: <7b976e5c-cb0a-ded2-e812-fd3cdddfe864@youngman.org.uk> (raw)
In-Reply-To: <46a82977-bb58-8ac5-bbde-ba027339f31e@fritscher.net>
On 07/02/18 20:00, Michael Fritscher wrote:
> Hello,
>
>> main.c:20:5: warning: incompatible implicit declaration of built-in
>> function ‘memset’ [enabled by default]
>> memset( &array, 0, blocks * sizeof(int) );
>
> at least my compiler says something about
>> a.c:21:5: note: include ‘<string.h>’ or provide a declaration of ‘memset’
>
> And yes, the first recipe does indeed help :-P
>
Thank you both! Perfect!
I think actually stdlib had fixed the malloc problem, but I missed it
because the memset problem was still there.
Cheers,
Wol
next prev parent reply other threads:[~2018-02-07 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 19:46 [OT] C programming problem Wol's lists
2018-02-07 20:00 ` Linus Lüssing
2018-02-07 20:00 ` Michael Fritscher
2018-02-07 20:22 ` Wol's lists [this message]
2018-02-07 22:43 ` Phil Turmel
2018-02-07 23:32 ` Wol's lists
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=7b976e5c-cb0a-ded2-e812-fd3cdddfe864@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=michael@fritscher.net \
/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