| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | AJ ONeal <coolaj86(at)proton(dot)me> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to Build Postgres in a Portable / Relocatable fashion? |
| Date: | 2024-05-04 02:44:23 |
| Message-ID: | 2798894.1714790663@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
AJ ONeal <coolaj86(at)proton(dot)me> writes:
> It seems like the first bit of magic I need is:
> `--prefix=/doesntexist/postgres`
No, you want an actual path so that "make install" will succeed.
The point is that then you can tar up that installation tree
(relative to its top) and untar it somewhere else.
> I'd like to build as much static as possible (or reasonable). Is there a way to tell it "just include openssl"?
No, and are you really sure you want that? Then it's on you to
rebuild and redistribute, pronto, every time openssl issues a security
fix. There's a reason why most Linux distros forbid static linking of
libraries from different sources.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Siddharth Jain | 2024-05-04 03:02:49 | Re: Question regarding how databases support atomicity |
| Previous Message | Adrian Klaver | 2024-05-04 02:35:24 | Re: How to Build Postgres in a Portable / Relocatable fashion? |