Hi Vaclav, try linking to las_c instead of las
gcc liblastest.c -o liblastest -ggdb -L/usr/lib -llas_c /usr/lib/libgdal.so /usr/lib/libgeotiff.so /usr/lib/x86_64-linux-gnu/libtiff.so boost and las.so not required here, i think On Fri, May 23, 2014 at 10:04 PM, Vaclav Petras <wenzesl...@gmail.com>wrote: > > > > On Fri, May 23, 2014 at 3:35 PM, Rashad M <mohammedrasha...@gmail.com>wrote: > >> Hi Vaclav, >> >> If it helps: http://trac.osgeo.org/grass/ticket/2065 >> >> Thanks, I tried to unify the variables (r57541 and the patch from #2065): > > CFLAGS="$CFLAGS $LIBLAS_CFLAGS $LIBLAS_INC" > CPPFLAGS="$CPPFLAGS $LIBLAS_CPPFLAGS $LIBLAS_INC" > > but it did not help. I see that the ticket is closed and it puzzles me > that it is not enough for me. > > >> On Fri, May 23, 2014 at 9:25 PM, Vaclav Petras <wenzesl...@gmail.com>wrote: >> >>> >>> On Fri, May 23, 2014 at 2:53 PM, Glynn Clements < >>> gl...@gclements.plus.com> wrote: >>> >>>> >>>> Vaclav Petras wrote: >>>> >>>> > So the test failed with segmentation fault >>>> >>>> Possibly due to linking with gcc rather than g++. But that doesn't >>>> matter, as configure tests don't normally try to execute the program >>>> (that doesn't work if you're cross-compiling); they only care whether >>>> linking succeeds. >>>> >>>> >>> I have to remember this gcc vs g++ possible issue and that ./cofigure >>> does not execute. However, it did not helped me now. My sample program >>> still segfaults when compiled with g++. >>> >>> >> > I've tried also cxxflags and a file with cpp extension: > > g++ liblastest.cpp -o liblastest -ggdb $(liblas-config --libs) > $(liblas-config --includes) $(liblas-config --cxxflags) > > but it still segfaults (with and without -ggdb). Should I report this > somewhere (Launchpad, libLAS)? > > > but it would actually fail >>>> > during compilation if I would use `liblas-config --libs` because the >>>> boost >>>> > libraries are `libboost_program_options.so.1.54.0` on my computer >>>> while >>>> > `liblas-config --libs` says just `libboost_program_options.so` (same >>>> for >>>> > thread library). >>>> >>>> You may need to install a -devel package, e.g. boost-devel or >>>> whatever. >>>> >>>> Typically, the unversioned symlink is in the -devel package, as it's >>>> only needed for compiling programs which use the library; running them >>>> will use either the library itself or a symlink which includes at >>>> least the major version number. >>>> >>> >>> I installed libboost-thread-dev and libboost-program-options-dev and >>> compilation works with $(liblas-config --libs) $(liblas-config --includes). >>> So, it should work in ./configure but the result is still "libLAS support: >>> no". >>> >>> >>>> >>>> -- >>>> Glynn Clements <gl...@gclements.plus.com> >>>> >>> >>> >>> _______________________________________________ >>> grass-dev mailing list >>> grass-dev@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/grass-dev >>> >> >> >> >> -- >> Regards, >> Rashad >> > > -- Regards, Rashad
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
