xchat does not compile when building fe-gtk dependency

[dmsmith555@…]

I tried to build "port install xchat" and it fails with the following error, which seems to be a problem with fe-gtk. Here is the output (The other, prior dependencies built fine): $ sudo port install xchat Password: ---> Building xchat with target all Error: Target com.apple.build returned: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_irc_xchat/work/xchat-1.8.11" && make all" returned error 2 Command output: make all-recursive Making all in po Making all in intl make[2]: Nothing to be done for `all'. Making all in src Making all in common make[3]: Nothing to be done for `all'. Making all in fe-gtk gcc -I/opt/local/include -I/opt/local/include/glib-1.2 -I/opt/local/include/gtk-1.2 -I/opt/local/lib/glib/include -I/usr/X11R6/include -Wall -g -c test -f 'mmx_cmod.S' || echo './'mmx_cmod.S mmx_cmod.S:38:Unknown pseudo-op: .global mmx_cmod.S:38:Rest of line ignored. 1st junk character valued 115 (s). mmx_cmod.S:39:Unknown pseudo-op: .type mmx_cmod.S:39:Rest of line ignored. 1st junk character valued 115 (s). mmx_cmod.S:40:Unknown pseudo-op: .global mmx_cmod.S:40:Rest of line ignored. 1st junk character valued 115 (s). mmx_cmod.S:41:Unknown pseudo-op: .type mmx_cmod.S:41:Rest of line ignored. 1st junk character valued 115 (s). mmx_cmod.S:42:Unknown pseudo-op: .global mmx_cmod.S:42:Rest of line ignored. 1st junk character valued 115 (s). mmx_cmod.S:43:Unknown pseudo-op: .type mmx_cmod.S:43:Rest of line ignored. 1st junk character valued 115 (s). mmx_cmod.S:44:Unknown pseudo-op: .global mmx_cmod.S:44:Rest of line ignored. 1st junk character valued 104 (h). mmx_cmod.S:45:Unknown pseudo-op: .type mmx_cmod.S:45:Rest of line ignored. 1st junk character valued 104 (h). mmx_cmod.S:47:Unknown pseudo-op: .bss make[3]: * [mmx_cmod.o] Error 1 make[2]: * [all-recursive] Error 1 make[1]: * [all-recursive] Error 1 make: * [all] Error 2

Error: /opt/local/bin/port: Status 1 encountered during processing.

[mij@…]

Is there any particular reason you're using the xchat port instead of the xchat2 port? In all honestly, the xchat port should probably be nuked...

[dmsmith555@…]

I was not at all aware of the xchat2 port. I might have found it if I didn't find xchat.

I think nuking it would be a fine resolution!