Sun Studio 11 CC's Bug? Compared with Forte

class proc_pdu_cursor
friend proc_pdu;
private:
bool set;
prp_cursor cursor;
operator prp_cursor*() const;
public:
proc_pdu_cursor();
proc_pdu_cursor(const proc_pdu_cursor &);
proc_pdu_cursor(const prp_cursor c);
proc_pdu_cursor& operator=(const prp_cursor c);
proc_pdu_cursor& operator=(const proc_pdu_cursor&);
friend bool operator==(const proc_pdu_cursor& lhs,
const proc_pdu_cursor& rhs);
friend bool operator!=(const proc_pdu_cursor& lhs,
const proc_pdu_cursor& rhs);
bool is_set() const;
bool is_null() const;
void dump() const;
proc_pdu_cursor& reset();
prp_cursor cont() const { return cursor; }
class proc_cursor {
     private:
          static void * dup_f(void*);
          static void clear_f(void*);
     //protected:
          void * (*dup)(void *);
          void (*clear)(void *);
          void * curs;
     public:
          proc_cursor(void);
          proc_cursor(const proc_cursor&);
          proc_cursor(void *, void*(*)(void*), void(*)(void*));
          void * get(void) const {return curs;}
          proc_cursor& operator=(const proc_cursor&);
          virtual ~proc_cursor(void);
class PDUCUR: public proc_cursor
private:
static void * dup_f(void* dat) { return dat; }
static void clear_f(void*) { }
public:
PDUCUR();
PDUCUR(const PDUCUR &);
PDUCUR(const prp_cursor);
PDUCUR(const proc_pdu_cursor &);
~PDUCUR() { }
where process invokes:
int MCB::dispatch_link_pdu(proc_pdu& lpdu)
PDUCUR cursor(proc_pdu_cursor());
int req = lpdu.get_command();
proc_pdu_cursor c1;
if (lpdu.next_peer(c1))
if (lpdu.get_ref_qual(c1).category() == "SD_PREFIX") mPrefixCur = c1;
cursor = mPrefixCur;
mPrefixCus is member varialbe of class proc_pdu_cursor to MCB.
While Forte6.1 passed this file's compilation.
but Studio11 Failed and offered an error:Error: The operand "*cursor" cannot be assigned to.
Even I updated the member function of PDUCUR& operator =(const proc_pdu_cursor&), it still encounter such a problem. Who can help me, thanks.

You don't show enough of the code to determine what is wrong. The code example uses types proc_pdu and proc_pdu_cursor, which are not defined. The function at the end where you have the problem is a member of class MCB, which is not defined.
Try reducing the test case to remove references to types that don't matter, and provide stub definitions of classes that do matter. (By "stub", I mean just enough declarations in the classes to let the code compile and still show your problem.)
Verify that you can compile the code wtih FD6u1 but get the error wtth Studio 11.
The Forum posting sofware tends to mangle code examples, so enclose the code in "code" brackets.

Similar Messages

  • Sun Studio Compilers for Linux: Problems with undefined variables using CC

    I am experiencing the following errors below while trying to compile C++ programs using Sun C++ from the latest release of Sun Studio Compilers for Linux Alpha, on Red Hat Enterprise Linux 4 with kernel 2.6.9-34.EL and Ubuntu Breezy Badger 5.10 with kernel 2.6.12-10-686. I get the same exact errors on both OS's and on two different machines.
    root@ubuntu:/home/jc/cs225/Machine Problems/cs225/mp1/cs225_mp1# make
    CC -c -g string.cpp
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 74: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 75: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 191: Error: "," expected instead of "state_type".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 194: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 261: Error: "," expected instead of "get_state".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 265: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 299: Error: "," expected instead of "state_type".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 302: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 410: Error: "," expected instead of "get_state".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 414: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 506: Error: The function "strstr" must have a prototype.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 523: Error: The function "strcspn" must have a prototype.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 529: Error: The function "strspn" must have a prototype.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: Template parameter std::stateT requires a type argument.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: Template parameter std::stateT requires a type argument.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 214: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 221: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 277: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 335: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 392: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 443: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 504: Error: Template declarations cannot have extern "C" linkage.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 558: Error: Template declarations cannot have extern "C" linkage.
    Compilation aborted, too many Error messages.
    make: *** [string.o] Error 1
    Except on ubuntu, it has one more error
    "/usr/include/wctype.h", line 47: Error: A declaration was expected instead of "}".
    and what is on line 47 is below
    __END_NAMESPACE_C99
    When I comment this line out, that particular error does not show up but still the other errors above still show up.
    From the testing I did, it appears to have these problems for most of the C++ programs I have written, especially the ones that involve object oriented programming. All programs that I wrote do not have these problems with g++ or Sun CC for Solaris. It does however work fine only for small fraction of the programs I have written. I dont quite understand why it works in some cases and others it doesnt, but I know for sure, that it should be working for all cases when Sun CC from Sun Studio 10 on Solaris 10 for X86 has no problems compiling the same programs.

    I tried workaround number 2 from the 3 choices that were listed by horsh. That fixes the mathcalls.h problem but still I have the following errors.
    jcurran2@ubuntu:~/cs225/Machine Problems/cs225/mp1/cs225_mp1$ make
    CC -c -g string.cpp
    "/usr/include/wctype.h", line 47: Error: A declaration was expected instead of "}".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 74: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 75: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 191: Error: "," expected instead of "state_type".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 194: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 261: Error: "," expected instead of "get_state".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 265: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 299: Error: "," expected instead of "state_type".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 302: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 410: Error: "," expected instead of "get_state".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 414: Error: Use ";" to terminate declarations.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 506: Error: The function "strstr" must have a prototype.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 523: Error: The function "strcspn" must have a prototype.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 529: Error: The function "strspn" must have a prototype.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: Template parameter std::stateT requires a type argument.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: Template parameter std::stateT requires a type argument.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 55: Error: mbstate_t is not defined.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 55: Error: Template parameter std::stateT requires a type argument.
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 61: Error: "," expected instead of "state_type".
    "/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 63: Error: Use ";" to terminate declarations.
    Error: Cannot continue processing because of prior errors.
    Compilation aborted.
    make: *** [string.o] Error 1
    jcurran2@ubuntu:~/cs225/Machine Problems/cs225/mp1/cs225_mp1$
    Can someone please respond? There is more to the problem. Perhaps
    there are more glibc headers that have problems. In addition, if Sun wants to port the Sun Studio Compilers for linux to be stable on all linux distributions I suggest using VM ware and installing several linux distrobutions as virtual machines and testing this software on each virtual machine to see the problems that occur on each distribution. That way you might be able to uncover more problems to find a solution that will work best for portability on all linux distributions.

  • Installing  cooltools when Sun studio is installed in a non default dir

    Hello all,
    I have installed sun studio 12 on one node of a SPARC cluster. When installing, I did not use the default directory (/opt/SUNWspro), but I used a different one as this installation is for trial purposes only.
    Now, I want to install discover, ats and all other tools that are included in the tar file. I followed the instruction on suns web page : http://cooltools.sunsource.net/cmtdt/install.html, but all the information there is based on the fact that sun studio is installed in the default directory.
    Does anyone know, what should I do in order to install the tools in the proper directory? Should I specify a path in the "pkgadd" command? Please help as I am stuck at the moment.
    Thanks a lot.
    Yiannis

    I think I found the answer myself. It is written in sun's web page:
    If the Sun Studio 12 tools are installed with a different base directory, say /opt/Studio12/SUNWspro/bin, then use the option -a none in the pkgadd command. When you are prompted for the <base_dir>, enter /opt/Studio12. The tools in the SPROprfns and SPROcool packages will be installed in /opt/Studio12/SUNWspro/extra/bin.
    I think this solves the problem, but in any case, please feel free to comment on this one.

  • -nodisplay bug with Sun Studio 10 for Linux installer

    I'm currently trying to install a trial Sun Studio 10 for Linux on a Fedora Core 3 box. I want the installer to run via the command line, so I use "./installer -nodisplay", but I get the following error message:
    java.lang.UnsatisfiedLinkError: /home/pacey/SS10/.install/jvm_1.4.2/j2re1.4.2_06/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
    libXp is part of the X window system, but I've specified -nodisplay. A non-graphics option shouldn't be trying to load graphics libraries - looks like a bug. Anyway, as I don't have version 6 of that lib on my system, I'm stalled on this. Any suggestions?

    I'm currently trying to install a trial Sun Studio 10 for Linux on a Fedora Core 3 box. I want the installer to run via the command line, so I use "./installer -nodisplay", but I get the following error message:
    java.lang.UnsatisfiedLinkError: /home/pacey/SS10/.install/jvm_1.4.2/j2re1.4.2_06/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
    libXp is part of the X window system, but I've specified -nodisplay. A non-graphics option shouldn't be trying to load graphics libraries - looks like a bug. Anyway, as I don't have version 6 of that lib on my system, I'm stalled on this. Any suggestions?

  • Poor performance of string::append on Solaris 10 with Sun Studio 10

    I found string::append(size_type num, char ch) of libCstd consumes too much cpu time comparing with stlport. Anybody knows if this is a known issue on Solaris 10 and Sun Studio 10? Or if I need to use special build options to build with libCstd?
    For example: a.c
    #include <iostream>
    #include <time.h>
    using namespace std;
    int main()
      string ss;
      for ( i=0; i<60000; i++)
        ss.append(1, 'A');
      cout << clock();
      cout << endl;
      return 0;
    }Build with libCstd:
    CC a.c -o a1
    Build with stlport:
    CC -library=%none -library=stlport4 a.c -o a2
    a1 outputs: 10000
    a2 outputs: 1900000
    You can see how big different they have. I am sure their running environment is same.

    I suspect this is due to a bug in libCstd that manifests itself by reallocating the string for each append. Compile and run the program below:
    #include <string>
    #include <new>
    #include <stdlib.h>
    int in_main;
    void* operator new (size_t nbytes) throw (std::bad_alloc) {
    if (in_main) printf ("operator new (%zu)\n", nbytes);
    return malloc (nbytes);
    void operator delete (void *p) throw () {
    if (in_main) printf ("operator delete (%p)\n", p);
    free (p);
    int main () {
    in_main = 1;
    std::string ss;
    for (int i = 0; i < 256; i++) {
    printf ("append(1, 'A')\n");
    ss.append (1, 'A');
    in_main = 0;
    }

  • Solaris 10 vs sun studio 7 forte

    How better is solaris 10 tools compared to sun studio 7 forte tool ... is the compiler of better performance?

    Are you asking about specific tools included with Solaris 10
    or Sun Studio 10 ? If the latter, the newer version has considerable
    performance improvements over the older one. If you're referring
    to the gcc that's included on an extras/bonus CD, that's a more
    difficult question to answer since there are quite a few factors
    involved. I believe there are documents online with some
    comparisons.
    In any case, the latest version of our compilers is Studio 11 and
    it's available as a free download from:
    http://developers.sun.com/prodtech/cc/downloads/sun_studio/index.html

  • Code generation bug in Sun Studio 12

    Hi,
    The following program prints `Failure' when compiled with -xO4 where nothing should be printed (when compiled with no optimization or -xO2). It looks to me that the first comparison `buggy_routine' against 0x80 is returning True where it should return False.
    #include <stdlib.h>
    #include <stdio.h>
    typedef unsigned long long int      EIF_NATURAL_64;
    typedef unsigned char   EIF_BOOLEAN;
    typedef int EIF_INTEGER_32;
    typedef char * EIF_REFERENCE;
    char s[] = "9223372036854775808";
    void buggy_routine (EIF_REFERENCE Current, EIF_NATURAL_64 arg1)
        EIF_NATURAL_64 tu8_1;
        tu8_1 = (EIF_NATURAL_64) ((EIF_INTEGER_32) 128L);
        if ((EIF_BOOLEAN) (arg1 <= tu8_1)) {
        } else {
            if ((EIF_BOOLEAN) (arg1 <= ((EIF_NATURAL_64)  9223372036854775808ull ))) {
            } else {
                  printf("Failure\n");
    int main (int argc, char ** argv, char **envp ) {
        EIF_NATURAL_64 loc2 = (EIF_NATURAL_64) 0;
        loc2 = (EIF_NATURAL_64) atoll(s);
        buggy_routine ("s", loc2);
    }To reproduce:
    cc -xO4 bug.c -o bug ; ./bug
    It fails on both 32 and 64-bit code generation for x86. I haven't tried on Sparc as I need to install Sun Studio 12. Is this a known issue? Is there an easy workaround?
    I tried with Sun Studio 11 and it worked just fine there.
    Regards,
    Manu
    PS: I've tried with both version (the first is the one from the default installation) and the second after I noticed there were some patches available:
    cc: Sun C 5.9 SunOS_i386 Patch 124868-01 2007/07/12
    cc: Sun C 5.9 SunOS_i386 Patch 124868-02 2007/11/27

    An issue filed at bugs.sun.com does not go directly into the bug database. It is evaluated, and if it turns out the report is actually a bug not previously reported, goes into the database. You get a notification and chance to reply after the report is evaluated.
    In this case, I picked up your report myself, and filed the bug. The bug ID is 6654314, and will be visible at bugs.sun.com in a day or two.

  • Core dump using iostream with Sun Studio 8

    I'm running on Solaris 9 using C++ compiler Sun Studio 8, and encoutered a very strange problem.
    My application failed with a core and here is the stack.
    [1] t_splay(0x3774b470, 0x387a0ec0, 0x389aec60, 0x39e5ef1f, 0x3774b470, 0x1), at 0xfc347930
    [2] t_delete(0x387a0ec0, 0x80, 0x39be9748, 0x20, 0x383ccd20, 0x0), at 0xfc347698
    [3] mallocunlocked(0x80, 0x0, 0x21b08, 0xfc3bc000, 0x10, 0x20), at 0xfc346d40
    [4] malloc(0x80, 0xfbaa7400, 0x1, 0x759c40, 0x0, 0x0), at 0xfc346b74
    [5] operator new(0x80, 0x0, 0xd3a18, 0x759c74, 0x0, 0x8345fc), at 0x760c10
    [6] strstreambuf::overflow(0xf41f6e28, 0x29, 0xf41f6e28, 0x39fe0e88, 0x39fe0e88, 0x8345fc), at 0x75bb1c
    [7] streambuf::xsputn(0xf41f6e28, 0xfee00bc0, 0x1, 0x0, 0x81010100, 0x1), at 0x75ab94
    [8] unsafe_ostream::outstr(0xf41f6e78, 0xfee00bbf, 0x0, 0x0, 0xf41f6e7c, 0xfffffffe), at 0x757bac
    =>[9] unsafe_ostream::operator<<(this = 0xf41f6e78, _s = 0xfee00bbf ")"), line 1211 in "iostream.h"
    [10] ostream::operator<<(this = 0xf41f6e74, _s = 0xfee00bbf ")"), line 1350 in "iostream.h"
    [11] CorInterfaceEntity::ifState(this = 0x1bc3de78, newState = MISMATCH_OF_INSTALLED_AND_EXPECTED, needToSendEvent = false
    Can somebody help me giving a direction of investigation ?
    Is there perhaps known problem with iostream on Sun Studio 8 running on Solaris 9 ?
    Thanks for any tips.
    Yaakov Berkovitch
    [email protected]

    But sorry for my insistence, but do you think that
    purify or/and runtime are not able to detect any
    corruption of the heap ?They can detect some kinds of corruption, such as some uses of an invalid pointer.
    But a wild pointer that changes the value of data that is part of your program cannot be detected by RTC or Purify. Those programs can't know whether that change is intentional.
    >
    BTW, we are not using any volatile declaration, and weIf non-local data is shared among threads, it should be declared volatile. For example, suppose you have
    x = foo;
    ... // code not changing foo
    y = foo;
    If foo is not marked volatile, the compiler is allowed to assume its value hasn't changed, and assign to y the same value assigned to x. If foo was changed by another thread, y will not have the current value of foo. The "volatile" declaration says that the variable's value might change without any obvious reason, and the compiler should generate code to load a fresh value each time it is referenced.
    are using the rwtools library packaged with the
    compiler, and are not using the STD library.OK, you are not running into a std::string synchronization bug.
    >
    Also about the compiler option -xarch=v8, is probably
    not relevant for us because we are running Solaris 9.
    So the relevant compiler is probably -xarch=v9. Do you
    advise us using this option ?I think you misunderstand. The -xarch values refer to the kind of processor your program will run on.
    The -xarch=v8 option generates 32-bit code that will run on all SPARC chips, including the chips found in very old SPARCstations. This option is the default for compilers prior to Sun Studio 9 (which ships this week).
    The -xarch=v8plus option generates 32-bit code that runs only on UltraSPARC chips, found in Ultra workstations. These are the only kinds of workstations shipped by Sun since about 1996. Unless you need to support the ancient SPARCstations, we recommend compiling with -xarch=v8plus, to get smaller and faster code.
    The -xarch=v9 option generates 64-bit code that runs only on UltraSPARC chips, an only on Solaris 7 or later. Unless your program requires a very large address space, you generally don't want to generate 64-bit code. On SPARC, 64-bit code is larger and slower than 32-bit code. (Type "long" and all pointers are 64 bits instead of 32 bits.)
    >
    Also I want to return you two new questions:
    1) I read in another discussion,
    http://forum.sun.com/thread.jsp?forum=5&thread=18124&me
    sage=47854#47854
    that another memory manager can be more efficient in
    multi-threaded environment (libmtmalloc.so), and also
    an alternate threads library (/usr/lib/lwp) that
    reduced CPU usage. Do you advice us using this
    alternate library ?The libmtmalloc library usually has better performance in MT programs than the default version of malloc. It also can result in more memory fragmentation. In that case, the larger working set can sometimes have a large negative effect, more than offsetting the MT efficiency. You have to experiment to see whether it is appropriate for your particlular program. If you are running into heap corruption, the pattern of corruption will probably be different with libmtmalloc than with the default malloc. The differences might provide a clue to what is wrong.
    The alternative "T2" threads library was introduced in Solaris 8 as an option.
    In Solaris 9 it is the default, so you are already using it.
    >
    2) We are using the Rogue Wave library shiped with the
    compiler. Is it an up-to-date version ? Can we assume
    that is a good choice or it will be preferable to move
    to the STD library ?I assume you mean Rogue Wave Tools.h++. As explained in the compiler docs, this version of Tools is obsolete, and has not been supported for many years. We continue to provide it for customers who used it before the introduction of the C++ Standard Library in 1998, and who don't want to change their code. We do not recommend it for use in new code.

  • After installing Sun Studio 11, libfsu.a in Sun Forte  6 is removed.

    I have Sun compilers 5.0 and 6.2 on my Sun Solaris 8 Ultra Sparc machine. After installing Sun Studio 11, some library files (e.g., libfsu.a in Sun Forte 6) from the old compilers were removed. What is wrong with my installation?
    Note that I install the different versions of compilers in separate directories.

    After the 1st failed installation of Sun studio 11,
    did you making sure that Sun studio 11 is not exist
    on your system before re-install Sun studio 11? The
    rule is you can have different Sun studio releases
    on the same system, but you can not have the
    multiple copy of the same release on the same
    system, even though they are in a totally separate
    directory. If Sun Studio 11 exist after 1st fail
    installation, you need to un-install it first before
    you re-start 2nd installation attemp.
    Installation of Sun Studio 11 should not remove files
    from older releases, but we know the case it did mess
    up package of the older release before.
    -NgocNo, after 1st install failed due to insufficient disk space, I did not uninstall Studio 11. After I deleted some user files to free up disk space, I run the install again, specified the same directory for installation, and just select Sun Performance Libraries. The installation seems to finished successfully. Perhaps this is one scenario where old versions can get messed up.

  • Sun studio patches on linux: how to deal with?

    hello all,
    on solaris 10, i'm using a tool like pca (1) to maintain sun studio up to date.
    But on linux, i don't know how to do the same process?
    I've a Centos on a Sun x2270, i've installed SS21u1 with rpms, and sometimes, i go to the patches website, and do the painful job of installing the latest patches.
    Is there another way? or a better process to get the latest rpms available?
    For instance, on solaris 10, pca loads afile name patchdiag.xref, in which i can find patches related to Sun Studio on Linux:
    grep -i 'Studio 12' /var/tmp/patchdiag.xref | grep -i Linux | awk -F\| '{print $1}'
    124874
    124877
    126497
    126997
    127145
    127149
    127154
    127158
    141856
    141859
    142367after that, i have to use pca with -r (README) flags, to find the name of the rpms:
    Files included with this patch:
    Note:
        sun-cpl-12.1-5.i386.rpm
        sun-cplx-12.1-5.x86_64.rpm
        sun-scl-12.1-5.i386.rpm
        sun-sclx-12.1-5.x86_64.rpm
        sun-stl4o-12.1-5.i386.rpm
        sun-stl4x-12.1-5.x86_64.rpm
        sun-tll7-12.1-5.i386.rpm
        sun-tll7x-12.1-5.x86_64.rpmthen, on linux, i have to query if the rpm is installed:
    bash-3.2# rpm -qa|grep sun-cpl
    sun-cpl-12.1-4
    sun-cplx-12.1-4and install it if needed:
    sudo rpm -Fvh /tmp/128230-04/*.rpmthanks in advance for help,
    gerard
    (1) [http://www.par.univie.ac.at/solaris/pca/] and a review by a sun guy: [http://blogs.sun.com/quenelle/entry/patch_check_advanced]

    Thanks Julien for this information.
    For a SCD Type 1 dimension I used IKM Oracle Incremental Update module and when I execute the interface I get ORA-01031: insufficient privileges error message because I have only read access on the source system. Based on your suggestion, ODI shouldn't access/need source system for staging purposes.
    What did I do wrong then?
    According with ODI documentation, IKM Oracle Incremental Update module: Integrates data in an Oracle target table in incremental update mode. This IKM creates a temporary staging table to stage the data flow. It then compares its content to the target table to guess which records should be inserted and which others should be updated. It also allows performing data integrity check by invoking the CKM. Inserts and updates are done in bulk set-based processing to maximize performance. Therefore, this IKM is optimized for large volumes of data. Consider using this IKM if you plan to load your Oracle target table to insert missing records and to update existing ones. If you plan to use this IKM with very large tables, you should consider enhancing this IKM by removing the MINUS set-based operator. To use this IKM, the staging area must be on the same data server as the target.

  • Migrating Solaris with out migrating Sun Studio

    HI ,
    Currently we are using sun studio 8 on solaris 8 to compile our application(C++).
    We are planning to migrate Solaris 8 to solaris 10. Will there be any problems, If we use sun studio 8 on sun solaris 10.
    Thanks and Regards,
    Venkat

    Mr.Bond wrote:
    HI ,
    Currently we are using sun studio 8 on solaris 8 to compile our application(C++).
    We are planning to migrate Solaris 8 to solaris 10. Will there be any problems, If we use sun studio 8 on sun solaris 10.Technically speaking, this combination is supported. However, it is rather old, it predates Solaris 10 and having all latest patches installed is a must (see http://developers.sun.com/sunstudio/downloads/patches/ss8_patches.html for list of patches available).
    If your final goal is to upgrade both OS and compiler, then switching to Solaris 10 and staying with Sun Studio 8 is a good idea; this way you minimize differences. After dealing with OS differences, you will be able to upgrade to Studio 12 update 1 (most recent release) more smoothly. Latest Sun Studio release is preferable because
    - its compiler better conform to the standard,
    - they generate better code,
    - whole suite works better on Solaris 10 since it was developed and tested on Solaris 10,
    - IDE is a huge improvement compared to Sun Studio 8.
    However, if you choose to stay with Sun Studio 8 (remember, end of support life is just one year away), I'd recommend purchasing support contract so that if you happen to run into a problem, it is solved with Sun Studio 8 patch, not in the next Sun Studio release (13?), which will be unacceptable for you.

  • Trouble viewing disassembly with Sun Studio 11

    I was wondering how someone can bring up a window with a program�s disassembly when debugging a C program with Sun Studio 11. (SPARC). I would like to be able to set breakpoints at specific assembly instructions using Sun Studios�s GUI interface rather than using typed commands with DBX. I would also like to know how to get a window that shows the current value of the registers. Any help would be greatly appreciated.
    Chris

    Oops, it appears that you can't set breakpoints
    through Disassembler window, it just shows the code
    and current position within the code, that's all.It
    gives you better view of context than dbx's 'dis' or
    'list -i' commands, though.Actually you can set breakpoints through Disassembler window:
    - select an address, click right mouse button to open context menu
    - choose "Set Breakpoint"
    If you need this feature, please file an RFE (Request
    For Enhancement) through bugs.sun.comThe Disassembler window has been significantly improved between
    EA1 and FCS. Now users can set and delete breakpoints using the
    same way as they do in source file - click on the left gray area (toggle
    breakpoints). Also Disassembler window has "Step Into", "Step Over",
    "Step Out" and "Run To Cursor" buttons.
    Thanks,
    Nik

  • How to report bugs for Sun Studio 12 update 1?

    I want to report a bug for the Sun Studio 12u1 C compiler, but bugreport.sun.com doesn't know about Sun Studio 12u1. The latest release know is SS12.
    Furthermore, the form doesn't allow to attach additional files, e.g. sources and other information needed to reproduce the problem.
    Since we have a valid service support contract with Sun, I used the official channel via the member support center, on January 15. Now, one month later, there is still no answer - and searching the databases both on sunsolve and bugreport.sun.com show, that my report hasn't gotten that far, yet.
    I really like Sun Studio, and I use it both for research and education, but reporting issues is really a problem. This somehow spoils the fun, both for the end users and the developers of a really great product!
    So the big question is: What is the best and quickest way to get bugs reported?
    Regards,
    Bernd

    If you have a support contract, the best way is to report via official channel; this is the only way to ensure that the bug is fixed in a patch for already released product. The fact that you can't find your report on sunsolve and bugreport.sun.com does not mean anything: not all bugs are public for obvious reasons.
    I think you should request an update via the same official channel; if you get nothing in a reasonable time (a day, I think), please report back here, we'll try to find out what's going on.

  • Will Sun Studio 12 Update 1 eventually show up with smpatch analyze?

    I have a Solaris 10 (sparc) box on which previous Sun Studio updates have been applied via smpatch. I was able to use smpatch analyze/download/update to find and apply the updates. Will Sun Studio 12 Update 1 eventually show up with smpatch analyze or will I need to manually install it?
    Thanks.
    Matthew

    I'm not 100% sure, but it is a different release, despite the name (12 update 1). Most, if not all, components have different version numbers compared to ones from Sun Studio 12.

  • Problem with setting Source Level in Sun Studio 2

    I've got problem with setting Source Level to 1.5 in Sun Studio 2. When I try to set it to 1.5 in Project properties and click Ok everything seem to go well, but when I open Project Properties again Source Level is set to 1.4. I need this to work cause I started to lear Java recently and I want to use foreach loop.
    Please help

    I'm just citing an example using Date().
    In fact, whether I use DateFormat or Calendar, it shows the same result.
    When I set the date to 1 Jan 1950 0 hours 0 minutes 0 seconds,
    jdk1.4.2 will always return me 1 Jan 1950 0 hours 10 minutes 0 seconds.
    It works correctly under jdk1.3.1

Maybe you are looking for