Re: Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference
> John David Anglin wrote:
> >> John David Anglin wrote:
> >>>> John David Anglin wrote:
> >>>>>> Moreover, I have downloaded the package from
> >>>>>> http://packages.debian.org/squeeze/hppa/libpt2.6.5/download and
> >>>>>> extracted the lib. IIUC, that function is there indeed (the first is on
> >>>>>> my amd64 machine, the second is hppa extracted file):
> >>>>>>
> >>>>>> snoopy:~$ nm -D /usr/lib/libpt.so.2.6-beta7 |grep Trigger
> >>>>>> 000000000020d850 T _ZN12PVXMLSession7TriggerEv
> >>>>>> 000000000020d840 T _ZThn1096_N12PVXMLSession7TriggerEv
> >>>>>> snoopy:~$ nm -D libpt.so.2.6.5 |grep Trigger
> >>>>>> 001abb74 T _ZN12PVXMLSession7TriggerEv
> >>>>>> 001abb6c T _ZThn1152_N12PVXMLSession7TriggerEv
> >>>>>> snoopy:~$
> >>>>> The latter symbol is the symbol of interest. Would you run the link
> >>>>> command with --trace-symbol=_ZThn1152_N12PVXMLSession7TriggerEv to find
> >>>>> the name of the linked file which references the symbol.
> >>>>>
> >>>>> It may be the link order is bad.
> >>>> /home/dedu/softs/ekiga/ptlib/lib_linux_x86_64/obj/vxml.o: definition of
> >>>> non-virtual thunk to PVXMLSession::Trigger()
> >>> We need to know which file references the symbol. Does adding -lpt
> >>> at the end of the g++ link command resolve the problem?
> >> Well, I know the source file with the symbol. It's src/ptclib/vxml.cxx,
> >> see
> >> http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/ptlib/tags/v2_6_5/src/ptclib/vxml.cxx?revision=23495&view=markup
> >
> > You misunderstood my comment. It's necessary to know which files
> > reference this symbol in order to determine whether this is just an
> > error in the link command, or the linker itself.
>
> So you want that I add -lpt at the end of the following line:
>
> g++ obj_linux_hppa/main.o -lopal -lpt -lpthread -lrt -lsasl2 -lldap
> -llber -lldap_r -lssl -lcrypto -lexpat -lSDL -lodbc -lresolv -ldl
> -lspeexdsp -L ../../lib* -o obj_linux_hppa/simpleopal
>
> but on a hppa architecture, is that right?
Can't hurt.
I just noticed the `../../lib*' in the link command. It could
be a problem.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Reply to: