Re: Configure problem when cross-compiling PostgreSQL 16.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dominik Michael Rauh <dmrauh(at)posteo(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Configure problem when cross-compiling PostgreSQL 16.1
Date: 2023-12-07 14:18:13
Message-ID: 1266022.1701958693@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dominik Michael Rauh <dmrauh(at)posteo(dot)de> writes:
> Apparently when cross-compiling the linker is automatically assumed to not
> understand "--export-dynamic", leading to aforementioned problem on my end.
> ...
> There is also at least one additional linker flag "--as-needed" that is not
> being used when cross-compiling. Is this a bug or am I misunderstanding the
> implications that PostgreSQL has when "$cross_compiling=yes"?

Cross-compiling isn't really a supported thing, because there's too
much stuff we can't find out about the target system in that case.
If it works for you, great, but if it doesn't we're unlikely to put
a lot of effort into fixing it. You might be able to manually
correct whatever mistaken assumptions configure made (by editing
its output files). It's hard to see how that could be automated
though.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-12-07 14:22:10 Re: backtrace_on_internal_error
Previous Message Aleksander Alekseev 2023-12-07 14:16:59 Re: Proposal to add page headers to SLRU pages