Brewing glib is wonky.

[homebrew]

Brewing glib is wonky.

[mxcl]

I believe the GUI popups are unavoidable, I've seen it outside of Homebrew, it's usually fine. Configure does a lot of stuff and plenty of it is writing little programs that crash, and the crash means the configure failed. etc.

But indeed, I don't think glib and gettext are building yet, or if they are, it's badly. I added them a long time ago because I wanted wireshark and it wasn't easy so I just commited what was there.

I'll check them out again, I'm sure we'll get to the bottom of it.

I'll leave this open when we finish anyway because the GUI popups suck and maybe there is a solution. I gotta say, I never saw it with macports.

[adamv]

More info, brewing wget is similarly wonky. It's the configure's use of xgettext, which links lib-gettext-something, which defines an extern char ** _environ which doesn't exist on OS X. Some sort of patch to gettext might be in order, if we want to "go there"; I don't particularly want to go there, so much as being able to brew wget. (I suspect that if I didn't have gettext installed, then wget would brew fine and just not use gettext...)

[mxcl]

This I don't get as I can brew both wget and glib just fine, although I do get the GUI popup error -- but it doesn't stop the brew.

Do they brew successfully if you remove GNU gettext?

[adamv]

So it turns out that, for me at least, a ton of stuff breaks during compile if gettext is linked, and works if I unlink it first (but then have to remember to re-link it for sshfs.) The errors seem entirely due to the xgettext and msgfmt helper apps being invoked doing ./configure or make or make install.

[mxcl]

I think it's clear we need to keep gettext unlinked by default. Handy that Homebrew can do this :) Wonder what Macports does?

[adamv]

This patch fixed the issue for me on 10.5 and 10.6. Woot!
http://github.com/drodriguez/homebrew/commit/b653545603d1d823ebf524f9cb0e040cf39dd050