emacs +x11 tries to use libXaw3d.dylib

[russell.jones@…]

This prevents emacs from being built with the +x11 variant.

Output of

sudo port selfupdate
sudo port clean emacs
sudo port -d install emacs +x11 &> "emacs+x11-debug-`date "+%Y%m%d%H%M%S"`.txt"

attached

[russell.jones@…]

port -d install output

[sewebster@…]

Xaw3d isn't a dependency of emacs +x11, right? Does an existing i386 Xaw3d install cause a conflict with xorg-libXaw here?

[sewebster@…]

Cc Me!

[dports@…]

Cc Me!

[dports@…]

Looks like emacs +x11 is linking against Xaw3d instead of Xaw, which surprises me.

BTW, emacs +gtk is also an option.

[ryandesign@…]

Xaw3d does not build universal because it does not have a universal variant. But it does build just fine x86_64 for me on my system. And I think it did on your system too. The output you attached shows:

ld: warning: in /opt/local/lib/libXaw3d.dylib, file was built for unsupported file format which is not the architecture being linked (i386)

That means you are currently trying to build something i386 (the i386 part of emacs' +universal variant) but libXaw3d.dylib does not contain that architecture (it only contains x86_64).

So it appears that emacs +x11 tries to use Xaw3d, though no dependency on it is declared. A dependency needs to thus either be added somewhere (and the universal variant of that something then disabled), or it needs to not use Xaw3d.

[dports@…]

It looks like emacs+x11 only requires Xaw (hence the dependency) but looks for and uses Xaw3d if it's available. I'll pass it --without-xaw3d to stop that, assuming it works.

[dports@…]

Replying to dports@…:

It looks like emacs+x11 only requires Xaw (hence the dependency) but looks for and uses Xaw3d if it's available. I'll pass it --without-xaw3d to stop that, assuming it works.

Done in r69381.

And did the same for emacs22 in r69383, albeit via a somewhat more forceful means because it didn't support --disable-xaw3d.