* [Buildroot] cannot build: conflicting types for '__kernel_dev_t'
@ 2009-02-01 11:44 S0L0 at gmx-topmail.de
0 siblings, 0 replies; only message in thread
From: S0L0 at gmx-topmail.de @ 2009-02-01 11:44 UTC (permalink / raw)
To: buildroot
Hello,
i just wanted to try again getting buildroot to wrk, but I seem to have one more porblem:
I set up a new debian environment before ~ 2 hours. Installed gcc, libncurses5-dev and subversion (and all dependencies, of course).
After that I downloaded the sources and tried to compile:
svn co svn://uclibc.org/trunk/uClibc
cd uClibc
make menuconfig
->changed "Target Architecture" to "i386" and "Target x86 Processor Family" to "Pentium/586/K5/5x86/6x86/6x86MX".
make
################
I got the folowwing error after a couple of seconds:
CC libc/inet/ether_addr.os
In file included from /usr/include/linux/if_ether.h:24,
from ./include/netinet/if_ether.h:26,
from ./include/netinet/ether.h:26,
from libc/inet/ether_addr.c:31:
/usr/include/linux/types.h:11: error: conflicting types for '__kernel_dev_t'
./include/bits/kernel_types.h:19: error: previous declaration of '__kernel_dev_t' was here
make: *** [libc/inet/ether_addr.os] Fehler 1
################
ok, I think, I understand what the error is, but I do not have a clue of how to fix this. I just played a bit around commenting-out the suspicious lines, but I ended up with more errors.
I hope anybody out there can help me :)
Best regards,
S0l0
--
_____________________________________________________________
Stephan Blanke
Stephan.Blanke at gmx.de
#166931535
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-02-01 11:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-01 11:44 [Buildroot] cannot build: conflicting types for '__kernel_dev_t' S0L0 at gmx-topmail.de
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox