[Paraview-developers] [EXTERNAL] Re: protoc error
Andy Bauer
andy.bauer at kitware.com
Wed Jan 18 21:52:19 EST 2012
I know that I've seen that error go away when I loaded the GCC module.
Andy
On Wed, Jan 18, 2012 at 5:45 PM, Fabian, Nathan <ndfabia at sandia.gov> wrote:
> Hi Andy,
>
> Thanks for the pointer. My problem is definitely similar. I swapped
> modules because the default intel version stopped building some of the HDF5
> code. But I can't seem to find a set that works! :)
>
> Nathan.
>
> From: Andy Bauer <andy.bauer at kitware.com>
> Date: Wed, 18 Jan 2012 14:34:01 -0500
> To: Nathan Fabian <ndfabia at sandia.gov>
> Cc: "paraview-developers at paraview.org" <paraview-developers at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview-developers] protoc error
>
> Hi Nathan,
>
> I got the same message when building on an SGI Altix. When I switched to
> using a different compiler (intel I think) with the available modules I was
> able to get past this error. Maybe check which modules you loaded and what
> paths are loaded with that. If you come up with a better solution, I'd be
> happy to hear it though.
>
> Andy
>
> On Wed, Jan 18, 2012 at 2:25 PM, Fabian, Nathan <ndfabia at sandia.gov>wrote:
>
>> Hi,
>>
>> I'm using a non-standard location for gcc and it looks like it's
>> causing problems with protoc.
>>
>> I get the following error when trying to build vtkPVMessage.pb.cc
>>
>> …/ParaView_build/bin/protoc: /usr/lib64/libstdc++.so.6: version
>> `GLIBCXX_3.4.10' not found (required by …/ParaView_build/bin/libprotobuf.so)
>>
>> I'm not sure why it's looking at /usr/lib64/libstdc++.so.6 instead
>> of /apps/x86_64/compilers/gcc/gcc-4.3.4/lib64 which is where
>> LD_LIBRARY_PATH is pointing.
>>
>> Thanks,
>> Nathan.
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20120118/0ce0f89b/attachment.htm>
More information about the Paraview-developers
mailing list