[MacPorts] #72037: gmic @3.5.2_0: Undefined Symbol "_faccessat", referenced from gmic-lib (was: gmic #3.5.2_0 does not Build on Mtn Lion - Undefined Symbol "_faccessat", referenced from gmic-lib)

MacPorts noreply at macports.org
Sun Feb 9 21:11:04 UTC 2025


#72037: gmic @3.5.2_0: Undefined Symbol "_faccessat", referenced from gmic-lib
------------------------+--------------------------
  Reporter:  RobK88     |      Owner:  (none)
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.10.5
Resolution:  duplicate  |   Keywords:  mountainlion
      Port:  gmic       |
------------------------+--------------------------
Changes (by ryandesign):

 * status:  new => closed
 * resolution:   => duplicate


Old description:

> gmic #3.5.2_0 does not Build on Mtn Lion - Undefined Symbol "_faccessat",
> referenced from gmic-lib
>
> {{{
> :info:build undef: _faccessat
> :info:build Undefined symbols for architecture x86_64:
> :info:build   "_faccessat", referenced from:
> :info:build       gmic_library::cimg::posix_searchpath(char const*) in
> gmic.o
> :info:build ld: symbol(s) not found for architecture x86_64
> :info:build clang: fatal error: linker command failed with exit code 1
> (use -v to see invocation)
> :info:build make[1]: *** [gmic] Error 1
> ...
> }}}
>

> See attached main.log.

New description:

 gmic @3.5.2_0 does not Build on Mtn Lion - Undefined Symbol "_faccessat",
 referenced from gmic-lib

 {{{
 :info:build undef: _faccessat
 :info:build Undefined symbols for architecture x86_64:
 :info:build   "_faccessat", referenced from:
 :info:build       gmic_library::cimg::posix_searchpath(char const*) in
 gmic.o
 :info:build ld: symbol(s) not found for architecture x86_64
 :info:build clang: fatal error: linker command failed with exit code 1
 (use -v to see invocation)
 :info:build make[1]: *** [gmic] Error 1
 ...
 }}}


 See attached main.log.

--

Comment:

 `faccessat` is a system call but it is not available on old systems.
 legacy support contains an implementation of it. The port already uses
 legacy support. The problem was that the port did not use LDFLAGS
 correctly. This was already reported in #70676. We don't need a second
 ticket for it.

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


More information about the macports-tickets mailing list