usmanhu14 / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

gen_bridge_metadata can fail if ruby is not /usr/bin/ruby #355

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Steps to reproduce:
1. Install a copy of ruby in addition to the system-provided one (e.g. with 
MacPorts)
2. Make the new ruby come first in PATH
3. Try to build MacFUSE

Expected result: MacFUSE builds successfully
Actual result: build fails with an error like "Usage: gen_bridge_metadata 
[options] <headers...>"

MacFUSE version: 1.5.1
Operating System: Mac OS X 10.5.2

Additional information: This happens because gen_bridge_metadata is a ruby 
script that starts 
with "#!/usr/bin/env ruby". Invoking it with "/usr/bin/ruby 
$GEN_BRIDGE_METADATA" instead of 
just "$GEN_BRIDGE_METADATA" is an effective workaround.

This issue was originally reported in this MacPorts ticket: 
<http://trac.macports.org/ticket/15284>

Original issue reported on code.google.com by joshua.r...@gmail.com on 24 May 2008 at 9:51

Attachments:

GoogleCodeExporter commented 8 years ago
> Invoking it with "/usr/bin/ruby $GEN_BRIDGE_METADATA" instead of 
> just "$GEN_BRIDGE_METADATA" is an effective workaround.

Who guarantees that gen_bridge_metadata will always be a ruby script? It's an 
Apple-provided tool; MacFUSE is 
merely calling it.

Why is the workaround needed? Shouldn't the "new ruby" have at least the same 
functionality as /usr/bin/ruby?

Original comment by si...@gmail.com on 24 May 2008 at 6:20

GoogleCodeExporter commented 8 years ago
> Who guarantees that gen_bridge_metadata will always be a ruby script? It's an 
Apple-provided tool;
> MacFUSE is merely calling it.

Right, the real fix is for Apple to change the shebang line.

> Why is the workaround needed?

I don't know. I've only empirically observed that my build fails without it and 
works with it.

> Shouldn't the "new ruby" have at least the same functionality as 
/usr/bin/ruby?

It looks like Apple ships a bunch of gems that are not part of the basic Ruby 
package.

Original comment by joshua.r...@gmail.com on 25 May 2008 at 9:45

GoogleCodeExporter commented 8 years ago
Right, so changing this in MacFUSE is not a good solution.

Original comment by si...@gmail.com on 25 May 2008 at 5:29