Bug 8327 - ironpython scripts in 3.0.1 build are broken
Summary: ironpython scripts in 3.0.1 build are broken
Alias: None
Product: Runtime
Classification: Mono
Component: packaging ()
Version: unspecified
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Duncan Mak
Depends on:
Reported: 2012-11-10 13:00 UTC by Bob Tolbert
Modified: 2013-09-08 18:47 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Bob Tolbert 2012-11-10 13:00:20 UTC
Actual OS: 10.8.2
Mono installer: MonoFramework-MDK-3.0.1.macos10.xamarin.x86.dmg (downloaded today, 11/10/12)

The ipy* scripts in the 3.0.1 beta installer are broken.

the shipped script is:

$ cat /usr/bin/ipy
exec /Library/Frameworks/Mono.framework/Versions/3.0.1/bin/mono /Library/Frameworks/Mono.framework/Versions/3.0.1/lib/ironpython/bin/ipy.exe "$@"

Note the "bin" in the path to the ipy.exe in the Framework. There is no "bin" directory so the actual script should be:

$ cat /usr/bin/ipy
exec /Library/Frameworks/Mono.framework/Versions/3.0.1/bin/mono /Library/Frameworks/Mono.framework/Versions/3.0.1/lib/ironpython/ipy.exe "$@"

The exact same bug appears in ipy64.exe, ipyw.exe and ipyw64.exe
Comment 1 Rodrigo Kumpera 2013-09-08 18:47:01 UTC
This has been fixed since 3.1.1.