From: Thiemo Seufer <ths@networkno.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: linux-mips@linux-mips.org
Subject: Re: [OT?] is there something strange about __builtin_ffs these days?
Date: Mon, 17 Dec 2007 21:45:03 +0000 [thread overview]
Message-ID: <20071217214503.GB17397@networkno.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712171602090.13289@localhost.localdomain>
Robert P. J. Day wrote:
>
> i'm hoping i'm not abusing this list overly by asking for some help
> with debugging an OpenWRT issue. the trac ticket is here:
>
> https://dev.openwrt.org/ticket/2735
>
> and involves cross-compiling an image for the MIPS-based linksys
> WRT54GL router. i've verified that this error still exists in the
> latest svn update of openwrt and, in a nutshell, it involves the claim
> that "__builtin_ffs" is undefined:
>
> ...
> CC [M] /home/openwrt/builds/trunk_brcm47xx/build_dir/linux-brcm47xx/spca5xx-le/spca_core.o
> /home/openwrt/builds/trunk_brcm47xx/build_dir/linux-brcm47xx/spca5xx-le/spca_core.c:538:5:
> warning: "__builtin_ffs" is not defined
> /home/openwrt/builds/trunk_brcm47xx/build_dir/linux-brcm47xx/spca5xx-le/spca_core.c:538:5:
> error: missing binary operator before token "("
> ...
>
> that line in the source file is simply:
>
> #if PUD_SHIFT
>
> i have no idea what the problem is here and, as you can see from the
> trac ticket, this seems to have started because of the kernel version
> upgrade from 2.6.22 to 2.6.23. but what about that would affect the
> usage of __builtin_ffs?
>
> does anyone have an idea why something this basic might be going
> wrong now? any suggestions appreciated. thanks.
The compiler should never attempt to use __builtin_ffs by itself, because
the kernel makefile adds -ffreestanding to CFLAGS. So either your compiler
is broken, or the makefile of your kernel tree is incorrect, or somewhere
in your kernel tree there's a explicit call to __builtin_ffs (which is
also incorrect, as the compiler may invoke library functions to implement
it.)
Thiemo
prev parent reply other threads:[~2007-12-17 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:08 [OT?] is there something strange about __builtin_ffs these days? Robert P. J. Day
2007-12-17 21:45 ` Thiemo Seufer [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=20071217214503.GB17397@networkno.de \
--to=ths@networkno.de \
--cc=linux-mips@linux-mips.org \
--cc=rpjday@crashcourse.ca \
/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