[MacPorts] #69163: emacs @29.2: error: xwidgets requested but WebKitGTK+ or WebKit framework not found (was: Configuring error)

[MacPorts]

#69163: emacs @29.2: error: xwidgets requested but WebKitGTK+ or WebKit framework
not found
-------------------------+----------------------
  Reporter:  alan-zh-sh  |      Owner:  drkp
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  emacs       |
-------------------------+----------------------
Changes (by ryandesign):

 * status:  new => assigned
 * cc: catap (added)
 * owner:  (none) => drkp


Old description:

> When I was install the port with the following command, I got errors
> during configuring step. After tried a few times, I found it was
> +xwidgets led to those errors.
> sudo port install emacs +xwidgets +imagemagick +nativecomp
>
> Here is the error message from the log file.
>
> configure:6943: /usr/bin/clang -c -pipe -Os -Wno-attributes
> -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk -arch
> arm64 -I/opt/local/include
> -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk conftest.c
> >&5
> conftest.c:12:12: error: unknown type name 'barfbarf'
>            barfbarf
>            ^
> 1 error generated.

New description:

 When I was install the port with the following command, I got errors
 during configuring step. After tried a few times, I found it was +xwidgets
 led to those errors.
 sudo port install emacs +xwidgets +imagemagick +nativecomp

 Here is the error message from the log file.

 {{{
 configure:6943: /usr/bin/clang -c -pipe -Os -Wno-attributes
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk -arch arm64
 -I/opt/local/include
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk conftest.c
 >&5
 conftest.c:12:12: error: unknown type name 'barfbarf'
            barfbarf
            ^
 1 error generated.{
 }}}

--

Comment:

 > {{{
 > conftest.c:12:12: error: unknown type name 'barfbarf'
 > }}}

 That is an error message, but it is an intentional error message. That's
 how configure scripts work. They do things, some of which generate errors,
 and depending on what happened the configure script learns things about
 your system. If you look a couple lines above that error message in the
 config.log, you'll see it's part of the test "checking whether the
 compiler is clang" and below the error and the program that generated it,
 "result: yes". So the test successfully identified that your compiler is
 clang. So far so good.

 Looking toward the end of the config.log, I see the real problem was:

 {{{
 configure:17526: error: xwidgets requested but WebKitGTK+ or WebKit
 framework not found.
 }}}

 As to why that happened, I'll leave that to the port's maintainers, to
 whom I'm assigning the ticket.

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