SunWS 4.2 C++ compiler on Solaris 8

Hello,
I have heard that the SunWS 4.2 C++ compiler works on Solaris 8 but is not supported.
Is this accurate? What risks are there using it?
Basically, we are currently using SunWS 4.2 C++ compiler on Solaris 6 and were wondering that if we upgrade to Solaris 8, will this mean the SunWS 4.2 C++ compiler no longer works.
Also, any official documentation stating the above would be appreciated.
Could someone please get back to me soon.
Thanks in advance
Martin

We do not support Workshop 3.0(Compiler version C++ 4.2) on Solaris 8. The risk is: if you run it on Solaris 8 and it works, good; if not, we don't support.
I don't have official documentation at hand. Workshop 3.0 is an EOLed product.
- Rose

Similar Messages

License for cross-compilation for solaris 10 sparc on Linux x86

I'd like to do cross-compilation for solaris 10 sparc on Linux x86 using gcc (for linux). To do that, I have to copy libraries (/lib/64) and includes (/usr/include) from a sparc machine to my linux machine.
The compilation will be run on about (up to) 50 Linux machines (by various developers). We also have 3 solaris-10-SPARC machines.
I wonder if Solaris license allows me to copy the includes and libs to perform compilation elsewhere.
I also checked "OTN License Agreement for Oracle Solaris", but it looks like Oracle allows for installing "the programs" on up to 3 machines, but I need it on 50.
Thanks for any suggestions or redirections to a proper place where I can get an answer.
Marek

When installing Solaris 10 01/06 on a Dell 1850 I receive an error message during the install saying "no disk found". I assume that the drive/controller is not recognized. The Dell 1850 is listed under the HCL for Solaris 10 10/06. I don't believe I can use the Solaris(TM) Device Driver for the LSI MegaRAID Adapter floppy with 1/06. I don�t have any other Solaris boxes up so I can�t build a jump start server. Any suggestions?

Compiling for solaris 9

One of our boxes still runs solaris 2.5.1 but we need to compile some things for a solaris 9 box. Would the binaries compiled on solaris 2.5.1 be compatible for solaris 9?
From what I have gathered searching the web, there are notes that the binaries would be compatible, but there is also a chance it may not. What are the caveates?
Also, we are unable to compile on this solaris 9 box.

They should work.
7/M.

Again - compilation under solaris - help!

Hi all
I'm trying to compile the following test code:
#include <occi.h>
#include <iostream>
using namespace std;
using namespace oracle::occi;
int main(int argc, char ** argv)
Environment *env;
Connection * conn;
try{
env = Environment::createEnvironment();
conn = env->createConnection(user, pass, sid);
env->terminateConnection(conn);
Environment::terminateEnvironment(env);
} catch (SQLException &e) {
cout<<"Exception: %s\n", e.getNLSMessage(env).c_str();
return 0;
My system is Solaris 9 sparc 64-bit
Oracle Database 10.1.0.2
I run this command:
CC -I/u00/oracle/product/10.1.0/db_1/rdbms/public -L/u00/oracle/product/10.1.0/db_1/lib -locci10 test.cpp
and get the famous error
Undefined first referenced
symbol in file
void oracle::occi::Environment::terminateEnvironment(oracle::occi::Environment*) test.o
oracle::occi::Environment*oracle::occi::Environment::createEnvironment(oracle::occi::Environment::Mode,void*,void*(*)(void*,unsigned),void*(*)(void*,void*,unsigned),void(*)(void*,void*)) test.o
oracle::occi::__RTTI__1nGoracleEocciMSQdDLException_ test.o
[Hint: static member oracle::occi::__RTTI__1nGoracleEocciMSQdDLException_ must be defined in the program]
ld: fatal: Symbol referencing errors. No output written to a.out
I've tried to use:
gcc 3.4.2
Sun Forte 6.0
Sun Forte 6.2
Sun Forte 7
Sun Studio 10
all the same
if I set LD_LIBRARY_PATH and try to link with *.so library - it gives me "wrong ELF class: ELFCLASS64"
I've tried to install and use Client 10.2 - no effect
Under Windows it works perfectly.
What should I do to make this thing compile under Solaris?
Message was edited by:
[email protected]
Message was edited by:
[email protected]

If you want your application to be 32 bit
- use Sun Forte 6.2 and link with OCCI library under $ORACLE_HOME/lib32
If you want your application to be 64 bit
- use Sun Forte 8 and link with libraries under $ORACLE_HOME/lib
( You should be passing the 64 bit compile flag "-xarch=v9" )

Assertion problem while using C++ 5.0 compiler on Solaris 2.6

Hi,
we are using C++ compiler 5.0 on sparc solaris 2.6 machine.
when we tried to build the debug version of a particular exe with -g
option , we are getting the following error message
Assertion : ( ../links/dgb_cstabs.cc line 1516)
while compiling a .cc file.
Compiler options we used is
/opt/SUNWspro/bin/CC -c -compat=4 -g -KPIC -w -features=namespace,no%except,bool,mutable -verbose=template -DOS_USE_SHORT_NAMES -DINCLUDEALL +d -DRWSTD_MULTI_THREAD -D_REENTRANT -D_THREAD_SAFE -D_POSIX_C_SOURCE=199506L -DOS_NEW_CHECK -DOS_STL_ASSERT -DOS_NO_WSTRING -DOS_ALTERNATIVE_STL_NAMES -DRWSTD_NO_CONST_INST -DNO_ALLOCATOR_STL -DOS_OMIT_BOOL -DEXE_HANDLING -DNO_CPLM -DALO_ON -DSUBPROC_ON -DCANCEL_ON -D__EXTENSIONS__ -DEXPLICIT_OPERATOR_INVOKE -DSTL_SUPPORT_OPERATOR -DSUNSOLARIS -DWHAT_TIME_DATE="\"Build Date Time Not Set\"" -I/opt/orbplus/include -I/opt/orbplus/include/naming -I/opt/SUNWspro/SC5.0/include/CC4 -I/opt/SUNWspro/SC5.0/include/CC -I/usr/include/reentrant -I../.. -I../../include -I../inc -I. -I/opt/odbc/include -I/oracle/home/oracle/include -I/oracle/home/oracle/rdbms/demo pdl.tab.c -o ../../bin/hpux/obj/pdl.tab.o
without the -g option ,the file compiles successfully.
so please throw some light on this problem and help us to getout of
this problem.
regards
tunga

Assertion problem while using C++ 5.0 compiler on solaris 2.6

Where can I get a C compiler for Solaris 10 (sparc)?

Where can I get a C compiler for Solaris 10 (sparc)?

Have you tried gcc ?Ok. What kind of GCC compiler for Solaris 10( sparc) can you suggest me?
The gcc-3.3.2 was compiled on Solaris 9, but i am using it on Solaris 10, that is why(it is my assumption) i have some problems with compilation library files( for example, sys/kstat.h)

Sparc C/C++ compiler for Solaris 7 ?

A legacy programming project is making me dust-off my SPARCstation 20. I believe it has either Solaris 2.6 or Solaris 7 loaded. Although I should upgrade to the latest Solaris, I'm hoping to avoid that nightmare, since this project is a one-off. The old SUNWspro C/C++ compiler on this SS20 was an add-on purchase item back then, and now the debugger (dbxtool) is not working correctly.
Here is my silly question: Does the Sun Studio C compiler support Solaris 2.6 or Solaris 7 ?
Thanks.

My dbxtool is from many moons ago, just after Sun unbundled the standard C compiler from Solaris, and made it a product you had to buy separately. So my C/C++ compiler on Solaris 2.6 is a product known as "SPARCworks 3.0". In SPARCworks they had renamed the traditional dbxtool binary to "debugger". I remember the last time I used this system (at least 8 years ago) the debugger was working, but now when I run it, it stops with the error:
Debugger: internal error (11).
Abort.
I'm not working remotely, I'm on the console.
I think it will be easiest now to just get a Sunblade/Sparc and load Solaris 10/SunStudio 12.
There is more to this story for those who are old enough (like me) to remember Disco. I also have an old SPARCstation 2 (3/60) with SunOS 4.1.3 still running. It was used for supporting the ancient SunOS version of our CADDS 4X viewing software. I got it running yesterday, and updated the C source files for the project. Got it to compile without errors, but the regular "dbxtool" that came with OpenWindows fails to load my code. I should be able to do: "dbxtool dvcadds &" and that will load the project, but it just sits there (I'm on the console). I know that used to work. I can still use plain "dbx" on both systems, but that is too painful.
On the old SunOS system, if I just run "dbxtool", it appears, and I can "run dvcadds", but it doesn't recognize the fact that I have compiled all .o files with cc-g, and won't load source files to step through.
So I'm still looking at getting a Sunblade with Solaris 10/SunStudio 12...

Using 4.2 compiler with solaris 8?

Does anyone know if it is possible to get/use the 4.2 compiler with Solaris 2.8? If not, have people found that compat=4 was an adequate workaround? Thanks, John Ranta
Feel free to copy reply to my email
[email protected]

i don't know if it is possible to use the 4.2 compiler with solaris 8.
however we have used the compat=4 option for some ported code that
did not compile under the Forte 6 compiler without compat. we
have not seen a problem using compat=4 as a workaround.

Openldap client compile in Solaris 8/9

Did anyone compile openldap client with ssl/TLS in solaris 8/9 platform and authenticate against SUN one iplanet directory server 5.1 sp2 successfully?
I cannot get the openldap client talk to the IDS ?
Thanks
DMA

Lars,
Use ldmp2v to convert existing physical server to VM and
Convert Solaris 8 and 9 physical servers to container in Solaris 10 VM?
Is that what you are saying?
Major constraint I have is, applications running in the current physical servers have no vendor support, vendor doesn't exist any more. Application has been locked to run only on the same OS version. What I am worried is, while running ldmp2v should not prevent the application coming up in the new virtualized environment. Keeping that in mind, I gave a thought like
1. Install and configure the CDOM (control domain)
2. configure and Install LDOMs with Solaris 10 OS
3. Run flar on the existing Solaris 10 physical server
4. Transfer the flar created to Solaris 10 LDOM and configure it as a zone
5. For Solaris 8 and 9, create LDOMs with Solaris 10 OS
6. Install additional patches and packages needed for supporting Solaris 8 and 9 zones
6. create flar images on the existing Solaris 8 and 9 physical servers
7. transfer the images to newly created LDOM and configure the zone.
8. Current servers sun4u which has to be converted to sun4v.

Compiling for solaris 9 on solaris 8 machine

Hi, is it possible to use a solaris 8 machine with workshop, to compile binary for solaris 9.
I need to compile user-mode app as well as kernel modules both for 64/32 bit environments.
The modules are all dynamically linked.
If this is possible, what is the proper procedure??
ERAN.

For user space apps, if you are sticking to the published interfaces (ie: not using any private, non-public symbols you might have dug up in our libraries) then compiling and linking on Solaris 8 and running on Solaris 9 is not a problem, at least for user space. Run appcert on your application if you want to ensure you aren't using anything private. We are forward-compatible in this sense.
As for kernel modules, I don't know enough to comment.

Problem with software compilation with Solaris 10 x86

Hi!
I installed Solaris 10 (entire distribution) and realized that my gcc compiler can't compile even a very simple application.
#include<stdio.h>
int main()
printf("abc");
return 0;
}This is output from terminal screen:
# gcc test.cpp
Undefined first referenced
symbol in file
__gxx_personality_v0 /var/tmp//ccYJ4DSu.o
ld: fatal: Symbol referencing errors. No output written to a.out
collect2: ld returned 1 exit status
Please help!
Thank you.

GCC does different things depending on how the file is named. cpp should refer to a file that needs to go through the c preprocessor, not C code.
Try renaming test.cpp to test.c.
bash-3.00# gcc foo.cpp
Undefined first referenced
symbol in file
__gxx_personality_v0 /var/tmp//ccvnZHGr.o
ld: fatal: Symbol referencing errors. No output written to a.out
collect2: ld returned 1 exit status
bash-3.00# mv foo.cpp foo.c
bash-3.00# gcc foo.c
bash-3.00# ./a.out
abcbash-3.00#
Darren

Strange errors on compiling in solaris 10

I was trying to compile my application on solaris 10 and i got these strange long list of errors. i tried to verify the same by just trying to compile the hello world program and got the same error messages. i am using solaris 10 machine with gcc 3.4.2.
Also kindly note that its a 64 bit machine....
i am getting the following error messages:
# bash-3.00$ gcc hello.c -o hello
In file included from hello.c:1:
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:36:27: iso/stdio_i
so.h: No such file or directory
In file included from hello.c:1:
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:194: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:229: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:230: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:236: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:244: error: parse
error before "size_t"
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:249: error: parse
error before "size_t"
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:258: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:260: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:284: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:293: error: parse
error before '*' token
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:294: error: parse
error before "FILE"
/usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdio.h:295: error: parse
error before '*' token
Is it becoz of the gcc or something. Please help, as it is very important for me to solve this issue early or else i am dead meat.
Thanks in advance
-Sjain

Thanx Again Robert. But i have been able to resolve the issue. Dont ask me how coz even i dont know. I just installed the gcc 3.3.2 from sunfreeware compatible for solaris 10. yes, the mkheaders command did help me a great extent as simply installing the gcc from sunfreeware site didnt help, i had to explicitly do mkheaders to be able to use the gcc. but at the end of it, i am now running gcc... thankx for ur valuable help and that too a repeated one :-) am a happy man now!!!
-Sjain

Error on compiling in Solaris 10

I was trying to compile my application on solaris 10 and i got these strange long list of errors. i tried to verify the same by just trying to compile the hello world program and got the same error messages. i am using solaris 10 machine with gcc 3.4.2.
Also kindly note that its a 64 bit machine....
i am getting the following error messages:
In file included from /usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdi
o.h:36,
from hello.c:1:
/usr/include/iso/stdio_iso.h:51:31: sys/feature_tests.h: No such file or directo
ry
/usr/include/iso/stdio_iso.h:52:25: sys/va_list.h: No such file or directory
/usr/include/iso/stdio_iso.h:54:24: stdio_impl.h: No such file or directory
In file included from /usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/include/stdi
o.h:36,
from hello.c:1:
/usr/include/iso/stdio_iso.h:106: error: parse error before "fpos_t"
/usr/include/iso/stdio_iso.h:211: error: redefinition of parameter '_RESTRICT_KY
WD'
/usr/include/iso/stdio_iso.h:211: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:213: error: redefinition of parameter '_RESTRICT_KY
WD'
/usr/include/iso/stdio_iso.h:212: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:213: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:213: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:214: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:214: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:215: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:215: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:218: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:218: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:220: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:220: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:226: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:226: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:229: error: redefinition of parameter '_RESTRICT_KY
WD'
/usr/include/iso/stdio_iso.h:228: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:230: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:230: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:231: error: parse error before "__va_list"
/usr/include/iso/stdio_iso.h:232: error: parse error before "__va_list"
/usr/include/iso/stdio_iso.h:233: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:233: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:234: error: parse error before "__va_list"
/usr/include/iso/stdio_iso.h:236: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:236: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:238: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:238: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:253: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:252: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:255: error: conflicting types for '_RESTRICT_KYWD'
/usr/include/iso/stdio_iso.h:254: error: previous definition of '_RESTRICT_KYWD'
was here
/usr/include/iso/stdio_iso.h:257: error: parse error before "fpos_t"
/usr/include/iso/stdio_iso.h:258: error: parse error before '*' token
is it becoz of the gcc i am using, do i need to use some other gcc???
Please help. it is very important that i fix this issue early or else i am dead meat!!!
Thanx in advance
-Sjain

Sorry i have put up the wrong error messages. Please check the other post i have made for the same with the correct error messages. Sorry !!!
-Sjain

How to get the sparc c compiler in solaris 9.

How to get the sparc c compiler in solaris9 is the licence one?. If it is license what was the procedure to get the software.

The gcc compiler is available on the "extra" disk in Solaris 9, but we don't recommend using gcc for Solaris development. (You can if you want to, but you will get better performance using the Studio C compiler.
For Solaris 9, which is now obsolete, the most recent version of Studio that supports it is Sun Studio 12 (released in 2007). You can download it here:
http://www.oracle.com/technetwork/server-storage/solarisstudio/downloads/ss12-136026.html
Patches for Studio 12 are available to fix known bugs, but you need a service contract with Oracle to get them. Click on the "Support" tab for details.

Is it possible to use CC 5.7 to compile for Solaris 6/7 platforms?

Hello,
we are currently upgrading to the new CC 5.7 from CC5.2 (Forte Update 1). One advantage we notice is the new, simplified licensing scheme, and hence the possibility to get rid of the license server installations. However, we still have to support our product on Solaris 7 (and possibly, though unlikely, Solaris 6).
Because CC 5.7 only installs on Solaris 8, the question is whether it would be possible to cross-compile for those older platforms (e.g. via -xarch). (And use our Solaris 7 installations only for testing, not compile-purposes anymore.)
Your help is greatly appreciated!
Many thanks,
Andreas

Programs built on Solaris 8 usually will not run on Solaris 2.6 or 7, no matter what compiler you use. Sun Studio 9 (C++ 5.7) supports only Solaris 8, 9, and 10.
You need to build your applications on the lowest version of Solaris that they are intended to be run on. Maybe you could build on Solaris 7 using FD6u1, and again on Solaris 8 using Studio 10 for customers using Solaris 8 and later.

SunWS 4.2 C++ compiler on Solaris 8

Similar Messages

Maybe you are looking for