qucs fails from iverilog arch issues

[Jean-François Caron]

So three years ago this bug was opened: https://trac.macports.org/ticket/27520

The latest modifications are from 8 months ago.  The problem still persists:

fcaron at dhcp-128-189-75-8:~$ sudo port install qucs
Password:
--->  Computing dependencies for qucs
Error: Cannot install qucs for the arch(s) 'i386' because
Error: its dependency iverilog does not build for the required arch(s) by default
Error: and does not have a universal variant.
Error: Unable to execute port: architecture mismatch

I tried a variant on the reported workaround with "build_arch=x86_64", but qucs still tries to build for i386 (meaning that the port has a bug since it ignores the build_arch flag).  

I tried the same workaround as in the bug report, building iverilog with "build_arch=i386" and THEN qucs.  A problem occurs when configuring qt3-mac: 
--->  Configuring qt3-mac
Error: org.macports.configure for port qt3-mac returned: configure failure: command execution failed
Error: Failed to install qt3-mac
Here is the log file from that, but the important part is "This version of Mac OS X is unsupported."  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.log
Type: application/octet-stream
Size: 24867 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130930/f905d377/attachment.obj>
-------------- next part --------------


I am on a MacBook Pro (Late 2011), running Mac OS X 10.7.5, MacPorts 2.2.0, XCode 4.5.1 (4G1004).

Is this port abandoned?  The latest binary on their website seem to be for OSX 10.5 only (they crash immediately when running, with no useful debug messages):
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qucslog.log
Type: application/octet-stream
Size: 3157 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130930/f905d377/attachment-0001.obj>
-------------- next part --------------


If the program just isn't intended to work on 10.7 (or other new OSXes), then the user should be told this earlier in the process.

Jean-Fran?ois