| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: Building PostgreSQL in external directory is broken? |
| Date: | 2022-07-13 12:12:12 |
| Message-ID: | CAJ7c6TNoR9XYh8tVPLbQFULeF3+Z60N+T+-3ySjMLBJjykVWqw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Ilmari,
> 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.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-07-13 12:19:06 | Re: Building PostgreSQL in external directory is broken? |
| Previous Message | Spyridon Dimitrios Agathos | 2022-07-13 12:09:12 | Bug: Reading from single byte character column type may cause out of bounds memory reads. |