[pgrouting-users] Make pgrouting doesn't find postgres include dirs
Ian Tangert
itangert at gmail.com
Thu Aug 1 05:25:29 PDT 2013
thanks dave and steve,
now it built and installed successfully.
it took three more things:
1) adding #include <sstream> to k_targets_boost_wrapper.cpp
2)changing #include "boost/property_map/property_map.hpp" to #include
"boost/property_map.hpp" in
./src/apsp_johnson/src/apsp_johnson_boost_wrapper.cpp
3)adding to ./src/tsp/src/tsp2.c just under the line #include <math.h>:
#ifndef INIFINITY
# define INFINITY (1.0/0.0)
#endif
best,
ian
On Thu, Aug 1, 2013 at 5:11 AM, Dave Potts <dave.potts at pinan.co.uk> wrote:
> On 01/08/13 05:03, Stephen Woodbridge wrote:
> hi Ian,
>
> I am running this software on Ubunto 12.04
>
> I had some initial build issues mainly sorted by upgrade bits and bobs.
>
> I am running
>
> cmake 2.8.11
> gcc version 4.6.3
> bootst version 1.4.8
> postgis POSTGIS="2.0.0 r9605" GEOS="3.3.8-CAPI-1.7.8" PROJ="Rel. 4.8.0, 6
> March 2012" GDAL="GDAL 1.9.2, released 2012/10/08" LIBXML="2.7.8"
> LIBJSON="UNKNOWN" RASTER
>
> The development version compiles out of the box.
>
> I not suggesting that you upgrade to any of these versions, but its a set
> up that works.
>
> regards
>
> Dave
>
>
> Ian,
>>
>> This looks like something involving the includes in your old version of
>> gcc. I'm running gcc version 4.7.2 (Debian 4.7.2-5) which is very new, but
>> I also was compiling with gcc version 4.3.2 (Debian 4.3.2-1.1) and had no
>> problems with that.
>>
>> You might try adding to k_targets_boost_wrapper.cpp:
>>
>> #include <sstream>
>>
>> It might need to be explicitly included on your version.
>>
>> -Steve
>>
>>
>> On 7/31/2013 4:26 PM, Ian Tangert wrote:
>>
>>> Thanks Steve,
>>>
>>> I got alot farther with pgrouting 2.0 over 1.05 but the make && make
>>> install stopped with the following error:
>>>
>>> /sources/pgrouting/src/**kdijkstra/src/k_targets_boost_**wrapper.cpp: In
>>> function ‘std::string toString(T)’:
>>> /sources/pgrouting/src/**kdijkstra/src/k_targets_boost_**
>>> wrapper.cpp:282:
>>> error: invalid use of undefined type ‘struct std::stringstream’
>>> /usr/lib/gcc/x86_64-redhat-**linux/4.1.2/../../../../**include/c++/4.1.2/iosfwd:83:
>>>
>>> error: declaration of ‘struct std::stringstream’
>>> make[2]: ***
>>> [src/kdijkstra/src/CMakeFiles/**kdijkstra.dir/k_targets_boost_**wrapper.cpp.o]
>>>
>>> Error 1
>>> make[1]: *** [src/kdijkstra/src/CMakeFiles/**kdijkstra.dir/all] Error 2
>>> make: *** [all] Error 2
>>>
>>> a few things i did:
>>>
>>> i had to change the following cgal reference in the CMakeCache.txt
>>> =/usr/local/cgal/3.6.1/lib/**libCGAL.so
>>>
>>> Also, my make was:
>>> make -DWITH_DD=ON -WITH_TSP=ON .
>>> ......
>>> configuring done, generating done, no errors
>>>
>>> make && make install
>>> targets for trsp, astar, and dijkstra were built, but I don't understand
>>> what the new error means
>>>
>>> On Wed, Jul 31, 2013 at 3:27 PM, Stephen Woodbridge
>>> <woodbri at swoodbridge.com <mailto:woodbri at swoodbridge.**com<woodbri at swoodbridge.com>>>
>>> wrote:
>>>
>>> Hi Ian,
>>>
>>> What version of pgRouting are you trying to install?
>>> I strongly recommend us 2.0.0 which is in beta and far more stable
>>> than 1.05.
>>>
>>> git clone https://github.com/pgRouting/_**_pgrouting.git<https://github.com/pgRouting/__pgrouting.git>
>>> <https://github.com/pgRouting/**pgrouting.git<https://github.com/pgRouting/pgrouting.git>
>>> >
>>> cd pgrouting
>>> git checkout develop
>>> mkdir build
>>> cd build
>>> cmake -DWITH_DD=ON ..
>>> make && sudo make install
>>> cd ..
>>> tools/test-runner.pl <http://test-runner.pl>
>>>
>>> Read this for more information:
>>> https://github.com/pgRouting/_**_pgrouting/tree/develop<https://github.com/pgRouting/__pgrouting/tree/develop>
>>> <https://github.com/pgRouting/**pgrouting/tree/develop<https://github.com/pgRouting/pgrouting/tree/develop>
>>> >
>>>
>>> -Steve
>>>
>>>
>>> On 7/31/2013 3:10 PM, Ian Tangert wrote:
>>>
>>> hello,
>>>
>>> when i run make i get the following errors
>>>
>>> make
>>> [ 8%] Building C object
>>> extra/tsp/src/CMakeFiles/__**routing_tsp.dir/tsp.o
>>> In file included from
>>> /usr/pgsql-9.1/include/server/**__nodes/execnodes.h:17,
>>> from
>>> /usr/pgsql-9.1/include/server/**__executor/execdesc.h:18,
>>> from
>>> /usr/pgsql-9.1/include/server/**__executor/executor.h:17,
>>> from
>>> /usr/pgsql-9.1/include/server/**__funcapi.h:21,
>>> from
>>> /sources/pgrouting/pgrouting/_**_extra/tsp/src/tsp.c:26:
>>>
>>> if i edit the the files listed in the error output above so that
>>> the
>>> line that says #include "node/somefile.h" has the full path to
>>> the file
>>> to be included (/usr/pgsql-9.1/include/__**
>>> server/node/somefile.h)
>>> then the
>>> make command no longer produces an error. but any time there is
>>> a new
>>> file to be included i need to edit the first file to include the
>>> full
>>> path and on and on. Is there something i am missing so that
>>> that the
>>> pgrouting make "knows" that everything can be found somewhere in
>>> /usr/pgsql-9.1/include?
>>>
>>> my CMakeCahce.txt file looks like this:
>>> POSTGRESQL_INCLUDE_DIR:__**FILEPATH=/usr/pgsql-9.1/__**include
>>>
>>> I am trying to install this on CentOS 5.5 with a postgresql
>>> installation
>>> that came from 9.1.9-1PGDG.rhel5, postgis also successfully
>>> installed
>>> and extension created in database
>>>
>>> would it work if i just kept adding the full path in the include
>>> line in
>>> the *.h files, and if I did would that mess anything up for
>>> postgres in
>>> general?
>>>
>>> thanks for any advice
>>>
>>> ps my cmake -DWITH_TSP=ON -DWITH_DD=ON . output looks like this:
>>>
>>> Boost headers were found here: /usr/include
>>> Output directory for libraries is set to /usr/pgsql-9.1/lib
>>> Installation directory for libraries is set to
>>> /usr/pgsql-9.1/lib and
>>> for SQL files is set to /usr/share/pgrouting
>>> Installation directory for libraries is set to /usr/pgsql-9.1/lib
>>> -- Configuring done
>>> -- Generating done
>>> -- Build files have been written to: /sources/pgrouting/pgrouting
>>>
>>>
>>> ______________________________**___________________
>>> Pgrouting-users mailing list
>>> Pgrouting-users at lists.osgeo.__**org
>>> <mailto:Pgrouting-users at lists.**osgeo.org<Pgrouting-users at lists.osgeo.org>
>>> >
>>> http://lists.osgeo.org/__**mailman/listinfo/pgrouting-__**users<http://lists.osgeo.org/__mailman/listinfo/pgrouting-__users>
>>> <http://lists.osgeo.org/**mailman/listinfo/pgrouting-**users<http://lists.osgeo.org/mailman/listinfo/pgrouting-users>
>>> >
>>>
>>>
>>> ______________________________**___________________
>>> Pgrouting-users mailing list
>>> Pgrouting-users at lists.osgeo.__**org
>>> <mailto:Pgrouting-users at lists.**osgeo.org<Pgrouting-users at lists.osgeo.org>
>>> >
>>> http://lists.osgeo.org/__**mailman/listinfo/pgrouting-__**users<http://lists.osgeo.org/__mailman/listinfo/pgrouting-__users>
>>> <http://lists.osgeo.org/**mailman/listinfo/pgrouting-**users<http://lists.osgeo.org/mailman/listinfo/pgrouting-users>
>>> >
>>>
>>>
>>>
>>>
>>> ______________________________**_________________
>>> Pgrouting-users mailing list
>>> Pgrouting-users at lists.osgeo.**org <Pgrouting-users at lists.osgeo.org>
>>> http://lists.osgeo.org/**mailman/listinfo/pgrouting-**users<http://lists.osgeo.org/mailman/listinfo/pgrouting-users>
>>>
>>>
>> ______________________________**_________________
>> Pgrouting-users mailing list
>> Pgrouting-users at lists.osgeo.**org <Pgrouting-users at lists.osgeo.org>
>> http://lists.osgeo.org/**mailman/listinfo/pgrouting-**users<http://lists.osgeo.org/mailman/listinfo/pgrouting-users>
>>
>
> ______________________________**_________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.**org <Pgrouting-users at lists.osgeo.org>
> http://lists.osgeo.org/**mailman/listinfo/pgrouting-**users<http://lists.osgeo.org/mailman/listinfo/pgrouting-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20130801/6374067c/attachment.html>
More information about the Pgrouting-users
mailing list