What steps will reproduce the problem?
1. download protobuf 2.5.0 sources, unpak
2. apply two ppc64 patches (from issue 488)
3. ./configure, make (gcc 4.7.4) - OK
4. make install - got error "liblto_plugin.so not found", but it located in
/usr/gcc-4.7.4/lib/gcc/powerpc64-unknown-linux-gnu/4.7.4/
What is the expected output? What do you see instead?
libtool: relink: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/../lib64/crti.o
/usr/gcc-4.7.4/lib/gcc/powerpc64-unknown-linux-gnu/4.7.4/crtbeginS.o
.libs/code_generator.o .libs/command_line_interface.o .libs/plugin.o
.libs/plugin.pb.o .libs/subprocess.o .libs/zip_writer.o .libs/cpp_enum.o
.libs/cpp_enum_field.o .libs/cpp_extension.o .libs/cpp_field.o .libs/cpp_file.o
.libs/cpp_generator.o .libs/cpp_helpers.o .libs/cpp_message.o
.libs/cpp_message_field.o .libs/cpp_primitive_field.o .libs/cpp_service.o
.libs/cpp_string_field.o .libs/java_enum.o .libs/java_enum_field.o
.libs/java_extension.o .libs/java_field.o .libs/java_file.o
.libs/java_generator.o .libs/java_helpers.o .libs/java_message.o
.libs/java_message_field.o .libs/java_primitive_field.o .libs/java_service.o
.libs/java_string_field.o .libs/java_doc_comment.o .libs/python_generator.o
-Wl,-rpath -Wl,/usr/gcc-4.7.4/lib/../lib64 -lpthread -L/usr/local/lib
-lprotobuf -lz -L/usr/gcc-4.7.4/lib/gcc/powerpc64-unknown-linux-gnu/4.7.4
-L/usr/gcc-4.7.4/lib/gcc/powerpc64-unknown-linux-gnu/4.7.4/../../../../lib64
-L/lib/../lib64 -L/usr/lib/../lib64
-L/usr/gcc-4.7.4/lib/gcc/powerpc64-unknown-linux-gnu/4.7.4/../../..
-L/usr/gcc-4.7.4/lib/../lib64 -lstdc++ -lm -lc -lgcc_s
/usr/gcc-4.7.4/lib/gcc/powerpc64-unknown-linux-gnu/4.7.4/crtendS.o
/usr/lib/../lib64/crtn.o -pthread -O2 -pthread -Wl,-soname
-Wl,libprotoc.so.8 -o .libs/libprotoc.so.8.0.0
g++: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
compilation terminated.
libtool: install: error: relink `libprotoc.la' with the above command before
installing it
What version of the product are you using? On what operating system?
SLES-ppc64 11SP3
Please provide any additional information below.
Original issue reported on code.google.com by lawr.es...@gmail.com on 10 Jul 2014 at 8:29
Original issue reported on code.google.com by
lawr.es...@gmail.comon 10 Jul 2014 at 8:29