LARTC - Jun 2002 - compiling tc on ETRAX (fwd)

Hello.

I would like to compile iproute2 utility suite for Etrax 100LX processors
(www.axis.com). I compiled it, but after running tc i found a problem. tc
doesn''t recognize qdiscs. ex:
 [root@axis /var]67# ./tc qdisc add cbq help
 Unknown qdisc "cbq", hence option "help" is unparsable

I''ve a look through tc.c and found that tc tries to do
dlopen(q_cbq.so,...) and then dlopen(NULL,...) . the first call fail
(it''s
normal, q_cbq.so doesn''t exist), but dlopen(NULL,...) is opening
himself
as library. since q_cbq.o is compiled in, this call shouldn''t fail...
but
it fails.

Another problem is that I cannot run ltrace or gdb on this box (it''s
embedded system). So if tc fails it means that it cannot open itself as
lib. may be tc need some ld mechanism that my box doesn''t support...

How can we do tc without q_*, c_* and f_* included and make them as libs?
just link tc without [q╕c╕f]_*.o and ar them to .a or .so? Am i right?

thanks for your help

PoltoS/

> Hello.
>
> I would like to compile iproute2 utility suite for Etrax 100LX processors
> (www.axis.com). I compiled it, but after running tc i found a problem. tc
> doesn''t recognize qdiscs. ex:
>  [root@axis /var]67# ./tc qdisc add cbq help
>  Unknown qdisc "cbq", hence option "help" is unparsable
tc qdisc add dev eth0 root cbq
what does that say?
> Another problem is that I cannot run ltrace or gdb on this box
(it''s
> embedded system). So if tc fails it means that it cannot open itself as
> lib. may be tc need some ld mechanism that my box doesn''t
support...
It has some kind of fallback mechanism for finding qdisc code, but I
don''t
think it is normally needed.

Regards,

bert


-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO