Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Ray Van Dolson <rayvd@digitalpath.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: What am I missing?
Date: Thu, 27 Jul 2006 16:45:16 +0000	[thread overview]
Message-ID: <20060727164516.GA11363@digitalpath.net> (raw)
In-Reply-To: <loom.20060724T144823-710@post.gmane.org>

Follow-up to my own post here:

  http://marc.theaimsgroup.com/?l=lartc&m\x115332794424197&w=2

Problem ended up being that the tc included in the iproute RPM in Fedora
Core 2 was built specifically against the headers in the glibc-kernheaders
RPM.

When I switched to a custom kernel (for built-in MPPE support), apparently
some symbols referenced in the glibc-kernheaders package are not present in
the non-RH kernel.  This was causing my issue.

Solution was to modify the .spec file for iproute and tell it to compile
against my custom kernel's headers specifically.

Specifically I had to make the following changes to the .spec file to get
things to work:

 - Modify iproute2-2.4.7-kernel.patch to point to /usr/src/linux/include
 - Do not apply iproute2-2.4.7-misc.patch
 - Do not apply iproute2-2.4.7-in_port_t.patch

This makes everything happy once again!  I'm not sure what the consequenes
are of not applying those RedHat patches, but the tool still works normally
as far as I can tell.

Ray
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2006-07-27 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 13:01 [LARTC] Re: What am I missing? Jarek Poplawski
2006-07-27 16:45 ` Ray Van Dolson [this message]

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=20060727164516.GA11363@digitalpath.net \
    --to=rayvd@digitalpath.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox