[GRASS-dev] libLAS on Ubuntu 14.04

[Rashad M]

Hi again!.

Do you have ctest passed?

For me i have:

Test command:
/home/rashad/Desktop/libLAS-1.7.0/build/bin/Release/liblas_test
"/home/rashad/Desktop/libLAS-1.7.0/test/data"
1: Test timeout computed to be: 1500
1: libLAS Test Suite:
1: ==================
1: liblas::Bounds: ....
1: liblas::Error: ...
1: liblas::Header: ............
1: liblas::Point: ...................
1: liblas::Reader: ........
1: liblas::SpatialReference: .
1: liblas::VariableRecord: ......
1: liblas::Writer: ......
1: liblas::guid: .......
1: liblas::lasreader_iterator: ......................
1:
1: tests summary: ok:88
1/1 Test #1: liblas_test ......................   Passed    0.02 sec

100% tests passed, 0 tests failed out of 1

If so you need update the test in grass configure. BTW. it seems like c
library is not used anymore.You must check this with libLAS devs. But for
now try updating configure test code





On Fri, May 23, 2014 at 11:03 PM, Rashad M <mohammedrashadkm at gmail.com>wrote:

> Much interesting why it ask for c++ when using C headers ?
>
>
> On Fri, May 23, 2014 at 10:58 PM, Vaclav Petras <wenzeslaus at gmail.com>wrote:
>
>>
>>
>>
>> On Fri, May 23, 2014 at 4:52 PM, Rashad M <mohammedrashadkm at gmail.com>wrote:
>>
>>> 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
>>>
>>> Thanks but no success here.
>>
>>
>>>
>>> On Fri, May 23, 2014 at 10:04 PM, Vaclav Petras <wenzeslaus at gmail.com>wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Fri, May 23, 2014 at 3:35 PM, Rashad M <mohammedrashadkm at 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 <wenzeslaus at gmail.com>wrote:
>>>>>
>>>>>>
>>>>>> On Fri, May 23, 2014 at 2:53 PM, Glynn Clements <
>>>>>> glynn at 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 <glynn at gclements.plus.com>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> grass-dev mailing list
>>>>>> grass-dev at lists.osgeo.org
>>>>>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>>    Rashad
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>>    Rashad
>>>
>>
>>
>
>
> --
> Regards,
>    Rashad
>



-- 
Regards,
   Rashad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140523/26bb2f59/attachment-0001.html>