* elfutils disassembler
@ 2008-05-20 8:16 Tim Moore
2008-05-27 19:49 ` Andrew Cagney
0 siblings, 1 reply; 2+ messages in thread
From: Tim Moore @ 2008-05-20 8:16 UTC (permalink / raw)
To: frysk
I've reactivated the disassembler, using the elfutils version instead
of the one from libopcodes. Give it a spin. One problem with it is that
to run it in the build tree you need to set LD_LIBRARY_PATH to point to
the elfutils backend shared libraries e.g.,
LD_LIBRARY_PATH=~/frysk-build/frysk-imports/elfutils/backends. Is there
a way to avoid that without much libtool madness? I haven't done
anything yet about installing those libraries when frysk is installed;
I'll look into that.
Tim
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: elfutils disassembler
2008-05-20 8:16 elfutils disassembler Tim Moore
@ 2008-05-27 19:49 ` Andrew Cagney
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Cagney @ 2008-05-27 19:49 UTC (permalink / raw)
To: Tim Moore; +Cc: frysk
Cool. We gave it a spin at todays meeting and it looks good.
For the SOLIB question, I think we can work with this for the moment,
we'll be overhauling all the SOLIB stuff as part of JNI anyway.
Andrew
Tim Moore wrote:
> I've reactivated the disassembler, using the elfutils version instead
> of the one from libopcodes. Give it a spin. One problem with it is that
> to run it in the build tree you need to set LD_LIBRARY_PATH to point to
> the elfutils backend shared libraries e.g.,
> LD_LIBRARY_PATH=~/frysk-build/frysk-imports/elfutils/backends. Is there
> a way to avoid that without much libtool madness? I haven't done
> anything yet about installing those libraries when frysk is installed;
> I'll look into that.
>
> Tim
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-05-21 15:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-05-20 8:16 elfutils disassembler Tim Moore
2008-05-27 19:49 ` Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).