From: "Arend van Spriel" <arend@broadcom.com>
To: "Claudio Rossi" <rossi.claudio.82@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: __floatunsidf and __fixunsdfsi undefined
Date: Wed, 8 Feb 2012 16:06:30 +0100 [thread overview]
Message-ID: <4F328F76.2040406@broadcom.com> (raw)
In-Reply-To: <CAO1ZyKm1V6FF5aqbdRimdtJRZ+n9exkdUWh06P+i0uqcwweR4A@mail.gmail.com>
On 02/08/2012 03:41 PM, Claudio Rossi wrote:
> Dear all,
> I am trying to compile compat-wireless-3.2-rc6-3 on
> a2.6.32-37-generic i686 GNU/Linux.
> Everything goes well until I enter in phase 2, and I receive the
> following WARNING which prevent the mac80211 modules to work properly
> if installed
>
> make -C /lib/modules/2.6.32-37-generic/build
> M=/home/claudio/Programs/compat-wireless-3.2-rc6-3 modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.32-37-generic'
> Building modules, stage 2.
> MODPOST 9 modules
> WARNING: "__floatunsidf"
> [/home/claudio/Programs/compat-wireless-3.2-rc6-3/net/mac80211/mac80211.ko]
> undefined!
> WARNING: "__fixunsdfsi"
> [/home/claudio/Programs/compat-wireless-3.2-rc6-3/net/mac80211/mac80211.ko]
> undefined!
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-37-generic'
>
> the first time I compiled and installed the compat-wireless-3.2-rc6-3
> it worked, but now it is not.
>
> My distribution (UBUNTU 10.04) already comes with ath9k and mac80211.
>
> Could somebody give me an hint? I am a newbie at this
>
> Thank you
>
> Claudio
>
>
If I am not mistaken, those symbols should be provided by gcc. Maybe
this is a known gcc issue. Try your favorite search engine.
Gr. AvS
prev parent reply other threads:[~2012-02-08 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 14:41 __floatunsidf and __fixunsdfsi undefined Claudio Rossi
2012-02-08 15:06 ` Arend van Spriel [this message]
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=4F328F76.2040406@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rossi.claudio.82@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 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.