logo       

Bad extconf.rb (Was: Trackker): msg#00041

lang.ruby.gems.devel

Subject: Bad extconf.rb (Was: Trackker)

On Dec 18, 2006, at 14:18, Eric Hodel wrote:
> On Dec 16, 2006, at 08:54, Chad Fowler wrote:
>> Eric, are you aware of fixing
>> http://rubyforge.org/tracker/index.php?
>> func=detail&aid=982&group_id=126&atid=575.
>> It looks like you did. I added a test i expected to fail and it
>> passed. Looks like svn has the desired behavior now.
>
> I don't remember fixing it. If it is fixed go ahead and close the
> bug.

Actually, this isn't our bug.

Gem authors like to write broken extconf.rbs where they don't check
the output of #have_library or #have_header (or whatever the header
one is) so they'll build a Makefile when they shouldn't.

There's really nothing we can do about this.

If the C code is bad or the extconf.rb doesn't write a Makefile then
things are good.

--
Eric Hodel - drbrain-48TerJ1FxhPk1uMJSBkQmQ@xxxxxxxxxxxxxxxx -
http://blog.segment7.net

I LIT YOUR GEM ON FIRE!


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise