From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: gdb-7.4 bfin simulator fails to build on Fedora 17
Date: Tue, 24 Jan 2012 17:58:00 -0000 [thread overview]
Message-ID: <4F1EF0BF.1030005@rtems.org> (raw)
Hi,
gdb-7.4's bfin simulator fails to build for bfin-rtems* targets on
Fedora 17/RH rawhide:
....
In file included from /usr/include/linux/ethtool.h:17:0,
from /usr/include/linux/mii.h:12,
from ../../../gdb-7.4/sim/bfin/dv-eth_phy.c:31:
/usr/include/linux/if_ether.h:130:2: error: unknown type name '__be16'
In file included from /usr/include/linux/mii.h:12:0,
from ../../../gdb-7.4/sim/bfin/dv-eth_phy.c:31:
/usr/include/linux/ethtool.h:21:2: error: unknown type name '__u32'
/usr/include/linux/ethtool.h:22:2: error: unknown type name '__u32'
/usr/include/linux/ethtool.h:23:2: error: unknown type name '__u32'
/usr/include/linux/ethtool.h:28:2: error: unknown type name '__u8'
/usr/include/linux/ethtool.h:29:2: error: unknown type name '__u8'
/usr/include/linux/ethtool.h:30:2: error: unknown type name '__u8'
/usr/include/linux/ethtool.h:31:2: error: unknown type name '__u8'
/usr/include/linux/ethtool.h:32:2: error: unknown type name '__u8'
/usr/include/linux/ethtool.h:33:2: error: unknown type name '__u8'
/usr/include/linux/ethtool.h:34:2: error: unknown type name '__u32'
/usr/include/linux/ethtool.h:35:2: error: unknown type name '__u32'
...
The same configuration builds fine for Fedora 15/16 and openSUSE-11.4/12.1.
From what I gather, the bfin simulator chokes upon kernel header
incompatiblities.
Ralf
next reply other threads:[~2012-01-24 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 17:58 Ralf Corsepius [this message]
2012-01-24 20:59 ` Mike Frysinger
2012-01-25 6:18 ` Ralf Corsepius
2012-01-25 6:44 ` Mike Frysinger
2012-03-04 19:57 ` Mike Frysinger
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=4F1EF0BF.1030005@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=gdb@sourceware.org \
/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