From: Christoph Bussenius <busseniu@cip.physik.uni-muenchen.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: dereferencing pointer to incomplete type
Date: Wed, 16 Jun 2004 22:14:13 +0200 [thread overview]
Message-ID: <20040616201413.GG6157@opaque> (raw)
In-Reply-To: <016001c453dc$08d6ec70$d3113b80@yoursgz3xpngo4>
On Wed, Jun 16, 2004 at 03:56:37PM -0400, Anshuman S. Rawat wrote:
> Arping.xs:153: dereferencing pointer to incomplete type
> make: *** [Arping.o] Error 1
>
> memcpy(enet_src, src_mac->ether_addr_octet,6);
...
> struct ether_addr
> {
> u_char ether_addr_octet[6];
> };
Hi, I think you should define that struct _before_ you use it. This
error is exactly what you get when you define it later.
HTH,
Christoph
--
``There's no dark side of the moon, really
Matter of fact, it's all dark''
--Pink Floyd
next prev parent reply other threads:[~2004-06-16 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 19:56 dereferencing pointer to incomplete type Anshuman S. Rawat
2004-06-16 20:14 ` Christoph Bussenius [this message]
2004-06-16 20:13 ` Anshuman S. Rawat
2004-06-16 21:04 ` Glynn Clements
2004-06-16 22:01 ` Micha Feigin
2004-06-16 23:02 ` Anshuman S. Rawat
2004-06-17 4:21 ` Micha Feigin
2004-06-17 8:46 ` Christoph Bussenius
2004-06-17 10:24 ` Glynn Clements
2004-06-17 17:03 ` Micha Feigin
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=20040616201413.GG6157@opaque \
--to=busseniu@cip.physik.uni-muenchen.de \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).