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

Clearly your ncurses library is built for the wrong architecture. If your ncurses port had been installed with MacPorts 1.9 or later, MacPorts would have noticed this and rebuilt ncurses universal. Since it did not, that suggests your ncurses port was installed with MacPorts 1.8 or earlier, which predates Lion. This in turn suggests that it was installed before you upgraded to Lion, and that when you upgraded to Lion you did not follow the Migration procedure.

Clearly your ncurses library is built for the wrong architecture. If your ncurses port had been installed with MacPorts 1.9 or later, MacPorts would have noticed this and rebuilt ncurses universal. Since it did not, that suggests your ncurses port was installed with MacPorts 1.8 or earlier, which predates Lion. This in turn suggests that it was installed before you upgraded to Lion, and that when you upgraded to Lion you did not follow the Migration procedure.

I thought I only installed MacPorts after I installed Lion, but apparently there was still an old version on my disk. Thanks for pointing out the problem. I uninstalled and reinstalled all packages, and now also get a segfault while building.

Clearly your ncurses library is built for the wrong architecture. If your ncurses port had been installed with MacPorts 1.9 or later, MacPorts would have noticed this and rebuilt ncurses universal. Since it did not, that suggests your ncurses port was installed with MacPorts 1.8 or earlier, which predates Lion. This in turn suggests that it was installed before you upgraded to Lion, and that when you upgraded to Lion you did not follow the Migration procedure.

I thought I only installed MacPorts after I installed Lion, but apparently there was still an old version on my disk. Thanks for pointing out the problem. I uninstalled and reinstalled all packages, and now also get a segfault while building.

Just curious, what did you do exactly? I uninstalled _everything_ that I could think of (I have Macports 2.0.2) and it still doesn't work. Could you please paste the commands as to how you resolved the issue here?

Just curious, what did you do exactly? I uninstalled _everything_ that I could think of (I have Macports 2.0.2) and it still doesn't work. Could you please paste the commands as to how you resolved the issue here?

Reinstall Macports and maybe Xcode (though you probably did this already), then use these commands and reinstall everything you need that is listed in myports.txt as it says on the Migration page which ryandesign@… mentioned. Good luck.

Silly question. Never done this before... but how do I uninstall in a Mac?

Well, that depends on what you want to uninstall. For ordinary Mac OS X apps, you drag them from /Applications/ to the trash bin, and then empty the trash bin. But for Unix-y things, including Xcode and its suite of command line tools, you have to uninstall them in more Unix-y ways. I actually reinstalled Xcode myself after installing Lion, and that involved something like this:
​http://macdevelopertips.com/xcode/how-to-uninstall-xcode.html

Ok, I re-installed Xcode, I nuked from orbit MacPorts (even removed some of the directories that the guide said about uninstalling MacPorts), re-installed (from source) MacPorts and am trying to install CLisp.

And... there seems to be a different problem. The install hasn't failed, but when it gets to the part about "Building clisp" it takes forever. It's been about 30 minutes and it's still there. Is this normal?

Remember to use WikiFormatting please. I doubt you are seeing a similar error with gcc46. Please open a new ticket about gcc46 and attach gcc46's main.log there (if no existing gcc46 bug report is applicable, but check for example #31171).

Remember to use WikiFormatting please. I doubt you are seeing a similar error with gcc46. Please open a new ticket about gcc46 and attach gcc46's main.log there (if no existing gcc46 bug report is applicable, but check for example #31171).

joaomlneto, you don't need to attach two logs for the same problem; one log, the main.log, is sufficient. In your logs I see a segmentation fault, similar to what was reported earlier in the ticket, and I requested people report that to the developers of clisp. Have you done that? What did they say?

joaomlneto, you don't need to attach two logs for the same problem; one log, the main.log, is sufficient. In your logs I see a segmentation fault, similar to what was reported earlier in the ticket, and I requested people report that to the developers of clisp. Have you done that? What did they say?

Sorry, I overlooked the file contents, just compared their size and decided I should send you pretty much everything. Sorry :)
I also didn't see your indications to submit the files to clisp devs.

I saw the bug report from shaktool, not sure if I should add anything to it... :)

I patched the file /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/clisp/Portfile but unfortunately I again get a segmentation fault. Still I think the output was different than the previous time so will attach it.