linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Davide Pesavento <davidepesa@gmail.com>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: iw packaging
Date: Wed, 17 Sep 2008 23:52:46 +0200	[thread overview]
Message-ID: <1221688366.7412.13.camel@localhost> (raw)
In-Reply-To: <2da21fe50809171446y56cd5b2ctc864650be6030621@mail.gmail.com> (sfid-20080917_234700_559966_9B8DC833)

On Wed, 2008-09-17 at 23:46 +0200, Davide Pesavento wrote:
> $ make
>  GEN  version.h
>  CC   iw.o
>  CC   info.o
> info.c: In function 'print_phy_handler':
> info.c:108: error: 'NL80211_ATTR_SUPPORTED_IFTYPES' undeclared (first
> use in this function)
> info.c:108: error: (Each undeclared identifier is reported only once
> info.c:108: error: for each function it appears in.)
> make: *** [info.o] Error 1
> 
> I guess I have to build iw against >=2.6.27-rcX kernel headers, right?

Actually this one is new in wireless-testing, I have a branch you can
build against 2.6.27 but it's not very up-to-date.

Any ideas how to handle this are welcome. Should it just ship the header
file? I'd prefer not to, otoh doing it isn't really harmful because when
adding a new command clearly you need to edit iw sources.

johannes


  parent reply	other threads:[~2008-09-17 21:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 20:29 iw packaging Johannes Berg
2008-09-16 20:46 ` Stefanik Gábor
2008-09-16 20:50 ` Pavel Roskin
2008-09-16 21:11   ` Johannes Berg
2008-09-16 21:15     ` Johannes Berg
2008-09-16 21:23       ` Pavel Roskin
2008-09-16 21:38         ` Johannes Berg
2008-09-16 21:48           ` Pavel Roskin
2008-09-16 21:56             ` Johannes Berg
2008-09-16 22:14               ` Johannes Berg
2008-09-16 23:20                 ` Pavel Roskin
2008-09-17  7:30                   ` Johannes Berg
2008-09-17 10:41 ` Jochen Friedrich
2008-09-17 10:43   ` Johannes Berg
2008-09-17 11:05     ` "Adam Cécile (Le_Vert)"
2008-09-17 11:07       ` Johannes Berg
2008-09-17 11:11         ` "Adam Cécile (Le_Vert)"
2008-09-17 11:18           ` Johannes Berg
2008-09-17 11:25             ` Johannes Berg
2008-09-17 20:19             ` Stefanik Gábor
2008-09-17 20:31               ` Johannes Berg
2008-09-17 21:46                 ` Davide Pesavento
2008-09-17 21:51                   ` Stefanik Gábor
2008-09-17 21:52                   ` Johannes Berg [this message]
2008-09-17 21:58                     ` Stefanik Gábor
2008-09-17 22:03                       ` Luis R. Rodriguez
2008-09-17 22:06                         ` Stefanik Gábor
2008-09-17 22:07                           ` Johannes Berg
2008-09-17 22:04                       ` Johannes Berg
2008-09-17 16:23 ` Marcel Holtmann
2008-09-17 16:43   ` Johannes Berg
2008-09-17 18:06     ` Johannes Berg
2008-09-17 19:23       ` Luis R. Rodriguez
2008-09-17 23:36       ` Marcel Holtmann
2008-09-17 23:42         ` Johannes Berg
2008-10-10 21:25           ` Thomas d'Otreppe
2008-09-18  8:09 ` Helmut Schaa
2008-09-27 16:59 ` Davide Pesavento

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=1221688366.7412.13.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=davidepesa@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    /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).