As an aside, has gcc already moved to /usr/bin?

One nagging thought about moving the compilers to /usr/bin is that it 
seems to give a level of precedence to the GNU compilers and tools that 
is higher than we offer for our *own* tools (Studio).

I.e. if gdb and gcc are in /usr/bin, then why not dbx and cc?

I realize that this may not be the place to fully explore the idea of 
bundling Studio, but I'd hate for other parties to miscontrue this 
action as meaning our own Studio tools were "2nd class" on Solaris systems.

    -- Garrett

Don Cragun wrote:
> I am submitting this case for April Chin.
> It seeks a minor release binding.
>
> I believe it qualifies for self review and am marking it closed
> approved.  If anyone disagrees, let me know and I will change it to a
> fast track with the normal one week timer.
>
> Cheers,
> Don
>
> Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
> This information is Copyright 2007 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        Move gdb from /usr/sfw/bin to /usr/bin
>     1.2. Name of Document Author/Supplier:
>        Author:  April Chin
>     1.3  Date of This Document:
>       01 November, 2007
> 4. Technical Description
>
> 4.1 Summary
>
>       The GNU debugger, gdb, was initially introduced into Solaris with 
>       PSARC/2005/423 Add g77, gdb and autoconf to WOS
>
>       This project moves the gdb binary from /usr/sfw/bin to /usr/bin
>       and moves the gdb manpage from /usr/sfw/share/man to /usr/share/man.
>
> 4.2 Details
>
>       /usr/sfw/bin/gdb will move to /usr/bin/gdb.  A symbolic link
>       will be left behind from /usr/sfw/bin/gdb to the new location.
>
>       The manpage /usr/sfw/share/man/man1/gdb.1 will move to
>       /usr/share/man/man1/gdb.1.
>
>
> 5. References
>       PSARC/2005/423 Add g77, gdb and autoconf to WOS
>         PSARC 2007/345 Move GNU make to /usr/bin
>         PSARC 2004/742 Move gcc, gnumake, binutils and bison from CCD to WOS
>         PSARC 2005/185 Enabling Serendipitous Discovery
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               SFW
>     6.5. ARC review type: Automatic
>     6.6. ARC Exposure: open
>
>   


Reply via email to