From: John Baker <johnnyb@marlboro.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: [LARTC} how can I compile tc
Date: Fri, 23 Mar 2007 18:48:41 +0000 [thread overview]
Message-ID: <46042109.3010602@marlboro.edu> (raw)
Ok, I tried it out but for some reason it doesn't take for the compile
process. This is, after export KERNEL_INCLUDE=/usr/src/linux/include/ if
I run export this declare -x KERNEL_INCLUDE="/usr/src/linux/include/" is
there. But when I run make in iproute2 I still get the
/usr/include/linux/ip.h:93:2: error: #error "Endian problem - this
didn't happen" error.
I tried to circumvent this by moving the /usr/include/linux directory to
/usr/include/linux.old and then making /usr/include/linux a soft link
pointing to /usr/src/linux/include and got a different set of errors as
follows.
make[1]: Entering directory `/usr/src/iproute-2.6.20-070313/lib'
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include
-DRESOLVE_HOSTNAMES -c -o ll_map.o ll_map.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:144,
from /usr/lib/gcc/i486-linux-gnu/4.0.3/include/limits.h:122,
from /usr/lib/gcc/i486-linux-gnu/4.0.3/include/syslimits.h:7,
from /usr/lib/gcc/i486-linux-gnu/4.0.3/include/limits.h:11,
from /usr/include/bits/socket.h:31,
from /usr/include/sys/socket.h:35,
from ll_map.c:18:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file
or directory
In file included from ../include/linux/netlink.h:5,
from ../include/libnetlink.h:5,
from ll_map.c:23:
../include/linux/types.h:5:31: error: linux/posix_types.h: No such file
or directory
In file included from ../include/linux/netlink.h:5,
from ../include/libnetlink.h:5,
from ll_map.c:23:
../include/linux/types.h:166: error: syntax error before ‘__kernel_daddr_t’
../include/linux/types.h:166: warning: no semicolon at end of struct or
union
../include/linux/types.h:167: warning: type defaults to ‘int’ in
declaration of ‘f_tinode’
../include/linux/types.h:167: warning: data definition has no type or
storage class
../include/linux/types.h:170: error: syntax error before ‘}’ token
make[1]: *** [ll_map.o] Error 1
make[1]: Leaving directory `/usr/src/iproute-2.6.20-070313/lib'
make: *** [all] Error 2
The first time I tried this I forgot to run make clean after trying to
compile it against the original /usr/include/linux/ and it actually got
past the initial endian error and died trying to compile tc. When I ran
make clean and tried I go the above error.
Any other thoughts?
Thanks
John
Andy Furniss wrote:
> John Baker wrote:
>> I'm having a bunch of troubles with this as well. I'm using Ubuntu
>> Dapper with vanilla kernel 2.6.20.3.
>>
>> The iproute2-2.6.20 compile dies right away after
>>
>
> Maybe you are using the wrong headers - before the build do -
>
> export KERNEL_INCLUDE=/path/to/your/linux-2.6.20.3/include/
>
> don't build against anything in /usr/include/linux
>
> Andy.
--
John Baker
Network Systems Administrator
Marlboro College
Phone: 451-7551 off campus; 551 on campus
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-03-23 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 18:48 John Baker [this message]
2007-03-24 13:56 ` [LARTC] Re: [LARTC} how can I compile tc Andy Furniss
2007-03-26 14:20 ` John Baker
2007-03-26 20:43 ` Andy Furniss
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=46042109.3010602@marlboro.edu \
--to=johnnyb@marlboro.edu \
--cc=lartc@vger.kernel.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 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.