From: Johannes Berg <johannes@sipsolutions.net>
To: Franz Apeltauer <franz.apeltauer@gmx.at>
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: 2 compile errors: rt2x00firmware.c and mesh.c
Date: Mon, 03 Mar 2008 01:32:11 +0100 [thread overview]
Message-ID: <1204504331.3917.31.camel@johannes.berg> (raw)
In-Reply-To: <47CB3B5E.4020701@gmx.at> (sfid-20080302_234250_620354_B59BDB8D)
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
> CC [M]
> .../compat-wireless-2.6/drivers/net/wireless/rt2x00/rt2x00firmware.o
> .../compat-wireless-2.6/drivers/net/wireless/rt2x00/rt2x00firmware.c:116:
> Fehler: Redefinition von »rt2x00lib_load_firmware«
> = Error: redefiniton of »rt2x00lib_load_firmware«
>
> When I tried to "export CONFIG_CRC_ITU_T=y" before "make",
> rt2x00firmware.c compiled fine. (Probably this is not a good idea. I
> just wanted to see, if it compiles then.)
That's odd because the latest config.mk should check for CRC_ITU_T
before... Ivo could there be a problem with rt2x00 when crc-itu-t isn't
available?
> In /usr/src/linux-headers-2.6.22-14/include/linux/slab.h I found:
> struct kmem_cache *kmem_cache_create(const char *, size_t, size_t,
> unsigned long,
> void (*)(void *, struct kmem_cache *, unsigned long),
> void (*)(void *, struct kmem_cache *, unsigned long));
> i.e. the old, 6-parameter version.
>
> So, IMHO the #define kmem_cache_create in
> - compat-wireless-2.6/include/net/compat.h, line 120 and
> - compat-wireless-2.6/compat/compat.h, line 120
> should be moved 2 lines downwards into the block named
> /* Compat work for 2.6.22 and 2.6.23 */
> Then it compiles fine.
Ok, indeed, it should be moved then, I was working on .21 when I noticed
that needed to be done.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-03-03 0:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 23:42 2 compile errors: rt2x00firmware.c and mesh.c Franz Apeltauer
2008-03-03 0:32 ` Johannes Berg [this message]
2008-03-03 3:52 ` Luis R. Rodriguez
2008-03-05 23:12 ` Franz Apeltauer
2008-03-05 23:15 ` Johannes Berg
2008-03-05 23:25 ` Franz Apeltauer
2008-03-05 23:34 ` Johannes Berg
2008-03-10 23:09 ` Franz Apeltauer
2008-03-08 2:59 ` Luis R. Rodriguez
2008-03-10 21:41 ` Franz Apeltauer
2008-03-10 22:21 ` Ivo van Doorn
2008-03-10 23:33 ` Luis R. Rodriguez
2008-03-11 0:07 ` Franz Apeltauer
2008-03-11 1:26 ` Luis R. Rodriguez
2008-03-11 20:06 ` Hauke Mehrtens
2008-03-11 21:24 ` Luis R. Rodriguez
2008-03-11 22:14 ` Franz Apeltauer
2008-03-11 22:22 ` Ivo van Doorn
2008-03-11 23:01 ` Franz Apeltauer
2008-03-11 23:09 ` Ivo van Doorn
2008-03-16 0:33 ` Franz Apeltauer
2008-03-17 17:12 ` Luis R. Rodriguez
2008-03-03 9:37 ` Ivo Van Doorn
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=1204504331.3917.31.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=franz.apeltauer@gmx.at \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).