Hi,
Shouldn't GCC be installed into /usr/gnu and then linked back into /usr/bin,
/usr/lib, etc?
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Virtualization Architect and Consultant
Web: http://unixconsole.blogspot.com
E-Mail:
Suhasini Peddada wrote:
Hello All,
Here are the AI's from today's inception review of PSARC 2009/471.
Please let me know, in case any corrections/modifications are required:
1) Investigate whether JSON is better than XML for the manifest.
Some things to be aware of with JSON:
* doesn't
Raj Prakash Raj.Prakash at sun.com writes:
2. Project Summary
2.1. Project Description:
Provide GCC 4.X and allow for the coexistence of multiple
versions of GCC installed simultaneously.
GCC 3.4.3, the current build compiler for OpenSolaris and
Nevada, will
SYSTEM ARCHITECTURE COUNCIL
Platform Software ARC
-
PSARC Regular Meeting time: Wednesdays 10:00-1:00pm in MPK17-3507.
10-21-2009 MEETING MINUTES
Octave Orgeron wrote:
Hi,
Shouldn't GCC be installed into /usr/gnu and then linked back into /usr/bin,
/usr/lib, etc?
No. The rules for /usr/gnu/bin are that a binary only needs to go there
if its normal name clashes with an existing entry in /usr/bin that it
can not completely (ie
On 10/22/09, Alan Coopersmith Alan.Coopersmith at sun.com wrote:
You really need both 4.3.2 4.3.3? You don't believe even
micro releases are not safe or compatible upgrades?That's
just sad, and somewhat inconsistent with every other distro/OS
shipping gcc I've seen. (3.4.3 vs.
Raj, I can't find libdecnumber.so in the case materials. Are you
disabling decimal floating point support on Solaris?
On 10/22/09, Raj Prakash Raj.Prakash at sun.com wrote:
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Wyllys Ingersoll wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
pam_krb5 PKINIT support
1.2. Name of Document Author/Supplier:
Author: Will Fiveash
http://www.opensolaris.org/os/community/arc/announcements/
OpenSolaris ARC Agenda
TELECONFERENCE NUMBERS:
(866)545-5223 (Within US)
(215) 446-3661 (International)
ACCESS CODE 939-55-86
Times are US/Pacific Timezone
ARC meetings are recorded.
10/27/2009
No meeting
10/28/2009
I'm sponsoring this case for Renee Danson Sommerfeld, it times out on
10/29/2009. The release binding for this case is the same as the case
that it updates (PSARC 2008/532 NWAM Phase 1), namely Minor release
binding.
In the course of completing the implementation of NWAM Phase 1, several
=?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= olga.kryzhanovska at gmail.com writes:
In my option shipping both 4.3.3 and 4.3.2 is wasted time. 4.3.3 is a
bug fix only update to 4.3.2. You better invest the time in shipping
Indeed, and there exists even 4.3.4 by now.
the Ada frontend and runtime
=?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= olga.kryzhanovska at gmail.com writes:
Raj, I can't find libdecnumber.so in the case materials. Are you
disabling decimal floating point support on Solaris?
No, this is only enabled on specific platforms, but disabled by default. I
haven't yet tried if it
On Thu, Oct 22, 2009 at 01:40:11PM -0400, Sebastien Roy wrote:
* Add option to list subcommand, '-x', which includes explanation of state
Why -x and not -v or -xv or anything more in keeping with other Solaris
commands?
4. Add '-V' option to nwamcfg's 'get' subcommand
Default output
Nicolas Williams wrote:
On Thu, Oct 22, 2009 at 01:40:11PM -0400, Sebastien Roy wrote:
* Add option to list subcommand, '-x', which includes explanation of
state
Why -x and not -v or -xv or anything more in keeping with other Solaris
commands?
-x is in keeping with other Solaris
On Thu, Oct 22, 2009 at 07:47:29PM +0100, Darren J Moffat wrote:
Nicolas Williams wrote:
On Thu, Oct 22, 2009 at 01:40:11PM -0400, Sebastien Roy wrote:
* Add option to list subcommand, '-x', which includes explanation of
state
Why -x and not -v or -xv or anything more in keeping
Alan Coopersmith wrote:
You really need both 4.3.2 4.3.3?
My first choice would have been to replace the current gcc 3.4.3 with
gcc 4.X and simply called it gcc. However, gcc 3.4.3 is part of the
Solaris build environment and we must keep it until Solaris moves to a
newer version of gcc.
I'm filing the following case to clean up some software which _probably_
should have been removed along with the SPARCLE support (PSARC 2008/538).
In theory, the software could be useful to other SPARC platforms, but
no such platforms exist today, and none are anticipated, which is why
I'm filing
I forgot to mention: this is patch binding. The actual objects I'd
remove would be:
/kernel/drv/sparcv9/sdcard
/kernel/drv/sparcv9/sdhost
/kernel/misc/sparcv9/sda
These are contained in the SUNWsdcard package, which would also be
removed from SPARC.
- Garrett
Garrett D'Amore - sun
On Thu, Oct 22, 2009 at 01:37:13PM -0700, George Vasick wrote:
Alan Coopersmith wrote:
You really need both 4.3.2 4.3.3?
Solaris freezes on a specific release for its build compiler. What
happens when they are on 4.x.y and we want to release 4.x.z?
Just because the ONNV and/or other
George Vasick George.Vasick at sun.com writes:
Alan Coopersmith wrote:
You really need both 4.3.2 4.3.3?
My first choice would have been to replace the current gcc 3.4.3 with
gcc 4.X and simply called it gcc. However, gcc 3.4.3 is part of the
Solaris build environment and we must keep
Raj Prakash wrote:
usr/share/man/man7
usr/share/man/man7/fsf-funding.7
usr/share/man/man7/gfdl.7
usr/share/man/man7/gpl.7
Since those are not device drivers, the miscellaneous topics man pages
belong in section 5 on SysV-based platforms like Solaris, instead of
the
Alan Coopersmith wrote:
George Vasick wrote:
We released 4.3.2 in OpenSolaris 2009.06. We have to update 4.3.2 in
order to release 4.3.3 to avoid duplicate pathnames between the packages.
The case specified 4.3.2 as a new delivery, not something already provided.
Sorry about that. Here is
Rainer Orth wrote:
George Vasick George.Vasick at sun.com writes:
We released 4.3.2 in OpenSolaris 2009.06. We have to update 4.3.2 in
order to release 4.3.3 to avoid duplicate pathnames between the packages.
Is this relevant at all? Has this ever been ARCed? If not, it might as
well
Nicolas Williams wrote:
On Thu, Oct 22, 2009 at 01:37:13PM -0700, George Vasick wrote:
Alan Coopersmith wrote:
You really need both 4.3.2 4.3.3?
Solaris freezes on a specific release for its build compiler. What
happens when they are on 4.x.y and we want to release 4.x.z?
Just because
Date: Thu, 22 Oct 2009 13:40:11 -0400
From: Sebastien Roy Sebastien.Roy at sun.com
Subject: Network Auto-Magic (NWAM) Phase 1 Updates [PSARC/2009/577
FastTrack timeout 10/29/2009]
...
4. Add '-V' option to nwamcfg's 'get' subcommand
Default output from the
Didn't we have this very same coexistence conversation the first time
'round? :-)
The use case of the user installing gcc 4.3.2 yesterday, installing
gcc 4.3.3 today, and then uninstalling gcc 4.3.2 tomorrow is going
to be a reasonably common upgrade path; whatever causes the havoc to
both the
Rainer Orth wrote:
George Vasick George.Vasick at sun.com writes:
Alan Coopersmith wrote:
You really need both 4.3.2 4.3.3?
My first choice would have been to replace the current gcc 3.4.3 with
gcc 4.X and simply called it gcc. However, gcc 3.4.3 is part of the
Solaris build
Darren J Moffat wrote:
Wyllys Ingersoll wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
pam_krb5 PKINIT support
1.2. Name of Document Author/Supplier:
This case was approved at yesterday's meeting.
--matt
Matthew Ahrens wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
ZFS send dedup
1.2. Name of Document
On Thu, Oct 22, 2009 at 05:40:47PM +0100, Darren Moffat wrote:
Wyllys Ingersoll wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
pam_krb5 PKINIT support
On Thu, Oct 22, 2009 at 03:38:29PM -0500, Douglas E. Engert wrote:
Darren J Moffat wrote:
Wyllys Ingersoll wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
George Vasick wrote:
Yes, you are 100% corrected on the studio side. For gcc, the build uses
the compiler installed on the live system. I don't know why the two are
handled differently. We do need to accommodate Solaris builds, however.
They are one of our important users.
This is easy
32 matches
Mail list logo
