iTerm: build fail

[nefar@…]

See attached log

[nefar@…]

build log

[andreas.wilm@…]

Cc Me!

[deesto (John S. De Stefano Jr.)]

this was last touched 12 months ago ... is it still being worked on?

[deesto (John S. De Stefano Jr.)]

Cc Me!

[jasny@…]

Hi,

version 0.9.6 fails to build, too. Unfortunately the latest iTerm release (v0.10.0) has no SVN version tag.

I've files an upstream bug report: ​https://sourceforge.net/tracker/?func=detail&aid=3034309&group_id=67789&atid=518973

Thanks, Gregor

[jasny@…]

Cc Me!

[deesto (John S. De Stefano Jr.)]

It appears that the iTerm project has been abandoned, and forked to an iTerm2 project: ​http://code.google.com/p/iterm2/ Perhaps this port should be updated to point to iTerm2, or closed?

[ygramul.el.multiple@…]

Cc Me!

[ygramul.el.multiple@…]

Same problem with me!

The following build commands failed:
Growl:
	CompileC build/iTerm.build/Deployment/Growl.build/Objects-normal/i386/CFGrowlAdditions.o /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_iTerm/work/RC_0_9_6/Growl/CFGrowlAdditions.c normal i386 c com.apple.compilers.gcc.4_0
iTerm Framework:
	Ld /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_iTerm/work/RC_0_9_6/build/Deployment/iTerm.framework/Versions/A/iTerm normal i386
iTerm:
	Ld /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_iTerm/work/RC_0_9_6/build/Deployment/iTerm.app/Contents/MacOS/iTerm normal i386
(3 failures)

I attach the log file. My system is Mac OS X 10.5.8 and my Xcode version is 3.1.2

[ygramul.el.multiple@…]

iTerm log

[ygramul.el.multiple@…]

Well, it seems that this ticket is a little bit abandoned... it would be nice if a iTerm2 port is created when they exit the alpha phase, it seems a rather active project. Just as an interesting information, I downloaded the iTerm 0.10 from the iTerm site, unpacked it and moved to Applications, and it's working veery smoothly. This cannot be permanent solution, but for a few months it can be all right.

[nefar@…]

I move to just remove iTerm in favor of iTerm2. iTerm is really worthless. It's too slow to be of any use. I've been using iTerm2 since the recent redraw rewrite (it too was too slow before) and it has replaced Terminal.app for me.

Also, if no one is going to take the time to fix iTerm, it's another reason to just remove the port.

[ygramul.el.multiple@…]

I agree with you, a port which doesn't build is not very useful... has any of you filed a "request" ticket for iTerm2?

And about iTerm2: is it stable enough, being still an alpha?

[nefar@…]

I've not filed a request ticket.

I've been using it almost exclusively for the past few weeks. It has some rendering issue in finch, but otherwise I've seen nothing wrong and I use terminal all day for work.

however, I don't see an issue with just removing this port and waiting until iterm2 has been officially released

[ygramul.el.multiple@…]

I agree with you.

[nefar@…]

Cc Me!

[julien.cornebise@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

error: c.h: No such file or directory

I see the same with version 0.10 (0.10.x branch, revision 1871). I find a "c.h" on my system in /Developer/SDKs/MacOSX10.4u.sdk/usr/include/c.h but it doesn't seem to be in the 10.5 or 10.6 SDKs.

[ryandesign (Ryan Carsten Schmidt)]

patch to update to 0.10 which does not fix the problem

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #32610.

[ryandesign (Ryan Carsten Schmidt)]

waqar has retired.

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

Since iTerm has been abandoned by the authors and it doesn't build on any of the 4 OSes macports uses, I obsoleted this port in favor of iTerm2