All of lore.kernel.org
 help / color / mirror / Atom feed
From: Poltorak Serguei <poltorak@df.ru>
To: lartc@vger.kernel.org
Subject: [LARTC] compiling tc on ETRAX (fwd)
Date: Sat, 29 Jun 2002 15:47:08 +0000	[thread overview]
Message-ID: <marc-lartc-102536571701200@msgid-missing> (raw)

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/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-06-29 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29 15:47 Poltorak Serguei [this message]
2002-06-29 16:16 ` [LARTC] compiling tc on ETRAX (fwd) bert hubert

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=marc-lartc-102536571701200@msgid-missing \
    --to=poltorak@df.ru \
    --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.