mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: vda <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Maybe I have a bad day or something
Date: Tue, 25 Dec 2001 20:30:40 +1100	[thread overview]
Message-ID: <32642.1009272640@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 25 Dec 2001 09:09:31 BST." <Pine.LNX.4.33.0112250745190.631-100000@mikeg.weiden.de>

On Mon, 24 Dec 2001, vda wrote:
> Who fscking care that I am trying to debug a kernel problem and my first
> ksymoops compilation went astray? (I discovered that ksymoops needs bfd lib
> from binutils a month later). We need no stinking decoded oops!
> And we never were newbies, we were born with Linux in our blood!

If you had bothered to look at the INSTALL file in the ksymoops source,
you would have found this :-

  To compile and link ksymoops, you need bfd.h, libbfd and libiberty.  On
  most systems, these are all part of the binutils package so installing
  binutils is all that is required.  On Debian systems, bfd.h (at least)
  is in a separate package, binutils-dev.

Since you are obviously incapable of reading a simple INSTALL file and
then have the gall to complain on linux-kernel while demonstrating your
own ineptitude, you get a free introduction to my kill file.  vda meet
kill file, kill file meet vda.  Goodbye.


  reply	other threads:[~2001-12-25  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-24 17:07 vda
2001-12-24 14:23 ` Pat Villani
2001-12-24 16:11   ` Matthew Johnson
2001-12-24 17:39     ` David Lang
2001-12-24 18:21       ` John Alvord
2001-12-25 17:21   ` Matthew M
2001-12-24 15:27 ` Wakko Warner
2001-12-24 21:07 ` Stevie O
2001-12-24 22:18   ` Andreas Steinmetz
2001-12-25  8:09 ` Mike Galbraith
2001-12-25  9:30   ` Keith Owens [this message]
2001-12-31  1:13     ` Mark Harrop

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=32642.1009272640@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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

all inboxes | Powered by JetHome®