Mathieu Bouchard wrote on 3/26/05:
I have a question for you: how should be handled the situation that an executable ruby source file starts with the line "#!/usr/bin/env ruby" ?
Thanks for the information Mathieu!
As for the above, I'd give a not-very-experienced-with-Linux answer.
I encountered this problem right off and the error appeared on the console. It was pretty obvious that configure wasn't finding ruby, which I had just installed, so the question became why.
Doing a find on ruby quickly revealed where it was and that it was called ruby1.8, so the likely fix was to change the line to:
#! /usr/bin/env ruby1.8
...and that worked.
So, in short, I'd leave it alone. I'd assume most people that are capable of compiling a source package should be able to deal with this issue. Otherwise I guess you have to write a little shell script that would go out and find ruby and paste the correct name in the file...
Best,
Charles