-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal error: 'libpq-fe.h' file not found #59
Comments
you need to make sure you have install the postgresql server devel package for you system |
yeah, definitely the problem. I installed the postgres 9.4 and it went further, now what happens is:
|
Nevermind, i ended up using https://github.com/zzolo/osm2pgrouting-mac |
Probably this small change will solve the problem, but we need to see, if this affects other operating systems: zzolo@dc7fdce |
One thing that i don't know is worth the attention here is an error that i had in the load with the mac version:
|
I confirmed this issue on my macports environment. |
Osm data indices are bigint, maybe the code is storing them on int variables?. so the value 2171617416 is an ID and its out of range of integers but fit on int64_t. (aka long) |
On Ubuntu 14.04 installing libpq-dev and changing the include in Export2DB.h worked, but now I, and at least one other person on Gis Stack Exchange, get a bunch of linking errors. Apparently the solution is to add a -lpq somewhere, but I can't figure out where. The make output is very long so I dumped it into pastebin: http://pastebin.com/7ukNB3yn |
Well, I had no problems to create Ubuntu packages for 14.04, so it shouldn't be a problem to compile at least with Debian based distributions. You can find the package related configuration here: Debian
So |
I think the problem is due to the postgre version. I have this one installed: postgres (PostgreSQL) 9.3.6 PS: Im using mac OSX 10.9.5 |
Try doing |
this message is displayed even after i run the command "sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist" |
Anyone had this problem on mac osx at
inside the build folder?
The text was updated successfully, but these errors were encountered: