Tom, where's the -l switch exactly? What command is it attached to? (I'm not sure what to look for.)
Thanks, Travis On Fri, Jan 5, 2018 at 2:56 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvhe...@alvh.no-ip.org> writes: > > Travis Allison wrote: > >> No instance of Postgres 10 running. I took Tom's suggestion: I ran dpkg > -S > >> /usr/include/postgresql/pg_config.h > >> Result: libpq-dev: /usr/include/postgresql/pg_config.h > > Ah, thanks for clearing that up. > > >> Any suggestions on what to do next? > > > I wonder if there is a mistake in the use of INCLUDEDIR vs. > > INCLUDEDIR-SERVER for -I. Maybe both are being used, and looks like > > only the latter should be. It seems odd that there are two pg_config.h > > files getting included ... > > Yeah ... > > > but I do wonder why is there a pg_config.h in libpq-dev. > > Now I seem to recall some discussion with a packager who felt that > providing just the latest-and-greatest libpq was sufficient for > clients, and only server-side code needed to depend on the server > version. So I'm betting that the intention on the Ubuntu packager's > end is that you use a -I for /usr/include/postgresql when building > client code, while if you want to build a server extension, you > point at the appropriate version subdirectory. Meanwhile, the > extension Travis is trying to build is unfamiliar with that idea > and is throwing in a bunch of -I switches willy-nilly. > > In short, yeah, try removing the -I that's pointing at the upper > directory. > > regards, tom lane >
