madlib-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nikolay Samokhvalov <>
Subject Re: Installation issues: Postgres version detection in madpack + password usage
Date Thu, 09 Feb 2017 03:23:44 GMT
Thank you Rahul,

but I insist that this issue is more general than a lack of ability to
install via some manual play with cmake options .

On one the most popular server Linux platforms, Ubuntu (in that case it was
12.04 LTS), the latest Postgres version (9.6.1) installed from official
package is not detected by MADlib. I would be awesome if anyone could
install MADlib with "apt-get install .." only OR with "make && sudo make
install", w/o option puzzles...

Otherwize, this issue might significantly minimize possible audience of the

I would love to help somehow, but I didn't work with cmake.

On Wed, Feb 8, 2017 at 5:15 PM, Rahul Iyer <> wrote:

> The way cmake has been setup, it decides which version to compile for
> using that variable (if defined). If the variable is not defined, it
> locates pg_config and deduces version from it.
> We could add a default PG_CONFIG variable that links to the latest
> supported version. Created a JIRA
> <> for this.
> On Wed, Feb 8, 2017 at 3:10 PM, Jim Nasby <>
> wrote:
>> On 2/8/17 10:18 AM, Rahul Iyer wrote:
>>> add `-DPOSTGRESQL_9_6_PG_CONFIG=/path/to/pg_config' with the `cmake ...`
>>> command
>> Does that variable need to include the version number? Couldn't it just
>> be called PG_CONFIG ?
>> --
>> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
>> Experts in Analytics, Data Architecture and PostgreSQL
>> Data in Trouble? Get it in Treble!
>> 855-TREBLE2 (855-873-2532)

View raw message