Failed executing: make while installing Fontforge

[ghost]

To be short, the error I've got while install fontforge using brew shows: Error: Failed executing: make (fontforge.rb:38)
and the brew install -v fontforge --use-gccshows here

And here are some details:

I've brew update and brew upgrade
the brew doctor shows one warning and honestly I don't know how to deal with that:

Warning: "config" scripts exist outside your system or Homebrew directories.
.......

    /Users/iceX/.rvm/gems/ruby-1.9.3-p125/bin/passenger-config

And I'm running the latest Xcode download from App Store and have both Command Line Tools and Java Developer updated to the latest version, and have done sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

Never installed Macports, Fink before or OSX-GCC-installer

I've done sudo chown -R iceX /usr/local and sudo chown -R iceX /usr/local/.git

Besides, I've tried brew install fontforge --use-gcc and brew install fontforge --use-clang and both led to Error: Failed executing: make (fontforge.rb:38)

Even more info:

I've brew install automake
and brew install apple-gcc42 which solved the GCC could not be found problem.

And the gcc --version shows

i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.9.00)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

which make shows /usr/bin/make

Nothing showed up after brew list --unbrewed | egrep '^(lib|include)'

[2bits]

You can safely remove the gcc you brewed. It should not be needed.
Did you ever install ruby? The output you provided refers to one, v.1.9.3.
I'm fairly certain that Homebrew is only designed to run with the system ruby:

$ ruby --version
ruby 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]

After you remove the gcc and ruby, you should get better results when you brew install -vd fontforge
Let us know how it goes. If you still have problems at that point, gist your brew --config and the output
from the install command.

[ghost]

well… something seems still not right.

so, as you've suggested, I did the following things:
brew remove apple-gcc42
brew updatebrew upgrade

then
rvm use system and ruby -vlooks good:
ruby 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]

and brew doctorcomplains nothing.

then brew install fontforge --use-gccand it says GCC Could not be found.
so, I tried brew install -vd fontforge and here is the result

and brew --config

HOMEBREW_VERSION: 0.9
HEAD: 5ed1927ce36603cfb4dd89377ebaf2ca0e831c80
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: quad-core 64-bit sandybridge
OS X: 10.7.3
Kernel Architecture: x86_64
Xcode: 4.3.2
GCC-4.0: N/A
GCC-4.2: N/A
LLVM: build 2336
Clang: 3.1 build 318
MacPorts or Fink? false
X11: /usr/X11
System Ruby: 1.8.7-249
/usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
Which Perl:   /usr/bin/perl
Which Python: /usr/bin/python
Which Ruby:   /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby

and I've run brew doctor once more but:

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built.

    fontforge

BTW: /usr/local/Cellar/fontforge is emyty now.
And after remove apple-gcc42, I cannot use --use-gcc option anymore, will this be a problem?

[2bits]

You did all the right things. Fontforge has problems that the developer needs to fix. Until that time, Soren has made a patch to fix this issue (other people get it too). The pull request is here: #10714 If you download the raw fontforge.rb from that pull request and save it in your Homebrew Library, you will be able to build Fontforge.

You asked about --use-gcc a couple of times. You should not need to use it to compile any formula in Homebrew, and Apple does not provide it anymore for Lion users as part of the normal XCode-4.3+. That option is left over for Snow Leopard or Leopard users who still have gcc and who might have some special reason to use it.

Because the exact error you now get has been reported in #10572 and fixed in that other one I mentioned, would you be ok with closing this now because it is a duplicate?

[ghost]

Wow, it works now, and really, thank you for your help!
Issue closed :)