Compiling C++ application for Solaris 5.8

Hi,
How can we build/compile C++ application to be deployed on Solaris 5.8 OS? Which compiler should be used for the same?
We are exploring how this can be done. Request your help to identify the mechanism in which we can achieve this.
We explored following but it didnt worked -
- Using Studio 12 we build application on Solaris 10 but it is giving error at execution time
ld.so.1: ./distmgr: fatal: libCrun.so.1: version `SUNW_1.5' not found (required by file ./distmgr)
Questions -
- Is Studio 12 supported on Solaris 5.8?
- If ready made binaries are not available of Studio 12 then can be build this for 5.8? IS the source code of Studio 12 available?
- Can Studio 12 on Solaris 10 cross complie for OS Solaris 5.8
Thanks and Regards,
vinit.

I strongly advise against using WS62. Studio 11 is superior to WS6u2 by any reasonable measure. Valid source code that compiled with older compilers should continue to work correctly with later compilers. Any problems are usually due to invalid code that was incorrectly accepted by the earlier compiler. In some cases we provide compiler options to reproduce the old compiler behavior, but it is better to fix the code so that it is valid and has well-defined semantics.
Consider also whether you would wind up mixing binaries built by WS6u2 with binaries built by a later compiler. If so, you must use the later (or latest) compiler involved to perform any link steps. That is, steps that create shared libraries or executable programs.
We strive to maintain forward binary compatibility, meaning old binaries can be linked into new programs, but there are some issues with C++ compilers older than Studio 7 that can cause compatibility problems when the code is mixed with C++ code from newer compilers. In the worst case, a multi-threaded program can compile and link, but fail at run time, depending on compilation options used with WS6u2. It is safer to rebuild such old binaries using the newer compiler. Binaries created by Studio 7 or later compilers should not have that problem.
I'm sorry to have to list so many caveats, but continuing to use obsolete software creates its own problems. We bring out new versions and retire old software for good reasons.

Similar Messages

Compiling an application for Solaris 9 on a Solaris 10 system

Hi,
I was wondering if it's possible to compile an application Solaris 10 in such a way that it will run on Solaris 9.
I'm building a set of library tools and they need to run on Solaris 9 and 10, but it'd be nice if I could build this on a Solaris 10 box.
Is this possible, and if so, how do you do it?
thanks,
Trevor

I'm working on this same issue. Unfortunetly, it appears that my only option is to compile on a Solaris 10 box for running on a Solaris 8 box. Thankfully this doesn't look too bad because after doing a 'ldd', I get that the only file I'm missing is the libm.so.2. If I can specify in the makefile to use libm.so.1 only, then all should be ok.
So I guess my question would be: What exactly do I need to do in my makefile to explicitly link to libm.so.1? I've tried the following with no luck.
/opt/SUNWspro/bin/cc -xCC -Bdynamic -g \
/usr/lib/libm.so.1 \
/opt/mylibs/my_compiled_lib.lib \
first_obj.o \
second_obj.o \
-o my_program
The above returns:
ld: fatal: file /usr/lib/libm.so.1: open failed: No such file or directory
ld: fatal: File processing errors. No output written to macsruntime
However, if I change my link to /usr/lib/libm.so everything works but it is linked with the /usr/lib.libm.so.2. Any help would be appreciated.

Linking applications for Solaris 2.5.1 using Forte C 6

Hello,
We still need to provide applications that have to run on 2.5.1. Is there a way to compile C code using Forte C 6 on Solaris 7, and deliver executables that successfully run on 2.5.1 ?
Any help would be appreciated.
Thanks.
Yves.

Ordinarily, the same source files and makefiles that work with C++ 5.0 on Solaris 2.6 should work with C++ 5.3 on Solaris 8.
You didn't say what you did to "adapt the makefile" when changing compilers and OS versions. If the compiler was installed in the default /opt location on each system, we don't think any makefile change would be required. (You might want to make changes for performance or program organization reasons, but we don't think any changes are required just to repeat a working program build.)
What happens if you use the original files that worked with C++ 5.0 on Solaris 2.6?
Are C++ 5.0 and C++ 5.3 are both installed in the same /opt directory? That isn't allowed, and will lead to strange behavior.
Are you continuing a build using the new compiler and OS in a directory containing old binary files or template cache? When changing OS and compilers, it is safest, but not strictly necessary, to rebuild all your binary files. At a minimum, you must delete the old template cache.
Are you still using C++ 5.0 in the build process? If so, you must isolate the use of C++ 5.0 and 5.3. The compilers cannot share a template cache, so you must run compiles in different locations.
Anything beyond these hints will require more support and analysis than we could provide in the Forum. You will probably need to generate a .i file from the compilation and have a support engineer look at it. If you have contract with Sun, please follow the service channel.
- Rose

Delivering applications for Solaris 2.5.1 using Forte C 6

Is it possible, using Forte C 6 as the development environment, on Solaris 7, to produce applications that will successfully run on Solaris 2.5.1 ?
Any help will be appreciated.
Thanks.
Yves.

Ordinarily, the same source files and makefiles that work with C++ 5.0 on Solaris 2.6 should work with C++ 5.3 on Solaris 8.
You didn't say what you did to "adapt the makefile" when changing compilers and OS versions. If the compiler was installed in the default /opt location on each system, we don't think any makefile change would be required. (You might want to make changes for performance or program organization reasons, but we don't think any changes are required just to repeat a working program build.)
What happens if you use the original files that worked with C++ 5.0 on Solaris 2.6?
Are C++ 5.0 and C++ 5.3 are both installed in the same /opt directory? That isn't allowed, and will lead to strange behavior.
Are you continuing a build using the new compiler and OS in a directory containing old binary files or template cache? When changing OS and compilers, it is safest, but not strictly necessary, to rebuild all your binary files. At a minimum, you must delete the old template cache.
Are you still using C++ 5.0 in the build process? If so, you must isolate the use of C++ 5.0 and 5.3. The compilers cannot share a template cache, so you must run compiles in different locations.
Anything beyond these hints will require more support and analysis than we could provide in the Forum. You will probably need to generate a .i file from the compilation and have a support engineer look at it. If you have contract with Sun, please follow the service channel.
- Rose

Need to compile C code for Solaris 5.4 target

Hi,
I'm current on a project where the target platform is Solaris 5.4. I believe the SunOS version is 2.4. Unfortunately, there is no way I can get the customer to upgrade their server or OS.
In my search so far I've been unsuccessful in finding a compiler for that platform. The oldest gcc I can find is for SunOS 2.5.
What other options do I have?
Will code compiled with the C compiler in the Sun Studio 12 be able to run on SunOS 2.4? If so, is there a command line option I need to set while compiling the code?

No available Sun compiler can be used on, or to generate code for, SunOS 5.4 (Solaris 2.4). Even Sun Workshop 5.0, released in 1998, did not support Solaris 2.4.
If you develop code to be run on Solaris 2.4, you need to compile on Solaris 2.4 (or earlier). Binaries created on a later version of Solaris will not in general run on an earlier version of Solaris. I think that Sun WorkShop 3.0 was the last version that supported Solaris 2.4, but it might have been WorkShop 2.0. Those antiques are not available from Sun.
If I were in this situation, I would tell the customer that the OS and all support software are many years past End Of Service Life. No support is available, the software is no longer available, and I can't help them unless they are willing to upgrade to supported software. (I might also ask the customer if they still use Windows 3.1 on their PCs. The situation is comparable.)
If you don't have that option, your next best hope is that the customer has a C compiler on their system. If so, find a way to use it. If it's a Sun compiler, you will have a problem acquiring a license to run it. You will probably have to run it on their system.
If the customer doesn't have a compiler, I guess you have to keep trolling in newsgroups and forums, looking for a compiler that supports Solaris 2.4. Good luck.

Build for solaris 8 on solaris 10 - possible?

I want to build/compile an application for solaris 8, but I only have access to a machine running solaris 10. Can I compile for solaris 8 on a solaris 10 machine, and if so, what do I have to do to make it work?

The short answer is generally no.
The long answer is that it can be done but you will need to make sure that on the Solaris 10 machine you only use functions/headers/libraries that are available on Solaris 8 otherwise they will not be found and the software won't work.
alan

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.

Cross compiling apps on solaris 8 for solaris 10 x86 and x64

Hi All,
We have a few applications built on Solaris 8. and we want to build the same apps on Solaris 10 x86 and x64 but the problem is clearcase does not support Solaris 10 yet.
Can we cross compile the apps on Solaris 8 for Solaris 10 x86 and x64 ? and how ?
waiting for any info on this.
TIA,
warm regards,
Girish

FYI, I noticed the reply on Sun Studio General Forum:
If you build an app on one version of Solaris, the app will run on later Solaris versions. So in particular, you can build an x86 application on Solaris 8 and run it on Solaris 9 and 10.
Unfortunately, an x64 application must be built on a Solaris x64 system, which first became available with Solaris 10.

Any alternatives for compiling of applications / libraries using C++11 Standard Headers not supported in Studio 12.4?

Hi,
As mentioned in Compiler Issues - Oracle® Solaris Studio 12.4: Release Notes, the following statement below has listed 4 headers which are unsupported in C++11 Mode (-std=c++11):
C++11 Standard Headers
The following headers are for concurrency features and are not supported in the Oracle Solaris Studio 12.4 release:
<atomic>
<future>
<thread>
<mutex>
However, some applications / libraries (e.g. Mozilla Firefox) may require the use of unsupported C++11 Standard Headers, so what options do I have if I need to compile these applications / libraries using Studio 12.4 (I can use g++ compiler, but there are more errors during compilation using g++ as compared to CC, which is difficult to fix)? Plus, there are some performance issues (e.g. run-time) that I may take into consideration when compiling, which I may use CC for compilation as compared to g++.
Regards,
Brian

If those headers are included, you get an error message saying they are not supported. (We intend to support them in a future release.) If the headers are included because features from the headers are needed by the program, you are out of luck. Otherwise, I suggest you modify the source code so that unsupported headers are not included. (Why include a header that you don't need?)
We considered supplying stubs for the unsupported headers that would contain no declarations. That approach seemed like it would just lead to more questions and complaints. The header would appear to compile, but code using the header features would not.

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?

Error in compiling Flex application (1). Consult log file for details.

Dear All,
when i deploy the application from VC i am facing the below issue.
Error in compiling Flex application (1). Consult log file for details.
Please help us.
Regards,
Suman

Hi Juan,
Please look into the below issue.
Error in compiling Flex application: java.lang.InternalError: Can't connect to X11 window server using '172.16.12.41:0.0' as the value of the DISPLAY variable.
   at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
   at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:175)
   at java.lang.J9VMInternals.initializeImpl(Native Method)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:192)
   at java.lang.Class.forNameImpl(Native Method)
   at java.lang.Class.forName(Class.java:119)
   at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:91)
   at macromedia.fonts.JREFontManager.initializeSystemFonts(JREFontManager.java:242)
   at macromedia.fonts.JREFontManager.createSetForSystemFont(JREFontManager.java:58)
   at macromedia.fonts.CachedFontManager$FontCache.fetch(CachedFontManager.java:109)
   at macromedia.util.LRUCache.get(LRUCache.java:114)
   at macromedia.fonts.JREFontManager.getEntryFromSystem(JREFontManager.java:186)
   at macromedia.swf.builder.tags.FontBuilder.<init>(FontBuilder.java:52)
   at macromedia.css.FontFaceRule.initialize(FontFaceRule.java:82)
   at macromedia.css.StyleDocumentHandler.endFontFace(StyleDocumentHandler.java:36)
   at org.apache.batik.css.parser.Parser.parseFontFaceRule(Unknown Source)
   at org.apache.batik.css.parser.Parser.parseStyleSheet(Unknown Source)
   at macromedia.css.StyleParser.init(StyleParser.java:165)
   at macromedia.css.StyleParser.<init>(StyleParser.java:89)
   at macromedia.css.StyleSheet.parse(StyleSheet.java:71)
   at flex.compiler.parser.MxmlParser$4.end(MxmlParser.java:1123)
   at flex.compiler.parser.MxmlParser.endElement(MxmlParser.java:402)
   at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
   at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
   at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
   at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
   at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
   at javax.xml.parsers.SAXParser.parse(Unknown Source)
   at javax.xml.parsers.SAXParser.parse(Unknown Source)
   at flex.compiler.parser.MxmlParser.parseDocument(MxmlParser.java:4363)
   at flex.compiler.MxmlLoader.parse(MxmlLoader.java:277)
   at flex.compiler.MxmlLoader.loadComponentType(MxmlLoader.java:178)
   at flex.compiler.MxmlLoader.loadComponent(MxmlLoader.java:204)
   at flex.compiler.CachedComponentLoader.getComponent(CachedComponentLoader.java:197)
   at flex.compiler.CachedComponentLoader.loadDefinition(CachedComponentLoader.java:101)
   at flex.compiler.CachedComponentLoader.getDefinition(CachedComponentLoader.java:263)
   at flex.compiler.CompositeLoader.getDefinition(CompositeLoader.java:54)
   at flex.compiler.linker.Loader.getType(Loader.java:266)
   at flex.compiler.linker.Loader.findType(Loader.java:248)
   at flex.compiler.CompilerPackageManager.loadType(CompilerPackageManager.java:629)
   at flex.compiler.MxmlCompiler.openDocument(MxmlCompiler.java:61)
   at flex.compiler.MxmlCompiler.compile(MxmlCompiler.java:234)
   at flex.tools.Mxmlc.main(Mxmlc.java:166)
Regards,
Suman

How to compile your flex application for Iphone Using Adobe Flash CS5?

How to compile your flex application for Iphone Using Adobe Flash CS5?

I'm so sorry, I'm not really familiar with the codes.

OWB Real Application Cluster R2 for solaris

Hi all,
Can u give me the link from where i can download the software for OWB Real Appication Cluster for 10g R2 for solaris.
Regards,
Ram

If you are going to use windows. I recommend you to use Oracle9i Rel.2 and use OCFS instead of Raw devices.
Real Application Clusters Administration Contents / Search / Index / PDF
Real Application Clusters Concepts Contents / Search / Index / PDF
Real Application Clusters Deployment and Performance Contents / Search / Index / PDF
Real Application Clusters Documentation Online Roadmap Contents / Search / /
Real Application Clusters Real Application Clusters Guard I - Concepts and Administration Contents / Search / Index / PDF
Real Application Clusters Real Applications Clusters Guard I Configuration Guide Release 2 (9.2.0.1.0) for UNIX Systems: AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, and Sun Solaris Contents / Search / Index / PDF
Real Application Clusters Setup and Configuration Contents / Search / Index / PDF
http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
Joel Pérez
http://otn.oracle.com/experts

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.

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)

Compiling C++ application for Solaris 5.8

Similar Messages

Maybe you are looking for