You're right.

Thanks,
Anner.

--

Anner van Hardenbroek,
[email protected]


2010/11/18 Rush Manbert <[email protected]>

> Hi Anner,
>
> It looks to me like you need -lthrift in your command line. It's trying to
> link, but it's not linking against libthrift.a (or the dylib equivalent)
>
> - Rush
>
> On Nov 18, 2010, at 2:20 PM, Anner van Hardenbroek wrote:
>
> > Hi Thrift friends,
> >
> > I've a problem when I try to compile thrift_dump.cpp
> > $ c++ -L/usr/local/lib -I/usr/local/include/boost
> -I/usr/local/include/thrift thrift_dump.cpp -o thrift_dump
> > Undefined symbols:
> >  "vtable for apache::thrift::transport::TFDTransport", referenced from:
> >      __ZTVN6apache6thrift9transport12TFDTransportE$non_lazy_ptr in
> ccV27cVe.o
> >     (maybe you meant:
> __ZTVN6apache6thrift9transport12TFDTransportE$non_lazy_ptr)
> >  "vtable for apache::thrift::protocol::TBinaryProtocol", referenced from:
> >      __ZTVN6apache6thrift8protocol15TBinaryProtocolE$non_lazy_ptr in
> ccV27cVe.o
> >     (maybe you meant:
> __ZTVN6apache6thrift8protocol15TBinaryProtocolE$non_lazy_ptr)
> >  "vtable for apache::thrift::protocol::TDebugProtocol", referenced from:
> >      __ZTVN6apache6thrift8protocol14TDebugProtocolE$non_lazy_ptr in
> ccV27cVe.o
> >     (maybe you meant:
> __ZTVN6apache6thrift8protocol14TDebugProtocolE$non_lazy_ptr)
> >  "vtable for apache::thrift::transport::TFramedTransport", referenced
> from:
> >      __ZTVN6apache6thrift9transport16TFramedTransportE$non_lazy_ptr in
> ccV27cVe.o
> >     (maybe you meant:
> __ZTVN6apache6thrift9transport16TFramedTransportE$non_lazy_ptr)
> >  "vtable for apache::thrift::transport::TBufferedTransport", referenced
> from:
> >      __ZTVN6apache6thrift9transport18TBufferedTransportE$non_lazy_ptr in
> ccV27cVe.o
> >     (maybe you meant:
> __ZTVN6apache6thrift9transport18TBufferedTransportE$non_lazy_ptr)
> > ld: symbol(s) not found
> > collect2: ld returned 1 exit status
> >
> > What I'm missing?
> > Thanks for the help.
> >
> > Kind regards,
> >
> > --
> > Anner van Hardenbroek
> > [email protected]
>
>

Reply via email to