Bug 13627 - mono runtime symlink points to a wrong path
Summary: mono runtime symlink points to a wrong path
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: packaging ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-30 16:17 UTC by Nikita Tsukanov
Modified: 2016-03-01 13:12 UTC (History)
4 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Nikita Tsukanov 2013-07-30 16:17:50 UTC
Hello. When I run make install with DESTDIR option, it creates symlink to a wrong path. For example

$ ls /opt/mono-3/bin/mono -la
lrwxrwxrwx 1 root root 65 июля  30 23:52 /opt/mono-3/bin/mono -> /tmp/mono32/mono-3.2.0/debian/mono-3-opt/opt/mono-3/bin/mono-sgen

As you can see /opt/mono-3/bin/mono points to /tmp/mono32/mono-3.2.0/debian/mono-3-opt/opt/mono-3/bin/mono-sgen instead of /opt/mono-3/bin/mono-sgen
Comment 1 Zoltan Varga 2013-07-30 18:12:31 UTC
That seems to be linux only, it works fine on osx.
Comment 2 Alexander Köplinger [MSFT] 2016-03-01 13:12:01 UTC
This seems to be fixed now.