All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nickola Kolev <nikky@mnet.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Compile error "iproute2"
Date: Tue, 02 Sep 2003 21:41:17 +0000	[thread overview]
Message-ID: <marc-lartc-106253897012234@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106122635300870@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

Hello,

For example you can try patching iproute2:

vim include-glibc/netinet/in.h
.,$s/linux\/in.h/\/usr\/include\/linux\/in.h

I'm not that "in" those things, but it seems that some distros have
/usr/include/linux linked to the kernel source tree and others dont. I had a
similar situation recently, and I resolved it this way.

Hope this helps.

On Tue, 02 Sep 2003 17:41:13 -0300
Matнas Lуpez Bergero <mlopezb@udesa.edu.ar> wrote:

 : I have a very similar problem with the same iproute2 and htb version, 
 : but with linux 2.4.22 vanilla, not rc2.
 : 
 : /usr/src/linux/include/linux/in.h:140: field `gr_group' has incomplete type
 : /usr/src/linux/include/linux/in.h:141: confused by earlier errors, 
 : bailing out
 : make[1]: *** [ll_map.o] Error 1
 : make[1]: Leaving directory `/opt/iproute2/lib'
 : make: *** [all] Error 2

[ cut ]

-- 
Със здраве,
Никола
_____________________________________________________________

"Engineering does not require science. Science helps a lot but
people built perfectly good brick walls long before they knew
why cement works."	-Alan Cox 	

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-09-02 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 17:04 [LARTC] Compile error "iproute2" Steffen Moser
2003-09-02 20:41 ` Matías López Bergero
2003-09-02 21:41 ` Nickola Kolev [this message]
2003-09-06 14:09 ` ThE PhP_KiD
2003-09-07 12:39 ` Nickola Kolev

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-106253897012234@msgid-missing \
    --to=nikky@mnet.bg \
    --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.