On Wed, Dec 21, 2011 at 8:39 AM, Jeremy Bennett
<[email protected]> wrote:
> On Mon, 2011-12-19 at 18:07 +0000, Julius Baxter wrote:
>> Hi all,
>>
>> I've been working on a library which will provide a standard execution
>> trace output format across each of the simulation models.
>>
>> It pulls in the libopcodes and libbfd which are generated when
>> building our binutils port.
>>
>> https://github.com/juliusbaxter/or1ktrace
>>
>> I have a number of problems, though and was wondering if anyone can
>> suggest how to solve them.
>
> Hi Julius,
>
> I asked Joern Rennecke about this, and he made some comments.
Thanks very much for the help.
>
> <snip>
>
>> So if this is the way forward, can anyone suggest how I get the libbfd
>> and libopcodes we compile with our binutils installed somewhere? (I've
>> tried make install-libbfd and install-libopcodes in the build
>> directory and saw it only installed a bunch of .po files get installed
>> and no .a's or .so's.)
>
> Joern> The Makefile in the build dir has a target
> Joern> install-bfdlibLTLIBRARIES. I think that's the one to try.
Yep, that appears to be there.
Do you have any idea of how we might control where this ends up?
I see "$(DESTDIR)$(bfdlibdir)" but am not really sure what that equates to.
Grepping gets me bfdlibdir as empty and DESTDIR being set in
fixincludes/fixinc.sh like so:
./fixincludes/fixinc.sh: DESTDIR=`cd $1;${PWDCMD}`
./fixincludes/fixinc.sh: export DESTDIR
... but then I'm not sure where fixinc.sh gets run from
Anyway, running it got me this:
~/svn/opencores/openrisc/trunk/gnu-src/bd-elf/bfd$ make
install-bfdlibLTLIBRARIES
test -z "" || /bin/mkdir -p ""
... and that was all. I suspect some configuration options are
missing. Can you give me any pointers on what I might need to get the
libraries installed?
>
>> And does anyone know how to get those library
>> switches in after the one we've built for the libor1ktrace test
>> executable?
>
> Joern> One way would be to put another explicit use of the libor1ktrace
> Joern> library before the libbfd switch - assuming the references to the
> Joern> former are already there at this point. Or you could use the
> Joern> --undefined=symbol option to force linking in what you need from
> Joern> libbfd.
>
> Joern> I'm not sure if you could use a --start-group without a matching
> Joern> --end-group to create an open interval.
>
> Joern> If code size is unimportant, you can also try to apply
> Joern> --whole-archive to libbfd.
If we build libor1ktrace when we build the toolchain, this is
certainly something we could do to avoid having to install libbfd and
libopcodes along with it. On the other hand, we're going to have to
install libor1ktrace somewhere, anyway, so if we're doing that we
might as well install the toolchain's libbfd and libopcodes alongside
it then that would solve the problem, too.
Cheers,
Julius
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc
