Having lurked following this discussion, here are my $0.02.
I don't understand why a solution
similar to the multiple jdks would not be applicable and appropriate
here.
What John P stated in a previous follow up was the closest to that.
/usr/suncc/
[version1]/
bin/
lib/
[version2]
bin/
lib/
All binaries in bin/ would be compiled with a relative RPATH pointing
at items in their respective lib/.
Users wanting access to a specific version would just have to point
at the specific one.
We could even accomodate SPRO, GCC 'latest' links in the same manner
that the jdk deals with.
/usr/suncc/
gcc-latest ---> ./[version2]
spro-latest ---> ./[version1]
[version1]/
bin/
lib/
[version2]
bin/
lib/
Arieh
On Jan 23, 2009, at 1:54 AM, Nicolas Williams wrote:
> On Thu, Jan 22, 2009 at 03:47:34PM -0800, Danek Duvall wrote:
>> On Thu, Jan 22, 2009 at 05:33:45PM -0600, Nicolas Williams wrote:
>>
>>> On Thu, Jan 22, 2009 at 06:28:32PM -0500, Dale Ghent wrote:
>>>> On Jan 22, 2009, at 4:17 PM, David.Ford at sun.com wrote:
>>>>
>>>>> May I suggest /usr/suncc (short for Sun
>>>>> Compiler Collection).
>>>>
>>>> I like that.
>>>
>>> I think I just wrested a concession, that a directory under /usr
>>> is not
>>> needed. A directory under /usr/lib, with symlinks from /usr/bin,
>>> should
>>> do until the i-team is able to spread the bundled bits into the
>>> correct
>>> locations.
>>
>> Except that in a parallel thread, Chris told us that there's a bin
>> directory that users will have to access, as not all things that
>> are there
>> will have symlinks in /usr/bin (such as "version"). Yes, that
>> could be
>> /usr/lib/suncc/bin, but is that better than /usr/suncc/bin?
>
> Oh well. I tried :) So count me in favor of /usr/suncc.
Arieh Markel Sun Microsystems, Inc.
xVM - Virtualization Management 9 Hamenofim St. 8th Floor. MS
ETLV04
e-mail: arieh.markel at sun.COM Herzliya Pituach, Israel
http://blogs.sun.com/arieh Phone: +972-9-971-1291 (70)
x12291
Mobile: +972-54-238-2771
