Solaris 10


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Solaris 10
# 8  
Old 08-02-2007
just add

PATH=${PATH}:/opt/SUNWspro/bin

to your .profile or the config file you have for your user. if ss is installed in an other path you have to put the right path to the statement above Smilie
 
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies

2. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

3. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

4. Solaris

application compiled on solaris 10 throwing error when executed on solaris 9

I have compiled my application on Solaris 10 with following description SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320 The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 But when installing the application on Solaris 9 SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies
Login or Register to Ask a Question
BUILDER-CC(1)							 Debian GNU/Linux						     BUILDER-CC(1)

NAME
builder-cc - gcc wrapper to facilitate pentium-optimizations SYNOPSIS
export DEBIAN_BUILDARCH=architecture export DEBIAN_BUILDGCCVER=gcc-version gcc ... DESCRIPTION
The builder-cc wrapper is normally used by calling gcc as usual. If the environment variable DEBIAN_BUILDARCH is not set, builder-cc does nothing, and the real gcc is invoked with the specified arguments. When the DEBIAN_BUILDARCH environment variable is set, builder-cc invokes gcc with the specified arguments, plus -mcpu=DEBIAN_BUILDARCH -march=DEBIAN_BUILDARCH This has the effect of telling gcc to use architecture-specific optimizations without changing the command line. This is particularly useful for package builds. If DEBIAN_BUILDGCCVER is not set, builder-cc calls gcc.real. If DEBIAN_BUILDGCCVER is set, builder-cc calls gcc-DEBIAN_BUILDGCCVER instead. ENVIRONMENT
DEBIAN_BUILDARCH If set, the architecture to compile for. Useful values are pentium or pentiumpro. DEBIAN_BUILDGCCVER If set, the version of gcc to be invoked. Useful values are 3.0 or 2.95. NOTES
The real gcc is renamed gcc.real, and a diversion is registered with dpkg-divert(1). Thus builder-cc's idea of the default gcc is dictated by whatever package installed /usr/bin/gcc. SEE ALSO
gcc(1) Debian Project 2002-03-02 BUILDER-CC(1)