All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: jarmo kettunen <oh1mrr@nic.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: My previous question about iwlib
Date: Thu, 29 Nov 2001 19:02:55 MET-1	[thread overview]
Message-ID: <A9497EC5D6C@vcnet.vc.cvut.cz> (raw)

On 29 Nov 01 at 16:49, jarmo kettunen wrote:
> 
> gcc -O2 -Wall -DGLIBC_HEADERS  -c iwlib.c
> In file included from iwlib.c:11:
> iwlib.h:91:8: warning: extra tokens at end of #endif directive
> iwlib.h:96:8: warning: extra tokens at end of #endif directive
> In file included from iwlib.h:42,
>                  from iwlib.c:11:
> /usr/include/linux/in.h:25: conflicting types for `IPPROTO_IP'
> /usr/include/netinet/in.h:32: previous declaration of `IPPROTO_IP'

iwlib.h (or any other userspace app) must not include <linux/*> and 
<asm/*> files. If it needs access to them for accessing ioctl API
(or anything else), maintainer must create stripped-down copy of
these headers, and distribute them with app - which is btw only
correct way, as otherwise you cannot create userspace app which
will support more than one API version (and iw used couple
of incompatible APIs in the past...).
                                    Best regards,
                                            Petr Vandrovec
                                            vandrove@vc.cvut.cz
                                            

             reply	other threads:[~2001-11-29 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 19:02 Petr Vandrovec [this message]
2001-11-30  5:35 ` Vs: Re: My previous question about iwlib Jarmo
  -- strict thread matches above, loose matches on Subject: below --
2001-11-29 14:49 jarmo kettunen

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=A9497EC5D6C@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oh1mrr@nic.fi \
    /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.