Re: Building PostgreSQL in external directory is broken?

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Building PostgreSQL in external directory is broken?
Date: 2022-07-13 12:37:04
Message-ID: CAPpHfdvDT2VwQoOrjfJkc2KatTBHO7PPRu4_DxATKr7J1jnMcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 13, 2022 at 3:12 PM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
> > That's the short version. The longer version² does claim it's supported:
>
> You are right, I missed this. Thanks!
>
> Regarding these errors:
>
> > ar: cryptohash.o: No such file or directory
> > ar: hmac.o: No such file or directory
> > ...
>
> This has something to do with the particular choice of the ./configure
> flags on a given platform. If I omit:
>
> > --disable-debug --disable-cassert --enable-tap-tests
>
> I get completely different errors:
>
> > clang: error: no such file or directory: 'replication/backup_manifest.o'
> > clang: error: no such file or directory: 'replication/basebackup.o'
>
> Apparently this should be checked carefully with different configure
> flags combinations if we are going to continue maintaining this.

Please, check Alvaro's advise to run "git clean -dfx". Helped to me.

------
Regards,
Alexander Korotkov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2022-07-13 13:14:39 Re: Bug: Reading from single byte character column type may cause out of bounds memory reads.
Previous Message Alexander Korotkov 2022-07-13 12:35:56 Re: Building PostgreSQL in external directory is broken?