SUN WORKSHOP 5

Hello all!! I've tried to install Sun Workshop 5 in a Solaris 6. I've followed the steps in the manual but when I do step number 6 (start workshop install), I type the command and the next error is displayed:
"DISPLAY ERROR: Could not open an X Window display. Please check the setting of your DISPLAY environment variable, and if need be, execute an "xhost" command on this display to grant access. Proper execution of the "xhost" command is documented in your install guide.
If you have become the root user on this display by means of an "su" command, you will likely have to issue an "xhost" command as the owner of the display, not as root. See the install guide for more information on setting "xhost" access prior to becoming root."
I have installed the patch number 106242-02 and I have looked for bad directories in the fonts, but all is ok.
Can anybody help me?
Thanks very much.

Were you installing on another system remotely, and trying to bring
the display screen on this remote machine ? If so, you will have
to run 'xhost +' cmd on this remote machine and set your DISPLAY
variable on the actual machine (where you installed Workshop) to
this remote machine's value.
For example, in C-shell,
setenv DISPLAY hostname.sun.com:0.0 should display all windows on
hostname.sun.com remote machine, instead of actual machine where you
installed the Workshop.
Does this help ?
Thx
Tushar Patel.

Similar Messages

Install Sun Workshop 6 on Solaris 9

Has anyone successfully installed Sun Workshop 6 on a Solaris 9 machine? I checked release notes, and seems like this version does not support solaris 9. Thanks!
KC

By 'Sun Workshop 6'... do you mean Forte Developer 6? If yes, you can only install it on versions 2.6, 7, and 8 of the Solaris O/S.

Sun WorkShop 10 Errors

Hi All,
Thanks to all who helped me to resolve the last error.
Now I am again with some troubles..
I am compiling my code in Sun workshop 10 in Solaris 10
in x86 box.
My CC version is
CC: Sun C++ 5.7 Patch 117831-05 2005/11/11
I am getting the following compile time errors.
CC -c -PIC -DOPTIMAL -I/gsp-dist/blr/developer/pradeepk/tmp/IOP/IOP_Source/src/include -I/usr/dt/include -I/usr/openwin/
include -I. -DSolaris -DSolaris2_10 +w SockXCommon.c -o SockXCommon.o
"/usr/include/sys/signal.h", line 85: Error: siginfo_t is not defined.
"/usr/include/signal.h", line 111: Error: siginfo_t is not defined.
"/usr/include/signal.h", line 113: Error: siginfo_t is not defined.
"/usr/include/signal.h", line 113: Error: There must be an identifier to declare.
"/usr/include/signal.h", line 113: Error: "," expected instead of ")".
"/usr/include/signal.h", line 265: Error: "sigtimedwait(const sigset_t*)" is expected to return a value.
"/usr/include/signal.h", line 113: Warning: The last statement should return a value.
"/opt/SUNWspro/prod/include/CC/./new", line 32: Error: operator new(unsigned) was declared before with a different language.
"/opt/SUNWspro/prod/include/CC/./new", line 35: Error: operator delete(void*) was declared before with a different language.
"/opt/SUNWspro/prod/include/CC/./new", line 37: Error: operator new[](unsigned) was declared before with a different languag
e.
"/opt/SUNWspro/prod/include/CC/./new", line 40: Error: operator delete[](void*) was declared before with a different languag
e.
"/opt/SUNWspro/prod/include/CC/./new", line 53: Error: Only one of a set of overloaded functions can be extern "C".
"/opt/SUNWspro/prod/include/CC/./new", line 54: Error: Only one of a set of overloaded functions can be extern "C".
"/opt/SUNWspro/prod/include/CC/./new", line 55: Error: Only one of a set of overloaded functions can be extern "C".
"/opt/SUNWspro/prod/include/CC/./new", line 56: Error: Only one of a set of overloaded functions can be extern "C".
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 106: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 169: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 185: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 198: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 202: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 206: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 217: Error: Only one of a set of overloaded functions can be extern "
C".
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 225: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 239: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 249: Error: Template declarations cannot have extern "C" linkage.
"/opt/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 264: Error: Template declarations cannot have extern "C" linkage.
Compilation aborted, too many Error messages.
*** Error code 1
make: Fatal error: Command failed for target `SockXCommon.o'
Thanks in advance
Pradeep

I suspect that the IOP directory tree has files that override the system libraries in /usr/include or the compiler's own C++ headers.
Try this: Add -H to the compiler options and direct standard error to a file. The -H option lists the path to every included file, indented to show what file causes an inclusion.
If you find that files with names corresponding to system headers are being picked up from an IOP subdirectory, that is a likely reason for errors like siginfo_t not being defined.
Another possible source of errors is providing declarations of standard templates, types, functions, or data in your own code. User code should never declare standard entities, but include the appropriate standard header instead. The reason is that implementations are allowed some leeway in how standard entities are declared, and the declaration you provide might not match the one provided by the implementation.
Another aid to investigating these problems is to replace the -c option with -E, and direct standard output to a file. The file will show the result of all file inclusions, expand all macros, and show where every line of code comes from. Given an error message about about a declaration, you can scan backwards in the file to find an eariler declarat on that causes the error message.

Compilation error with sun workshop 6u2

hi,
i try to compile a systemc code with sun work shop 6u2 but the compilation generate this error
Beginning generate/compile...
Compilation may take a few seconds... please wait.......ucbcc: Warning: Option -YP,:/usr/ucblib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin/../lib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin:/usr/ccs/lib:/usr/lib passed to ld, if ld is invoked, ignored otherwise
ucbcc: Invalid input file name /home/uei/chtourou/cadence/soflib/fir/pmb/spb.C, no output generated for this file.
ucbcc: Warning: Option -YP,:/usr/ucblib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin/../lib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin:/usr/ccs/lib:/usr/lib passed to ld, if ld is invoked, ignored otherwise
ld: warning: option -YP appears more than once, first setting taken
ld: fatal: file /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.o: cannot open file: No such file or directory
ld: fatal: File processing errors. No output written to /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.so
system-002: Error: The following system command failed.
CC -G -o /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.so /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.o `/home/uei/chtourou/tmp/systemc-2.0.1/spwSystemC/src/libList.csh.${PLATFORM_DIR}` -lc
leaf-057: Error: Failed to compile the SPB wrapper for polymorphic leaf
soflib/fir.pmb
Failed SPB Wrapper generation for soflib/fir with 2 Error(s), 0 Warning(s) and 0 Note(s).
Compilation Failed .
thank you very much

this compilation it's made from cadence spw and it use the sun workshop,so i don't know options of compilation
my os is the SUNOS 5.8
any help will be usefull
thank you

Relocation error sun workshop 6 C++ 5.3

iam using the sun workshop 6 C++ 5.3 compiler on SunOS 5.8. iam building a shared object abc.so
the build is fine but when this "so" is actually used in a process i get the following error:
fatal: relocation error: file abc.so: symbol __1cDstdbG__RTTI__1nDstdIios_baseHfailure__: referenced symbol not found.
i found that this symbol is defined in the libCstd.so which has been linked and its location is in the LD_LIBRARY_PATH.
what could be the problem ? (an "ldd abc.so" does not show libCstd.so nor does it give an error)
regards,
vivek

The combination rwtools7,iostream,Cstd is not valid.
These are the valid combinations:
rwtools7_std,Cstd
rwtools7,iostream
You cannot use rwtools7 and Cstd in the same program.
You need iostream when you use rwtools7.
You can use rwtools7_std and Cstd in the same program.
You cannot use rwtools7_std and iostream in the same program.
You generally cannot use both "classic" iostreams (iostream) and the C++ standard library (Cstd) in the same program, because of conflicts between classic and standard iostreams. If you understand all the issues and are very careful, you can make it work, but we recommend against trying to make it work.
If "ldd abc.so" does not show libCstd.so, it means either libCstd has been statically linked, or no dependency on libCstd occurred in the code.
In my previous message I described what you need to do to get libCstd linked dynamically using C++ 5.3. It should be easy to see whether the symbolic links are present in the compiler installation.
C++ 5.4, 5.5, and 5.6 link libCstd dynamically by default. You don't need to do anything special.

Sun WorkShop 3.0 (C++ 4.2) vs solaris 9

Hi All,
I would like to know whether "Sun Workshop 3.0" (C++ 4.2) compatibility with Solaris 9 or not
I would appriciate if you help me.
thanks
MS

Hi Ragive,
I already I saw the "Product Identification Table".
The table shows C++ 4.2 is compatible upto Solaris 7.
Currently I have Solaris 8 on my system and C++ 4.2 (whorkshop 3.0).
I can able to compile C++ 4.2 code on Solaris 8 even though "Product Identification Table" doesn't show.
We have plan to upgrade Solaris 9 soon.
Since i can able to compile C++ 4.2 code on Solaris 8, I just curious to know whether C++ 4.2 work on solaris 9 ?.
thanks
MSP

Need Sun WorkShop 6 update 2 for Solaris 8

Would it be possible to download an installation package for Sun WorkShop 6 update 2 for Solaris 8?
I have an old development project that I need to resurrect, and it requires this version of the Sun compiler.
Thanks,
-Ken Cooley

Object files and libraries created by WS6u2 can be linked into programs created by later versions of Sun Studio. The default template model changed in Studio 8, so you might need to add -instances=extern to CC command lines. Apart from that possibility, the only other issue I can think of would be invalid code accepted by WS6u2 that SS11 does not accept. I suggest you give Studio 11 a try, unless company policy forbids it.

Compilation error on Solaris 2.6 using SUn Workshop 4.2(Rogue wave STL)

Hello,
I am facing a problem while using Rogue wave STLs on SOlaris 2.6 using Sun WOrkshop pro 4.2
I am using Hash table implementation in the source. It throws the following error:
---->Error: "," expected instead of "const_iterator".
I found it to be problem in a declaration of pair for the class.
Before modification:
typedef pair<mytmp::iterator,int> interator;
Modified to:
typedef mytmp::iterator myitr
typedef pair<myitr,int> interator;
Now the above compilation error seems to be gone. Can anyone please help me in understanding this problem???????????????
Also after compiling few files now i am facing new problem. It throws signal 11 in iterator header file of std STL.
Help m e !!!!!!!!!!
For your reference options of compilation are:
/opt/SUNWspro/bin/CC -c -O -mt -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199506L -D_REENTRANT -D__EXTENSION
S__ -DRWSTD_MULTI_THREAD -D_RWBUILDSHARED -DRWSTD_COMPILE_INSTANTIATE -
DRWSTD_SHARED_BUILD --I/opt/mylib/common/include/Std mydemo.cc

I solved my own problem.
It seems that the C++ XML Parser cannot be used with earlier versions of Oracle. My ORACLE_HOME env variable was pointing to v734. Once I changed that to point to the later version of v816, It was a smooth parse.
null

Earlier versions of Sun Workshop (Forte) C running on Solaris 8

Is it possible to install an earlier version of Sun Workshop C (3.0 or 4.2) on SPARC Solaris 8?
Thanks,
Matt Richmond

These versions of C are not supported on Solaris 8,
versions of 5.0 and higher are supported. You may
get the earlier versions to install, whether they
would work reliabily is entirely another question,
they might, but a bug filed against them on Solaris 8
would not be fixed. The first thing you would hear
is upgrade to WS 5.0 or to FDev 6.

Problems and Workarounds from Sun Workshop[tm] 6 update 2 C++ Compiler Read

Hello out here,
the Sun Workshop[tm] 6 update 2 C++ Compiler Readme says
in Chapter E. Problems and Workarounds
and
Topic 4. Reference From Template to Non-Global File-Scope object is Not Supported:
A program using templates and static objects causes link-time errors of undefined
symbols. The compiler currently does not support reference to non-global file-scope
objects from templates.
So my problem is:
I have static tyname objects in Templates and get that link-time errors of undefined
symbols.
And I do not know how to get rid of that static typename objects.
Is there a Workaround?
Which?
P l e a s e h e l p.
If you need further information, please let me know.
Any help is appreciated.
Thanks in advance.
Yours truly
Karsten J. Martin

Hello,
Thank you for your detailed answer!
Unfortunately there has arosen another problem while
migrating from 4.2 to SunWorkshop[tm] 6 update 2 C++ Compiler.
Here comes the original(4.2) code:
template <class PersistObject>
class DIDDatabaseInterface : public DIDPersistenceInterface<PersistObject>
private:
     DIDTableObject<PersistObject>     m_tableObject;
public:
It does not compile under Version 6.
Now the new version:
template <class PersistObject>
class DIDDatabaseInterface : public DIDPersistenceInterface<PersistObject>
private:
typedef     DIDTableObject<PersistObject> PersistTable;
static typename DIDDatabaseInterface::PersistTable m_tableObject;
public:
That compiles until...
"did_factory.cc", line 73: Information: Instantiating DIDDatabaseInterface<Devx003>::DIDDatabaseInterface(const RWDBConnection&)
"did_persist.cc", line 81: DIDDatabaseInterface<Devx003>::m_tableObject cannot be initialized in a constructor.
Here comes line 81 and surroundings(compiles under 4.2):
template <class PersistObject>
DIDDatabaseInterface<PersistObject>::DIDDatabaseInterface(const RWDBConnection &c)
     :     DIDPersistenceInterface<PersistObject>(),
          m_tableObject(c)
Any idea?
I would be grateful if you could help.
Thank you so much.
Sincerely yours
Karsten J. Martin

Sun WorkShop 6 update 2 problem

I had a licensing problem running my compiler 'cc'. I
installed the licenses.and lmgrd daemon start
successfully
by command:
#/etc/rc2.d/S85lmgrd start
But , when i compile c program display :vendor daemon
is down :
# cc -o hello hello.c
License Error : Licensing product (Sun WorkShop
Compiler C SPARC).
License File: 7588@sun-host
The desired vendor daemon is down
See the system administrator about starting the
server, or make sure the you're referring to the right host (seeLM_LICENSE_FILE).
Feature:workshop.c.sparc
Vendor:Host:sunwlicd : sun-host
FLEXlm error:-97,380. System Error: 146 Connection
refused
cc: acomp failed for hello.c
I check license with command lmstat in
/etc/opt/licenses:
# /etc/opt/licenses/lmstat -a -c licenses_combined
lmstat - Copyright (C) 1989-1999 Globetrotter
Software, Inc.
Flexible License Manager status on Thu 11/4/2004 15:06
License server status: 7588@sun_host
License file(s) on sun_host:
/etc/opt/licenses/licenses_combined:
sun_host: license server UP (MASTER) v7.0
Vendor daemon status (on sun_host):
sunwlicd: The desired vendor daemon is down
(-97,380:146 "Connection refused")
Feature usage info:
Users of workshop.c.sparc: Cannot get users of
workshop.c.sparc: No
such feature
exists (-5,222:146 "Connection refused")
Users of workshop.dbx.sparc: Cannot get users of workshop.dbx.sparc: No
such feature exists (-5,222:146 "Connection refused")
Users of workshop.tools.sparc: Cannot get users of
workshop.tools.sparc: No such feature exists (-5,222:146 "Connection refused")
I try many times ( Load Licenses File & Manually
Licenses Installation ).

First, before start the FLEXLM License Manager, please set
LM_LICENSE_FILE=$LM_LICENSE_FILE:/etc/opt/licenses/licenses_combined
export LM_LICENSE_FILE
then,
# /etc/rc2.d/S85lmgrd start
Second, after you run /etc/rc2.d/S85lmgrd start , make sure license daemon sunwlicd is up and running. You can check out by command
% ps -ef | grep sunw
-Ngoc Nguyen

SUN Workshop 6U2 Debugger Problem

Hi,
I am using SUN Solaris 8 platform for our Application Prog. Development with SUN Forte 6 U2 C Compiler. However after successful build, whenever I am trying to run & debug any of the Application Prog. using SUN Workshop 6U2 dbx tool (using Xterm GUI Env), it is always throwing the following error and getting aborted:
(dbx) debug - 21314 <-- this is one of our application prog PID
There might be too many LWP's in this process.
See `help dbxenv' under mt_scalable.
dbx: Cannot open lwpstatus.
detaching from process 21314
However any of the application prog.s if I run without dbx is running successfully. I also tried to set the dbxenv parameter "mt_scalable" to "on" (which by default is always set to "off") but it didn't work. And I have verified that, all the "lwpstatus" files are there properly in the "/proc/<PID>/lwp/..." path for every process that I tried to debug.
It would be great if anyone can help me out on how to resolve this issue while trying to use Sun dbx 6�.
Thanks.

Hi,
I am using SUN Solaris 8 platform for our Application Prog. Development with SUN Forte 6 U2 C Compiler. However after successful build, whenever I am trying to run & debug any of the Application Prog. using SUN Workshop 6U2 dbx tool (using Xterm GUI Env), it is always throwing the following error and getting aborted:
(dbx) debug - 21314 <-- this is one of our application prog PID
There might be too many LWP's in this process.
See `help dbxenv' under mt_scalable.
dbx: Cannot open lwpstatus.
detaching from process 21314
However any of the application prog.s if I run without dbx is running successfully. I also tried to set the dbxenv parameter "mt_scalable" to "on" (which by default is always set to "off") but it didn't work. And I have verified that, all the "lwpstatus" files are there properly in the "/proc/<PID>/lwp/..." path for every process that I tried to debug.
It would be great if anyone can help me out on how to resolve this issue while trying to use Sun dbx 6�.
Thanks.

Can't debug in Sun Workshop 6.2 anymore

Hi,
Yesterday, we could not longer debug any of our C++ source code in Sun Workshop 6.2 on Solaris 8. We receive the following message when loading a program:
Reading <executable>
There might be too many LWP's in this process.
See `help dbxenv' under mt_scalable.
dbx: Cannot open lwpstatus.
dbx: warning: process initialization failed
This always occurs on:
C++ source
C source
code with 1 LWP
code with >1 LWPs
The same error occurs when we run dbx by itself.
This error is not occuring on Sun Workshop 6.2 on our Solaris 9 development server.
Any help, hints are most appreciated.
Thanks,
Tom

Was the application built on Solaris 8 or Solaris 9? An application built on Solaris 9 will not in general run correctly on Solaris 8.
Solaris 9 uses a different thread library than the default library on Solaris 8. Try re-linking on Solaris 8 (assuming the application was built on Solaris 8) using the optional thread library (which is the only thread library on Solaris 9).
You don`t have to recompile anything. In each link step, add the options
-L/usr/lib/lwp -R/usr/lib/lwp
to the command line (in addition to all existing options).
Finally, WS6.2 is End Of Life, and little support is available for it. Try using Sun Studio 11 instead. You can use the new debugger on old code, and you can switch to the new compilers when convenient. Studio 11 is free, and supports Solaris 8, 9, and 10. (Studio 12 is the current release, but does not support Solaris 8, which is End Of Life.)
http://developers.sun.com/sunstudio

Sun WorkShop 6 update 1 & 2

Greetings All:
Q: Can I build a C/C++ application with update 2 of WorkShop, and expect it to behave normally when executed on a system with update 1 installed?
I have a required for a 3rd party application which only supports 5.3, 5.5, & 5.6 of the compiler.
My system: SunOS jrsun 5.8 Generic_108528-17 sun4u sparc SUNW,Sun-Blade-100
Thanks in advance.
Jeff

Ordinarily, applications build with Sun Workshop (now Sun Studio) do not require that Workshop (Studio) be installed on deployment systems.
If the application requires a shared library from the compiler installation area, you need to supply that library with the application. The file "runtime.libraries" installed in the READMEs directory lists the libraries that you are free to ship along with your product. In that case, you must build the application with a runpath (-R option) that picks up libraries from where you want them installed, instead of from the compiler area.
The libraries that are shipped with a compiler release are intended for use with that compiler release, and not with any other compiler.

Sun WorkShop 6 update 1 C 5.2 2000/09/11 needed.

To get support from the one of our vendors I need Sun WorkShop 6 update 1 C 5.2 2000/09/11 to compile our application. Is ths version still available? Where??
Kind regards,
Markus

Hi
According to
http://developers.sun.com/sunstudio/support/matrix/index.jsp
the last order date for Forte 6u1 was almost 6 years ago.
IMO you'd be better off finding a better vendor that supports a more recent compiler. I presume that you pay this vendor - does it make sense to you to pay them for support for a product that requires a compiler that requires a compiler that is itself no longer supported (unless you're willing to shell out for special bid support)?
Paul

SUN WORKSHOP 5

Similar Messages

Maybe you are looking for