I think if -lprotobuf wasn't found, the linker would complain about that
first, rather than complain about undefined references -- unless you have
some other libprotobuf in your library path which is being taken instead.
Maybe an older version?
On Wed, Jan 19, 2011 at 10:29 AM, Jalitt <jal...@gmail.com> wrote:
> I am trying to build google protocol buffers in linux, and then link
> it into a build.
> for configure options, I am passing in --prefix=SOME_LOCAL_DIRECTORY
> make, make check, and make install all work just fine, and the library
> files are chilling in SOME_LOCAL_DIRECTORY.
> Elsewhere, I have a crazy folder heirarchy //one_folder/another/
> I copy the built protocol buffers library files from
> SOME_LOCAL_DIRECTORY and move them to /CompileDirectory/libs
> /CompileDirectory/includes has the include files
> In the makefile in CompileDirectory, I specific /CompileDirectory/libs
> for linking, and -lprotobuf
> Everything builds just fine, but during linking, I get a billion
> "undefined reference" errors. Clearly it is not linking properly with
> the library file.
> I went into the libs directory and "nm libprotobuf.a" and I see the
> symbols are properly published. Anyone have any ideas why its not
> properly linking libprotobuf.a? Is it a ./configfure option I am
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to firstname.lastname@example.org.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at