From: Enrik Berkhan <Enrik.Berkhan@planb.de>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: Tue, 22 Jan 2002 16:11:36 +0100 [thread overview]
Message-ID: <20020122161135.A6205@electra.intern.planb.de> (raw)
In-Reply-To: <3C4D5A46.426BE5E5@admin.france.hp.com>
Bruno,
On Tue, Jan 22, 2002 at 01:25:42PM +0100, Bruno Vidal wrote:
> I think that Enrik has a good starting point, where can I find
> a good how-to about libbfd ? there is nothing under /usr/share/doc ?
> A web page ?
(assuming debian) you can install `bintutils-doc´ and will be
able to do `info bfd´ afterwards. But it´s far from a tutorial ...
Enrik
--
Enrik Berkhan plan b. GmbH
Rüppurrer Straße 4
+49-721-388582 (voice) 76137 Karlsruhe
+49-721-388581 (fax) Germany
next prev parent reply other threads:[~2002-01-22 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 17:45 [parisc-linux] vmlinux header for savecrash Bruno Vidal
2002-01-21 20:25 ` Grant Grundler
2002-01-22 9:20 ` Bruno Vidal
2002-01-22 9:55 ` Enrik Berkhan
2002-01-22 12:25 ` Bruno Vidal
2002-01-22 15:11 ` Enrik Berkhan [this message]
2002-01-22 15:13 ` Matthew Wilcox
2002-01-22 12:05 ` James P. Kinney III
2002-01-22 17:45 ` Grant Grundler
2002-01-22 17:53 ` Randolph Chung
2002-01-22 17:59 ` Bruno Vidal
2002-01-22 17:55 ` Bruno Vidal
2002-01-22 18:11 ` Randolph Chung
2002-01-22 18:34 ` Grant Grundler
2002-01-22 0:43 ` James P. Kinney III
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 2:58 [parisc-linux] installation problems on an A500 Matthias Klose
2002-01-07 3:46 ` Grant Grundler
2002-01-22 19:59 ` [parisc-linux] vmlinux header for savecrash Paul Bame
2002-01-23 2:13 ` Grant Grundler
2002-01-23 10:23 ` Andreas Deresch
2002-01-25 6:30 ` Grant Grundler
2002-01-23 8:57 ` Enrik Berkhan
2002-01-23 9:29 ` phi 4369
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=20020122161135.A6205@electra.intern.planb.de \
--to=enrik.berkhan@planb.de \
--cc=bruno_vidal@hpfrcu03.france.hp.com \
--cc=parisc-linux@lists.parisc-linux.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