From: Keith Owens <kaos@ocs.com.au>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Florian Lohoff <flo@rfc822.org>, Keith Owens <kaos@ocs.com.au>,
linux-mips@oss.sgi.com, kaos@ocs4.ocs-net.sgi.com
Subject: Re: Kernel crash on boot with current cvs (todays)
Date: Tue, 12 Jun 2001 12:05:19 +1000 [thread overview]
Message-ID: <1118.992311519@ocs4.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 12 Jun 2001 03:01:32 +0200." <Pine.GSO.3.96.1010612025658.18298A-100000@delta.ds2.pg.gda.pl>
> On Mon, 11 Jun 2001, Florian Lohoff wrote:
>
> > Nope - it wont as it strictly uses the /usr/bin/objdump - You have to
> > set the environment var "KSYMOOPS_OBJDUMP"
>
> Good it has a way to override the default, but wouldn't looking for
> objdump in the PATH variable (i.e. using execvp()) be more reasonable?
> This way ksymoops would always work in a cross-compilation environment
> (i.e. with $tooldir/bin preceding $bindir in PATH).
I originally designed ksymoops that way but there are so many different
methods of naming the binutils for cross compile environments that I
gave up. Using the path runs the risk of picking random versions of nm
and objdump and still not being correct. Anybody running cross compile
has to specify parameters for System.map, ksyms and objects, so adding
paths for binutils is a small change and is the only way to guarantee
that the correct versions are used.
next prev parent reply other threads:[~2001-06-12 2:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 22:03 Kernel crash on boot with current cvs (todays) Florian Lohoff
2001-06-11 3:53 ` Keith Owens
2001-06-11 19:12 ` Florian Lohoff
2001-06-12 1:01 ` Maciej W. Rozycki
2001-06-12 1:01 ` Keith M Wesolowski
2001-06-12 1:22 ` Maciej W. Rozycki
2001-06-12 2:05 ` Keith Owens [this message]
2001-06-11 4:42 ` Ralf Baechle
2001-06-11 14:50 ` Raoul Borenius
2001-06-12 10:09 ` Florian Lohoff
2001-06-12 11:53 ` Ralf Baechle
2001-06-12 16:37 ` H . J . Lu
[not found] ` <20010613100602.A17124@bunny.shuttle.de>
2001-06-13 10:56 ` Florian Lohoff
2001-06-13 11:34 ` Keith Owens
2001-06-13 12:05 ` Ralf Baechle
2001-06-13 12:19 ` ksymoops changes for mips (was Kernel crash on boot with current cvs) Keith Owens
2001-06-16 9:22 ` Ralf Baechle
2001-06-27 2:21 ` ksymoops changes for mips Keith Owens
2001-06-28 14:32 ` Thiemo Seufer
2001-07-31 3:57 ` Keith Owens
2001-07-31 4:30 ` Keith Owens
2001-08-03 6:10 ` Keith Owens
2001-08-03 10:07 ` Thiemo Seufer
2001-06-13 13:44 ` Kernel crash on boot with current cvs (todays) Maciej W. Rozycki
2001-06-13 14:07 ` Keith Owens
2001-06-13 15:08 ` Maciej W. Rozycki
2001-06-16 9:24 ` Ralf Baechle
2001-06-13 11:37 ` Raoul Borenius
2001-06-13 11:46 ` Keith Owens
2001-06-13 11:46 ` Keith Owens
2001-06-13 13:16 ` Raoul Borenius
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=1118.992311519@ocs4.ocs-net \
--to=kaos@ocs.com.au \
--cc=flo@rfc822.org \
--cc=kaos@ocs4.ocs-net.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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