Opened 5 years ago
Closed 4 years ago
#58654 closed defect (fixed)
postgresql11-11.4_0 - problematic variant llvm
| Reported by: | tk7r (Thomas Kotzian) | Owned by: | jyrkiwahlstedt |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.5.4 |
| Keywords: | Cc: | ||
| Port: | postgresql11 postgresql12 |
Description
the package broke in its latest release - only the llvm variants is failing during the staging into destroot phase. Log attached. any other combination +python3, -python3, ... works fine.
Attachments (1)
Change History (6)
Changed 5 years ago by tk7r (Thomas Kotzian)
comment:1 Changed 5 years ago by mf2k (Frank Schima)
| Owner: | set to jyrkiwahlstedt |
|---|---|
| Status: | new → assigned |
In the future, please add the port maintainer(s) to Cc (port info --maintainers postgresql11), if any.
comment:2 Changed 5 years ago by tk7r (Thomas Kotzian)
postgresql12 package has the same problem ...
comment:3 Changed 5 years ago by mf2k (Frank Schima)
| Port: | postgresql12 added |
|---|
comment:4 Changed 5 years ago by tk7r (Thomas Kotzian)
I may have found the solution. on a working system 'port select --summary' shows: clang none mp-clang-8.0 none llvm none mp-llvm-6.0 mp-llvm-7.0 mp-llvm-8.0 none
on a non-working system 'port select --summary' shows have a selected clang and llvm f.e. mp-llvm-8.0/mp-clang-8.0
i have found the hint in the following post : https://postgrespro.com/list/thread-id/2384346
is it possible to set the used compiler/linker from the whole compilation process? - it seems mixing clang/llvm versions during build results in these compile errors.
comment:5 Changed 4 years ago by dgilman (David Gilman)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
build log