Opened 10 months ago
Last modified 7 months ago
#69163 assigned defect
emacs @29.2: error: xwidgets requested but WebKitGTK+ or WebKit framework not found
Reported by: | alan-zh-sh (Alan Zhang) | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | catap (Kirill A. Korinsky), cooljeanius (Eric Gallager) | |
Port: | emacs |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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.{
Attachments (1)
Change History (3)
Changed 10 months ago by alan-zh-sh (Alan Zhang)
Attachment: | config.log added |
---|
comment:1 Changed 10 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | catap added |
---|---|
Description: | modified (diff) |
Owner: | set to drkp |
Status: | new → assigned |
Summary: | Configuring error → emacs @29.2: error: xwidgets requested but WebKitGTK+ or WebKit framework not found |
comment:2 Changed 7 months ago by cooljeanius (Eric Gallager)
Cc: | cooljeanius added |
---|
Note: See
TracTickets for help on using
tickets.
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:
As to why that happened, I'll leave that to the port's maintainers, to whom I'm assigning the ticket.