Studio 11 compiler error - SunIR version

I am trying to recompile my code after installing sun studio 11, but am getting compilation errors. If I compile my code using
f90 -KPIC -C -e -u -v -r8const mengmr5.f -c -O2
My files seem to compile ok. If instead I use
f90 -KPIC -C -e -u -v -r8const mengmr5.f
(without -O2) I get the following
### command line files and options (expanded):
### -xcode=pic32 -C -e -u -v -r8const mengmr5.f -c
### f90: Note: NLSPATH = /ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/f90comp -y-o -ymengmr5.o -N132 -ev -eI -y-ftrap=common -m3 -dq -y-fbe -y/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/fbe -y-xarch=generic -H "/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/f90 -KPIC -C -e -u -v -r8const -c " -y-xcache=generic -xcache=generic -I/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/include/f95/v8 -p/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/lib/modules -y-verbose -RM -xall -y-PIC -PIC -y-xcode=pic32 -xmemalign=8i -y-xmemalign=8i -r8const -y-xdbggen=no%dwarf2+stabs -xassume_control=optimize -y-xassume_control=optimize -iorounding=processor-defined -xhasc=yes mengmr5.f
Build problem: Yabe expected SunIR version 7.0.0; got 7.1.3
Studio 11 is installed in /ford/thishost/unix/loc/studio11/opt/SUNWspro, which I added to my path. I also have LD_LIBRARY_PATH as /ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/lib:/ford/thishost/unix/loc/studio11/opt/SUNWspro/lib:/usr/local/lib:/usr/dt/lib:/usr/lib:/usr/openwin/lib:/usr/4lib:/usr/sfw/lib:/usr/share/lib:/usr/local/link/lib:/ford/thishost/u/Tools/SunOS/5.8/lib:/ford/thishost/u/Tools/SunOS/5.8/lib
If I build optimized, I have problems debugging as I cannot see values in optimized functions. Is there a way to fix this?

Try unsetting your LD_LIBRARY_PATH.
You should not need it.
If it is not that,
then you probably have some problem with your installation
of the compilers.
Check the installation logs and any patch logs for clues.
Peter.
-pd 2/22/06

Similar Messages

Studio 8 compiler error using rogue wave header in std mode

I get the following compiler error. I am using -library=rwtools7_std in the CC command.
The error is:-
"/opt/studio/SUNWspro/prod/include/CC/rw7/rw/rstream.h", line 46: Error: The name istream is ambiguous, istream and std::istream.
"/opt/studio/SUNWspro/prod/include/CC/rw7/rw/rstream.h", line 46: Error: The name istream is ambiguous, istream and std::istream.
"/opt/studio/SUNWspro/prod/include/CC/rw7/rw/rstream.h", line 46: Error: The type "istream" is incomplete.
Please help
Kandiah

All,
I'm getting the following error when I moved to Rogue Wave release 7.0 from 4.0. We're using Sun's FORTE C++ compiler version 7.0.
Please advise
*** Build for src 'all' target STARTED: Thu Jan 18 16:37:04 EST 2007
/xenv/Forte/sun4/7.0/5.8p4/prod/bin/CC -g -features=no%conststrings -DCPLUSREL=7 -D_RWCONFIG=12d -DRW_MULTI_THREAD -O -mt -D_REENTRANT -c -I. -I/xenv/rwsp_tools/sun4/5.8p4/7.0/32/core900_12d -I/xenv/mqi/sun4/5.x/5.3.0.5/inc -I/xenv/ccs_standard_s8/sun4/5.8p4/4.1_B1/include MQInfo.cc MQBase.cc ZeusAccountBridge.cc
MQInfo.cc:
MQBase.cc:
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/stringid.h", line 50: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/stringid.h", line 51: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/collint.h", line 75: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/collint.h", line 76: Error: A typedef name cannot be used in an elaborated type specifier..
7 Error(s) detected.
ZeusAccountBridge.cc:
"/xenv/ccs_standard_s8/sun4/5.8p4/4.1_B1/include/ccs_data.h", line 126: Warning (Anachronism): Using int(*)(void*,ccs_Data*) to initialize void*.
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier..
3 Error(s) and 1 Warning(s) detected.

Sun studio C++ compilation error in std when compile ACE5.2

CC -mt -g -instances=explicit -g -I/home/xxx/ACE_wrappers -DACE_NO_INLINE -c -KPIC -o .shobj/Basic_Types.o Basic_Types.cpp
"/opt/SUNWspro/prod/include/CC/Cstd/./stdexcept", line 57: Error: Function std::logic_error::~logic_error() can throw only the exceptions thrown by the function std::exception::~exception() it overrides.
"/opt/SUNWspro/prod/include/CC/Cstd/./stdexcept", line 60: Error: Function std::logic_error::what() const can throw only the exceptions thrown by the function std::exception::what() const it overrides.
"/opt/SUNWspro/prod/include/CC/Cstd/./stdexcept", line 128: Error: Function std::runtime_error::~runtime_error() can throw only the exceptions thrown by the function std::exception::~exception() it overrides.
"/opt/SUNWspro/prod/include/CC/Cstd/./stdexcept", line 131: Error: Function std::runtime_error::what() const can throw only the exceptions thrown by the function std::exception::what() const it overrides.
"/opt/SUNWspro/prod/include/CC/Cstd/./istream", line 41: Error: Use ";" to terminate declarations.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 438: Error: Illegal number of arguments for std::ostream::operator<<(std::basic_ostream<std::basic_ostream<std::charT, std::traits>::charT, std::basic_ostream<std::charT, std::traits>::traits>&, std::ostream::charT).
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 43: Where: While specializing "std::ostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 43: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 444: Error: Illegal number of arguments for std::ostream::operator<<(std::basic_ostream<std::basic_ostream<std::charT, std::traits>::charT, type "std::ostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 43: Where: While specializing "std::ostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 43: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 438: Error: Illegal number of arguments for std::wostream::operator<<(std::basic_ostream<std::basic_ostream<std::charT, std::traits>::charT, std::basic_ostream<std::charT, std::traits>::traits>&, std::wostream::charT).
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 46: Where: While specializing "std::wostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 46: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 444: Error: Illegal number of arguments for std::wostream::operator<<(std::basic_ostream<std::basic_ostream<std::charT, std::traits>::charT, std::basic_ostream<std::charT, std::traits>::traits>&, char).
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 46: Where: While specializing "std::wostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 46: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 451: Error: Illegal number of arguments for std::wostream::operator<<(std::ostream &, char).
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 46: Where: While specializing "std::wostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./iostream", line 46: Where: Specialized in non-template code.
Compilation aborted, too many Error messages.
make: *** [.shobj/Basic_Types.o] Error 1
sun0% CC -V
CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25

I have solved the problem by adding "-D ACE_HAS_EXCEPTIONS"

Compilation error while building boost 1_44_0 on Solaris (Sun Studio 10)

Hi All, I am trying to build boost version 1_44_0 on Solaris.The Solaris box has Sun Studio 10 installed.
The compiler details are
bash-2.05$ CC -V
CC: Sun C++ 5.7 2005/01/07
I am using the following command to build boost libraries
*bash-2.05$ bjam --build-dir=/export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost toolset=sun stage*
But i get the below compilation errors, not even one of the projects build
sun.compile.c++ /export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost/boo
st/bin.v2/libs/iostreams/build/sun/release/stdlib-sun-stlport/threading-multi/fi
le_descriptor.o
Notice: The Early Access serial number will expire in -7 days.
In order to purchase the product, visit http://www.sun.com/forte/buy.html
or contact your Forte Tools reseller.
"libs/iostreams/src/file_descriptor.cpp", line 352: Error: Could not find boost:
:shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i
ostreams::detail::file_descriptor_impl*) to initialize pimpl_.
"libs/iostreams/src/file_descriptor.cpp", line 355: Error: Could not find boost:
:shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i
ostreams::detail::file_descriptor_impl*) to initialize pimpl_.
"libs/iostreams/src/file_descriptor.cpp", line 360: Error: Could not find boost:
:shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i
ostreams::detail::file_descriptor_impl*) to initialize pimpl_.
"libs/iostreams/src/file_descriptor.cpp", line 380: Error: Could not find boost:
:shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i
ostreams::detail::file_descriptor_impl*) to initialize pimpl_.
"libs/iostreams/src/file_descriptor.cpp", line 385: Error: Could not find boost:
:shared_ptr<boost::iostreams::detail::file_descriptor_impl>::shared_ptr(boost::i
ostreams::detail::file_descriptor_impl*) to initialize pimpl_.
"libs/iostreams/src/file_descriptor.cpp", line 393: Error: Using static_cast to
convert from boost::iostreams::file_descriptor_flags to boost::iostreams::detail
::file_descriptor_impl::flags not allowed.
6 Error(s) detected.
"CC" -library=stlport4 -xO4 -mt -erroff=%none -KPIC -DBOOST_ALL_NO_LIB=1 -DB
OOST_IOSTREAMS_DYN_LINK=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o
"/export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost/boost/bin.v2/libs/
iostreams/build/sun/release/stdlib-sun-stlport/threading-multi/file_descriptor.o
" "libs/iostreams/src/file_descriptor.cpp"
...failed sun.compile.c++ /export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build
-boost/boost/bin.v2/libs/iostreams/build/sun/release/stdlib-sun-stlport/threadin
g-multi/file_descriptor.o...
sun.compile.c++ /export/home/dfdev/Boost_1_44_0/boost_1_44_0/tmp/build-boost/boo
st/bin.v2/libs/iostreams/build/sun/release/stdlib-sun-stlport/threading-multi/ma
pped_file.o
Notice: The Early Access serial number will expire in -7 days.
In order to purchase the product, visit http://www.sun.com/forte/buy.html
or contact your Forte Tools reseller.
"./boost/type_traits/is_array.hpp", line 41: Error: Multiple declaration for boo
st::is_array.
"./boost/type_traits/is_array.hpp", line 42: Error: Multiple declaration for boo
st::is_array.
"./boost/type_traits/is_array.hpp", line 43: Error: Multiple declaration for boo
st::is_array.
"./boost/type_traits/is_array.hpp", line 44: Error: Multiple declaration for boo
st::is_array.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 95: Error: The type
of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1> is dependent on
another argument.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 95: Error: Partial s
pecialization parameter Tag is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 112: Error: Partial
specialization parameter F is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 172: Error: The type
of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux
::P2> is dependent on another argument.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 172: Error: Partial
specialization parameter Tag is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 189: Error: Partial
specialization parameter F is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 254: Error: The type
of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux
::P2, boost::mpl::aux::P3> is dependent on another argument.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 254: Error: Partial
specialization parameter Tag is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 271: Error: Partial
specialization parameter F is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 339: Error: The type
of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux
::P2, boost::mpl::aux::P3, boost::mpl::aux::P4> is dependent on another argument
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 339: Error: Partial
specialization parameter Tag is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 357: Error: Partial
specialization parameter F is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 427: Error: The type
of specialized argument boost::mpl::aux::F<boost::mpl::aux::P1, boost::mpl::aux
::P2, boost::mpl::aux::P3, boost::mpl::aux::P4, boost::mpl::aux::P5> is dependen
t on another argument.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 427: Error: Partial
specialization parameter Tag is not used in the arguments.
"./boost/mpl/aux_/preprocessed/plain/full_lambda.hpp", line 445: Error: Partial
specialization parameter F is not used in the arguments.
"libs/iostreams/src/mapped_file.cpp", line 441: Error: Could not find boost::sha
red_ptr<boost::iostreams::detail::mapped_file_impl>::shared_ptr(boost::iostreams
::detail::mapped_file_impl*) to initialize pimpl_.
20 Error(s) detected.
Am i missing something? I will appreciate your input's.
Regards,
solarisneo

C++ 5.7 will not give good results building Boost.
Support for boost began with C++ 5.9 (Sun Studio 12), but you will get better results using the current release, Sun Studio 12 update 1, and better still with the upcoming release, Oracle Solaris Studio 12.2.

Sun Studio 11 f90 INTERNAL COMPILER ERROR: "FWOutput"

Hello SUN-Users,
I am new here, so I don't know I am right here!?
I have a w2100z with two opteron proc. With Sun Studio 11 I am trying to compile the new MUMPS (Ver. 4.6) package, but I get still the error message:
f90 -I/opt/mpich/include -Dpord -I. -I../include -c dmumps_ooc.F
1:LEN$1:1INTERNAL COMPILER ERROR near line 2494 in dmumps_ooc.F (phase FWOutput):
FWOutput: no visit function for class 'SubscriptTriplet'
*** Error code 1
make: Fatal error: Command failed for target `dmumps_ooc.o'
I search with google for "FWOutput" and I found out, that a similar problem already was recognized in Sun Studio 9 and fixed with the patch 115985-04 (6351156 f90 compiler internal error "FWOutput: no vist function for class 'SubscriptTriplet').
Here is some code near line 2494 from file dmumps_ooc.F:
      SUBROUTINE DMUMPS_614(id)
      I=id%MYID
      J=id%OOC_NB_FILES
      K=id%KEEP(35)
      L=MOD(id%KEEP(204),3)
TMP_DIR=TRIM(id%DMUMPS_OOC_TMPDIR)
      TMP_FILE=TRIM(id%DMUMPS_OOC_PREFIX)
      DIM_DIR=LEN(TRIM(id%DMUMPS_OOC_TMPDIR))
      DIM_FILE=LEN(TRIM(id%DMUMPS_OOC_PREFIX))
    END SUBROUTINE DMUMPS_614The bolded line is the line 2494.
I can not see anything worng in this routine, but maybe I am already too tired for today.... :-)
Realy it is important to me to compile the MUMPS package,
so I hope somebody can help me?
****With best regards****

I think the TRIM should remove last character of the
string. (?)TRIM removes the trailing blanks in a string. String assignment then adds trailing blanks, so there's no point writing something like
s1 = TRIM(s2)
Can you say me where can I make a bug report? What is
to do?
Maybe next time I can do also a bug report?That's a good question. If you have a support contract, then you should be able to submit a bug report through that. Until recently, I believe that would have been the only way to do it. However, we now have an online support service:
http://developers.sun.com/developer_help/
I imagine you could get a bug filed through that channel as well.

I am running an old legacy Sun server (Solaris10 U7) and need a compiled 64 bit version of liblpSolve55. I don't have studio or R, and very limited knowledge of C.

Can anyone help, or point me in the correct direction ?
I have tried downloading source and compiling but get all sorts of gcc compiler errors, and as I'm not conversant with compilers, C or anything similar, need a precomiled version of this library.
Any help very gratefully received.
Charles Richards

That's a comment in the file. It has no effect at all.

Exceptions not caught in shared library when compiled under Sun Studio 9

I realize it's a fairly old version of Sun Studio, however if at all possibly we'd like to avoid updating to the latest.
Sun Studio 9, version reports
version of "/opt/SUNWspro/bin/../prod/bin/../../bin/cc": Sun C 5.6 2004/07/15
version of "/opt/SUNWspro/bin/../prod/bin/../../bin/CC": Sun C++ 5.6 2004/07/15
uname -a
SunOS sunblade 5.9 Generic_118558-27 sun4u sparc SUNW,Sun-Blade-100
The problem is within our shared library a function calls another method within a try/catch block. This method then sometimes throws an exception which does have a matching catch block. On all other systems (Windows, AIX, HP-UX, Linux) the code works, the exception is caught and handled. On Solaris with Sun Studio 9 though, the exception is ignored and instead triggers an abort and core dump.
Stack Trace:
ffffffff7daa871c lwpkill (6, 0, ffffffff7fffd9c0, ffffffff7d3064d4, 2, ffffffff7fffd9ec) + 8
ffffffff7da3e4b8 abort (ffffffff7d40dac8, ffffffff7d40cc38, ffffffff7d411e78, 10604c, 2, ffffffff7d40dac8) + 100
ffffffff7d3064d4 __1cH__CimplRdefault_terminate6F_v_ (ffffffff7d40dac8, ffffffff7d40cc38, ffffffff7d411e78, 10604c, 104e40, ffffffff7d3064d0) + 4
ffffffff7d3062b4 __1cH__CimplMex_terminate6F_v_ (ffffffff7d40de40, 0, 0, ffffffff7d40de40, ffffffff7d40c978, 1) + 24
ffffffff7d306f04 exthrow_body (ffffffff7d40de40, 0, 0, 105af4, 52, ffffffff7d40e2e8) + 84
ffffffff7d306e58 __1cG__CrunIex_throw6Fpvpkn0AQstatic_type_info_pF1_v_v_ (ffffffff7d40dec8, ffffffff7f0dea78, ffffffff7ecb6b28, ffffffff7d40de40, 0, ffffffff7d40de40) + 3c
ffffffff7ecb6d90 __1cLIGExceptionFThrow6FnQenumIGErrorCodes_pkcxxp2x_v_ (fffffffffffff3e3, 0, 0, 0, ffffffff7f1187da, a0) + 80
ffffffff7ecb6e78 __1cOThrowException6FnQenumIGErrorCodes_pkcxxp1x_v_ (fffffffffffff3e3, 0, 0, 0, ffffffff7f1187da, a0) + 30
ffffffff7f083304 __1cSIGRasterProcessingNVerifyPalette6FpnMIGRasterPage_nTenumIGContrastModes__v_ (1001f3c10, 0, 0, 0, 0, 0) + b4
ffffffff7f083760 __1cSIGRasterProcessingOInvertContrast6FpnMIGRasterPage_nTenumIGContrastModes_nTenumIGColorChannels_pnPtagAT_RECTANGLE__v_ (1001f3c10, 0, 0, ffffffff7fffe1a8, 0, 0) + 20
ffffffff7f039a2c iIG_IP_contrast_invert (1001f3c10, 100162b10, 0, 0, 0, 0) + 104
ffffffff7f039ba0 iIG_IP_contrast_invert_masked (1001f3c10, 100162b10, 0, 0, 0, 0) + 80
000000010000b4e0 ipcontrast_invert_notify (10014d000, 10014d, 0, 100000, 100162000, 100162) + 48
Try/catch block:
     try
          <Triggering function>
     catch(const IGException& ige)
          <Handling Code>
The code which throws the exception is a static method of IGException which has a basic throw line:
     throw IGException(...);
Source code is compiled with the following flags, none of which I could find any info to suggest affect this:
CC -c -Xt -xCC -misalign -xarch=v9 -O
Linking of the shared object is then done via the following, again nothing obvious that could cause issues. mapfile is an empty file.
ld -o <outputfilename> -G -z textoff -M mapfile -z noversion -64 -h <outputfilename> <object files> -L/opt/SUNWspro/lib/v9 -lCrun -lX11 -lc -lm
I did read somewhere mentioning to make sure to use RTLD_GLOBAL if using dlopen on the .so, but the test app is using ld to link the library.
Does anyone have any ideas why with the Sun Studio 9 compiler these exceptions are not being caught? Based on the fact they are caught on all other compilers, i'm guessing this issue is with the compiler.
Also, as a test it seems that if the shared object is not built as a 64-bit object, then everything works. The issue only seems to occur when it is a 64-bit object. Likely an issue with the 64-bit compiling?
Edited by: 837682 on Feb 17, 2011 9:23 AM

As the other poster pointed out, you need to link the shared library using CC, not ld. I should have noticed that error in the original post.
Try using CC instead of ld in your link command. The CC command causes additional files to be linked into the shared library that are required for proper operation, and particularly for exception handling. I think that is the actual source of your problem.
You should not use -L options that point into the compiler installation area, and when you use CC to link, you don't need to.
I'm surprised that you seem to have a copy of libCrun.so.1 in the compiler installation area -- that should not be the case. The the only versions of libCrun should be static libraries libCrun.a. You almost never want to link with a static version of a system library, and absolutely never when building a shared library. The file /opt/SUNWspro/lib/libCrun.so.1 ought to be a symbolic link pointing to /usr/lib/libCrun.so.1, but if that were the case, the version command would have the same output.
By any chance, did you install your compiler by copying it from another installation? If you do that, you need to use tar, not cp, to ensure that symbolic links are preserved.

Problem in compilation using Sun Studio 11

Hello,
We are migrating from a Solaris 8 to a Solaris 10 OS. At the same ttime we are also migrating from Ingres 2.6 to Ingres 2006. As a part of the creation of teh development environment, we are recompiling all the codes on teh new OS. WE have installed teh Sun Studio 11 compiler for this purpose. When compiling some C codes, we are getting the following error:
"am_xxxxxxxx.c", line 2596: warning: statement not reached
"am_xxxxxxxx.c", line 2778: undefined symbol: i8
"am_xxxxxxxx.c", line 2778: syntax error before or at: )
"am_xxxxxxxx.c", line 2858: undefined symbol: i8
"am_xxxxxxxx.c", line 2858: syntax error before or at: )
"am_xxxxxxxx.c", line 2889: warning: implicit function declaration: IIresnext
"am_xxxxxxxx.c", line 2891: warning: statement not reached
"am_xxxxxxxx.c", line 2920: warning: statement not reached
"am_xxxxxxxx.c", line 2931: undefined label: IIfdF1
"am_xxxxxxxx.c", line 2931: undefined label: IIosl9139
"am_xxxxxxxx.c", line 2931: undefined label: IIfdE1
"am_xxxxxxxx.c", line 2931: cannot recover from previous errors
cc: acomp failed for am_xxxxxxxx.c
The command used for compiling is :
cc -xarch=generic64 am_xxxxxxxx.c
We have exported teh following:
LD_LIBRARY_PATH_64=/usr/sfw/lib/sparcv9:/usr/local/lib/sparcv9:/usr/lib/sparcv9:/usr/openwin/lib/sparcv9:/usr/dt/lib/sparcv9:/opt/SUNWspro/lib/v9:/opt/SUNWspro/lib/v9:/eu/ingad/ingres/lib:/opt/oracle/lib:/usr/lib:/usr/ucblib:/usr/openwin/lib:/opt/SUNWspro/lib/:/opt/lib/cobol/coblib
LD_LIBRARY_PATH=/opt/SUNWspro/lib/v9:/eu/ingad/ingres/lib:/eu/ingad/ingres/lib:/opt/oracle/lib:/usr/lib:/usr/ucblib:/usr/openwin/lib:/opt/SUNWspro/lib/:/opt/lib/cobol/coblib
CXXFLAGS=-fast -xarch=v9b
CFLAGS=-fast -xarch=v9b
LDFLAGS=-L/usr/sfw/lib/sparcv9 -L/usr/lib/sparcv9 -R/usr/sfw/lib/sparcv9 -R/usr/lib/sparcv9
We are struggling with this issue for the last one week. Can someone please help me with this issue?
Could this be because the 64 bit library files are not installed? Please help.
Aneesha

The LD_LIBRARY_PATH environment variables determine where the runtime loader looks for shared libraries when you run an application. It is unlikely to be the source of compile-time errors.
I suspect that doing two major changes at the same time has resulted in undefined names and other problems, probably due to missing or incorrect header inclusion. If possible, make one change at a time, either compile the old code on the new OS, or the new code on the old OS, and get that to work first.
Check the Ingress documentation to see if you need to make source code changes when upgrading, and follow any recommendations there. You might also need to take up this problem with Ingress tech support.
Regarding LD_LIBRARY_PATH, the best advice is usually "don't set it at all". For more on this topic, see this article:
http://blogs.sun.com/rie/entry/tt_ld_library_path_tt
Just to eliminate this as a possible build problem, try removing LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 from your environment when building the program. Then modify the build process to set the executable runpath (-R option) to include the Ingress or Oracle libraries that need to be searched. You don't normally want to point into /usr/lib or into the compiler installation area.

F90 version 8.5 INTERNAL COMPILER ERROR

Hi,
Check the following program:
program p
TYPE :: boxnode
TYPE (boxnode), POINTER :: lft
END TYPE boxnode
TYPE (boxnode), pointer :: ra1(:)
TYPE (boxnode), pointer :: ra2(:)
integer :: st(2)
allocate (ra1(5),stat=st(1))
allocate (ra2(5),stat=st(2))
end program p
If I compile this on my solaris x86 system with 'f90 test.f90', I get:
INTERNAL COMPILER ERROR near line 10 in test.f90 (phase FWFinalize):
Assertion failed: result_type->is_scalar() && op1_type->is_scalar() && op2_type->is_scalar()
[internal line 1414 /net/desna.sfbay/export/home/train_builds/aten_intel-S2/100813.intel-S2/lang/f90/fe/srcme/compiler/phases/fwoutput/fwfinalize.cpp]
This, I think, is obviously a compiler bug.
f90 -V
f90: Sun Fortran 95 8.5 SunOS_i386 2010/08/13
Is there anyone from oracle listening in who can submit this as a bug?
And can I get a patch? Or do I need a contract for that?
Regards,
Nico

>
INTERNAL COMPILER ERROR near line 10 in test.f90 (phase FWFinalize):
Assertion failed: result_type->is_scalar() && op1_type->is_scalar() && op2_type->is_scalar()
>
I've seen that very same error with one of the codes I've tried to compile with Solaris Studio. I'm sorry that I cannot be more helpful right now, I don't even remember which one it was in the long list I'm working with, but it's not an isolated case. I'll wait for the explanation and try to reember it when I'll hit the issue again.

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

Help ! ever seen this in DVD Studio Pro : 'Compiler File Error' ?

Help !
This is a strange problem :
Evertime I try to burn a disc, it says :
Starting DVD Build DVD_
Compiler File Error
Build cancelled
Formatting finished.
Building was not successful. See log.
Now I tried several different projects and it does it on multiple computers.
Only explenation would be something I did in my DVD menu, or assets.
If I burn it on my powerbook though, it works perfectly....
Harry Potter was busy, so please help me, I'm getting desperate...
Have the latest update, the latest OS, en DVD Studio Pro 4.2

Welcome to the boards.
Take a look at the log as it is compiling and see where the compile stops/crashes. Also download MPEG streamclip and open up the last VOB in the build folder in MPEG Streamclip. (VOB ares here, you will have different VOBs of course and numbers but look at the last one that has something in it) http://dvdstepbystep.com/vts.php It will show you the last part was compiled properly so you can look at the asset in the DVD SP project.
Some things to look for
1.) Gaps in the timeline in the audio or video. In fact I just had this happen. The project compiled fine in an older version of DVD SP (4.03) BUT would crash out at 4.2. Turns out there was a gap I had missed (doh!) somehow and cleaning it up would then cure then problem.
2.) Did you make the audio AC3? What rates were the video encode? High rates can cause the compile errors.

Syntax error at line1 : �(� fortran90 compiler of SUN OS 5.6.

Does anyone know what this mean and how to correct the error?
�./some_program :syntax error at line1 : �(� unexpected
I executed the fortran 90 program under Sun OS 5.6 with SPARC platform.
The sun.com website do not provide the trial version fortran90 compiler of SUN OS 5.6.
Would you please tell me how to download the old version fortran90?!
Thanks in advance!

I notice your earlier post asking for download of f90 compiler. You may have installed the latest f90 and run it on your old OS 5.6. I suggest you upgrate your OS to S10. S5.6 is EOL and no long supported. And S10 is much better. If you want to keep 5.6, you may try this site for an old compiler:
http://www.sun.com/software/sundev/previous/fortran/buy.html

Compile error in hidden module: Essbaselogon. This error commonly occurs when code is incompatible with the version, Platform, or architecture of this application

Hi,
I am getting below wrror while accesing the Ecel:
compile error in hidden module: Essbaselogon. This error commonly occurs when code is incompatible with the version, Platform, or architecture of this application

IIRC essbase is a financial reporting add-in (Hyperion, or something similar?).
This message is telling you that the add-in is not compatible with your current software. You should check with the vendor who provided the essbase add-in. Tell them what version of windows and Excel (and maybe Hyperion) you are using, and get a compatible
version from them...
If you do not need or run essbase/hyperion/etc then you should just remove/disable the add-in. If it doesn't show in your add-in menu, then you may have to do a repair installation or re-install Excel

Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
As the editor and its compiler do not see the error and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
Our project comprises hundreds of Vis over several libraries.
Thanks,
Chris

Thanks Craig for all your suggestions.
We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
We will post about this in detail after we have positively proven that this actually was the case.
The .net version issue was already checked.
Performance was the same on all machines we tested on including the dev machine.
Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
In relation to your remark:
'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
Ragrds,
Chris

Compile Error for Import com.sun.javadoc.*;

I need to write some simple doclets and found some beginner code on the Sun website. The first line of the sample app is:
import com.sun.javadoc.*;However, I get a compile error:
C:\JavaDoc\Doclet\ListClass.java:1: package com.sun.javadoc does not exist
import com.sun.javadoc.*;I found the com.sun.javadoc package in the tools.jar file in the lib directory of my sdk. So I added the following to my classpath:
C:\j2sdk1.4.2_08\lib;Then I recompiled but received the same error. What have I done wrong? I'm on Windows XP.
TIA.

> C:\j2sdk1.4.2_08\lib;
C:\j2sdk1.4.2_08\lib\tools.jar;

Studio 11 compiler error - SunIR version

Similar Messages

Maybe you are looking for