[MacPorts] #67638: postgresql14 @14.8_0+clang15+llvm+perl+python3+tcl broken (by llvm15/16?)

MacPorts noreply at macports.org
Fri Jun 16 13:06:26 UTC 2023


#67638: postgresql14 @14.8_0+clang15+llvm+perl+python3+tcl broken (by llvm15/16?)
-----------------------------------------+--------------------
  Reporter:  Gandoon                     |      Owner:  (none)
      Type:  defect                      |     Status:  new
  Priority:  Normal                      |  Milestone:
 Component:  ports                       |    Version:  2.8.1
Resolution:                              |   Keywords:
      Port:  postgresql14 llvm15 llvm16  |
-----------------------------------------+--------------------
Description changed by Gandoon:

Old description:

> It turns out that the `+llvm` option for postgresql14 might be broken. I
> had the port installed as: `postgresql14
> @14.8_0+clang15+llvm+perl+python3+tcl` but recently the llvm jit
> compilation functionality seems to have been broken. The output of a rev-
> upgrade was as follows:
>
> {{{
> $ port -v rev-upgrade
> --->  Scanning binaries for linking errors
> Could not open /opt/local/libexec/llvm-15/lib/libc++.1.dylib: Error
> opening or reading file (referenced from
> /opt/local/lib/postgresql14/llvmjit.so)
> --->  Found 1 broken file, matching files to ports
> --->  Found 1 broken port, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt: postgresql14
> @14.8+clang15+llvm+perl+python3+tcl
> Continue? [Y/n]: n
> }}}
> Trying to rebuild it yielded an error, and trying to build it with
> clang16 and llvm16 didn't make things better (see attached log).
>
> I reverted to building the port without the `+llvm` option, and that
> works just fine. Any ideas?

New description:

 It turns out that the `+llvm` option for postgresql14 might be broken. At
 least on some legacy systems, I run MacOS 10.15 for certain backwards
 compatibility reasons. I had the port installed as: `postgresql14
 @14.8_0+clang15+llvm+perl+python3+tcl` but recently the llvm jit
 compilation functionality seems to have been broken. The output of a rev-
 upgrade was as follows:

 {{{
 $ port -v rev-upgrade
 --->  Scanning binaries for linking errors
 Could not open /opt/local/libexec/llvm-15/lib/libc++.1.dylib: Error
 opening or reading file (referenced from
 /opt/local/lib/postgresql14/llvmjit.so)
 --->  Found 1 broken file, matching files to ports
 --->  Found 1 broken port, determining rebuild order
 You can always run 'port rev-upgrade' again to fix errors.
 The following ports will be rebuilt: postgresql14
 @14.8+clang15+llvm+perl+python3+tcl
 Continue? [Y/n]: n
 }}}
 Trying to rebuild it yielded an error, and trying to build it with clang16
 and llvm16 didn't make things better (see attached log).

 I reverted to building the port without the `+llvm` option, and that works
 just fine. Any ideas?

--

-- 
Ticket URL: <https://trac.macports.org/ticket/67638#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list