You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Geir Magnusson Jr <ge...@pobox.com> on 2006/06/20 07:05:26 UTC
[drlvm] linking question
I've been puttering about and am having a problem under linux.
Everything builds now, and APR is built using the standard ./configure &
make combination. No big deal.
But I seem to have a linking problem - libvmi.so gets built w/o things
like pool_* entries resolved. I do believe that I'm pointing the linker
at the right files in /classlib via vmi.xml via libset. I think I'm
right as when I tweak the lib name, say from "hypool" to "hypoolwoogie"
the build complains.
But still - libvmi.so on my box is made w/o those deps.
Given that the <cc> and <linker> ant tasks are black magic to me, how
does one figure this out? can you make <cc> tell you want it's doing?
I have no idea what it's using to link, for example, and what the
invocation of the linker is in terms of flags and args.
Any help appreciated...
geir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: [drlvm] linking question
Posted by Geir Magnusson Jr <ge...@pobox.com>.
Thanks!
Yes, that solved is.
Marina Goldburt wrote:
> Hi,
>
> The problem is in the order of the linked libs. the order is important for
> gcc.
> Change components/vm/vmi, the order must be:
>
> <libset libs="hyzip" dir="${external.dep.CLASSLIB.libdir}" />
> <libset libs="hypool" dir="${external.dep.CLASSLIB.libdir}" />
> <libset libs="hyprt" dir="${external.dep.CLASSLIB.libdir}" />
>
> Marina
>
>
> On 6/20/06, Mark Hindess <ma...@googlemail.com> wrote:
>>
>>
>> On 20 June 2006 at 1:05, Geir Magnusson Jr <ge...@pobox.com> wrote:
>> > I've been puttering about and am having a problem under linux.
>> >
>> > Everything builds now, and APR is built using the standard
>> ./configure &
>> > make combination. No big deal.
>> >
>> > But I seem to have a linking problem - libvmi.so gets built w/o things
>> > like pool_* entries resolved. I do believe that I'm pointing the
>> linker
>> > at the right files in /classlib via vmi.xml via libset. I think I'm
>> > right as when I tweak the lib name, say from "hypool" to "hypoolwoogie"
>> > the build complains.
>> >
>> > But still - libvmi.so on my box is made w/o those deps.
>> >
>> > Given that the <cc> and <linker> ant tasks are black magic to me, how
>> > does one figure this out? can you make <cc> tell you want it's doing?
>> > I have no idea what it's using to link, for example, and what the
>> > invocation of the linker is in terms of flags and args.
>> >
>> > Any help appreciated...
>>
>> Does:
>>
>> ANT_ARGS=-v sh build.sh
>>
>> give you enough information?
>>
>> -Mark.
>>
>>
>>
>> ---------------------------------------------------------------------
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>>
>>
>
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: [drlvm] linking question
Posted by Marina Goldburt <ma...@gmail.com>.
Hi,
The problem is in the order of the linked libs. the order is important for
gcc.
Change components/vm/vmi, the order must be:
<libset libs="hyzip" dir="${external.dep.CLASSLIB.libdir}" />
<libset libs="hypool" dir="${external.dep.CLASSLIB.libdir}" />
<libset libs="hyprt" dir="${external.dep.CLASSLIB.libdir}" />
Marina
On 6/20/06, Mark Hindess <ma...@googlemail.com> wrote:
>
>
> On 20 June 2006 at 1:05, Geir Magnusson Jr <ge...@pobox.com> wrote:
> > I've been puttering about and am having a problem under linux.
> >
> > Everything builds now, and APR is built using the standard ./configure &
> > make combination. No big deal.
> >
> > But I seem to have a linking problem - libvmi.so gets built w/o things
> > like pool_* entries resolved. I do believe that I'm pointing the linker
> > at the right files in /classlib via vmi.xml via libset. I think I'm
> > right as when I tweak the lib name, say from "hypool" to "hypoolwoogie"
> > the build complains.
> >
> > But still - libvmi.so on my box is made w/o those deps.
> >
> > Given that the <cc> and <linker> ant tasks are black magic to me, how
> > does one figure this out? can you make <cc> tell you want it's doing?
> > I have no idea what it's using to link, for example, and what the
> > invocation of the linker is in terms of flags and args.
> >
> > Any help appreciated...
>
> Does:
>
> ANT_ARGS=-v sh build.sh
>
> give you enough information?
>
> -Mark.
>
>
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>