From: Jacek Bilski <dino@camelot.homedns.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] compile errors
Date: Sat, 27 Sep 2003 08:30:40 +0000 [thread overview]
Message-ID: <marc-lartc-106465152215211@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100324179302445@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
Hello!
On sob, 2003-09-27 at 05:11, Andrew Carson wrote:
> I've noticed a few people have had probs compiling iproute2 on the 2.4.22
> kernel.. has anyone found a fix yet? I'm having the same problem:
Workaround: make your /usr/src/linux point to /usr/src/linux-2.4.21
rather than /usr/src/linux-2.4.22, it works_for_me (TM). I didn't
investigate where from are those errors.
Greetings!
--
Jacek Bilski <dino@camelot.homedns.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-27 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 14:17 [LARTC] compile errors Ethy H. Brito
2001-10-16 14:20 ` Djamil ESSAISSI
2001-10-16 14:42 ` Djamil ESSAISSI
2001-10-16 14:56 ` Ethy H. Brito
2003-09-27 3:11 ` Andrew Carson
2003-09-27 8:30 ` Jacek Bilski [this message]
2003-09-27 8:55 ` Andrew Carson
2003-12-04 1:25 ` Cosmin Nutiu
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-106465152215211@msgid-missing \
--to=dino@camelot.homedns.org \
--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