Changes between Initial Version and Version 1 of Ticket #69163


Ignore:
Timestamp:
Jan 23, 2024, 12:34:44 PM (10 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #69163

    • Property Owner set to drkp
    • Property Status changed from new to assigned
    • Property Cc catap added
    • Property Summary changed from Configuring error to emacs @29.2: error: xwidgets requested but WebKitGTK+ or WebKit framework not found
  • Ticket #69163 – Description

    initial v1  
    44Here is the error message from the log file.
    55
     6{{{
    67configure: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
    78conftest.c:12:12: error: unknown type name 'barfbarf'
    89           barfbarf
    910           ^
    10 1 error generated.
     111 error generated.{
     12}}}