Compiling with rmic on Solaris

I tried to compile some of my activatable RMI objects on a Solaris system. Javac goes well, but rmic seems to have problems.
I always get an error message that "java.rmi.activation.activatable" isn't in my Activatable Object.
Funny thing is...This code compiles and runs under both windows and linux versions of java 1.2.1.
Anybody have any ideas?

This is what I get from the server:
I type:
<s975183@hswis> $ rmic -classpath . DataServerImplement
And I get:
error: Class java.rmi.activation.Activatable not found in class DataServerImplement.
1 error
This is the java version:
<s975183@hswis> $ java -version
java version "1.2.1"
Solaris VM (build Solaris_JDK_1.2.1_04c, native threads, sunwjit)

Similar Messages

PCC-S-02014 error while compiling with in Sun Solaris

We are porting our application from HP-UX to Sun Solaris and as part of that I am trying the compile a Pro*C program in Sun Solaris using SUNWspro C++ compiler. Precompiling is failing with following error.
PRECOMP set: /u01/app/oracle/product/10.2.0/bin/proc dbms=native code=cpp mode=ansi include=/u01/app/oracle/product/10.2.0/precomp
ireclen=255 oreclen=255
define=__sparc define=__SUNPRO_C include=/usr/include include=. include=/u01/app/SUNWspro/prod/include/CC/stlport4 include=/u01/app/oracle/product/10.2.0/rdbms/public/ include=/u01/app/oracle/product/10.2.0/network/public/ include=/u01/app/oracle/product/10.2.0/rdbms/demo/ errors=yes select_error=no
sqlcheck=limited ltype=NONE
release_cursor=no hold_cursor=no
Pro*C/C++: Release 10.2.0.3.0 - Production on Thu Dec 18 03:09:59 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
System default option values taken from: /u01/app/oracle/product/10.2.0/precomp/admin/pcscfg.cfg
Syntax error at line 44, column 30, file /u01/app/SUNWspro/prod/include/CC/stlport4/algorithm:
Error at line 44, column 30 in file /u01/app/SUNWspro/prod/include/CC/stlport4/a
lgorithm
# include STLPNATIVE_HEADER(algorithm)
.............................1
PCC-S-02014, Encountered the symbol "(" when expecting one of the following:
: [ ] + / . .. an identifier, a numeric constant, newline,
define, elif, else, endif, error, if, ifdef, ifndef, include,
line, pragma, undef, exec, sql, begin, end, var, type,
oracle, an immediate preprocessor command, a C token, create,
function, package, procedure, trigger, or, replace,
Normal C++ files are getting compiled with out eny issues. This particular file is having functions written in C fashion. Any idea what is missing in the compiler option.
regards
Vinu

Hi Vinu,
I'm not sure if this is still an issue for you. When I have encountered issues like this with Pro*C I have ended up specifying parse=none to the proc command and then putting all declarations between "EXEC SQL BEGIN DECLARE SECTION" and "EXEC SQL END DECLARE SECTION" markers. I have also moved any "special" declarations into a specific header file and then placed the "#include <special header file>" inside the declare section as well.
Perhaps that will help a bit,
Regards,
Mark

Help!Apache compiling with gcc in Solaris 10

Greetings
I am having problems with Apache 1.3.
When I am running the script ./src/Configure my output is:
#./Configure
Using config file: Configuration
Creating Makefile
+ configured for Solaris 2100 platform
+ setting C pre-processor to gcc -E
+ using "tr [a-z] [A-Z]" to uppercase
+ checking for system header files
+ adding selected modules
./helpers/TestCompile: make: not found
+ using builtin Expat
./Configure: make: not found
+ checking sizeof various data types
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
./helpers/TestCompile: make: not found
+ doing sanity check on compiler and options
./helpers/TestCompile: make: not found
** A test compilation with your Makefile configuration
** failed. The below error output from the compilation
** test will give you an idea what is failing. Note that
** Apache requires an ANSI C Compiler, such as gcc.
======== Error Output for sanity check ========
./helpers/TestCompile: make: not found
============= End of Error Report =============
Aborting!
I am root, my PATH is
/usr/bin:/usr/ucb:/etc:/usr/local/bin:/opt/netscape:/usr/css/bin/:/bin:/usr/openwin/bin:/usr/sbin:/
I am missing something stupid, I know but I can't find it!!!!Help please I am a newbie.
I am curious. Has anyone been able to compile succesfully apache server with gcc in Solaris 10?
Thanks,

Thanks,
It was only that.!!!
But now I have the following problem, I can't create executables when I type make. The output is:
when I am in the src/folder
#make
===> regex
<=== regex
===> os/unix
gcc -c -I../../os/unix -I../../include -DSOLARIS2=2100 -DUSE_HSREGEX -DUSE_EXPAT -I../../lib/expat-lite -DNO_DL_NEEDED os.c
In file included from /usr/include/sys/wait.h:24,
from ../../include/ap_config.h:1079,
from os.c:21:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:294: error: parse error before '}' token
/usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
/usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
/usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
/usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
/usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
/usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
/usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
/usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
/usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
/usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
/usr/include/sys/siginfo.h:426: error: parse error before '}' token
/usr/include/sys/siginfo.h:428: error: parse error before '}' token
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
In file included from /usr/include/sys/procset.h:24,
from /usr/include/sys/wait.h:25,
from ../../include/ap_config.h:1079,
from os.c:21:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from ../../include/ap_config.h:1079,
from os.c:21:
/usr/include/sys/wait.h:86: error: parse error before "siginfo_t"
In file included from ../../include/ap_config.h:1096,
from os.c:21:
/usr/include/signal.h:111: error: parse error before "siginfo_t"
/usr/include/signal.h:113: error: parse error before "siginfo_t"
*** Error code 1
make: Fatal error: Command failed for target `os.o'
Current working directory /web-download/apache_1.3.33/src/os/unix
*** Error code 1
The following command caused the error:
for i in regex os/unix ap main lib modules; do \
echo "===> $i"; \
case ".Solaris 2100" in \
.OS390 | .TPF) ( cd $i && make SDP='' OPTIM='') || exit 1;; \
*) ( cd $i && make SDP='' CC='gcc' AUX_CFLAGS=' -DSOLARIS2=2100 -DUSE_HSREGEX -DUSE_EXPAT -I./lib/expat-lite -DNO_DL_NEEDED ' RANLIB='ranlib' OPTIM='') || exit 1;; \
esac; \
echo "<=== $i"; \
done
make: Fatal error: Command failed for target `subdirs'
but when I am typing one step up is.
===> src
===> src/regex
<=== src/regex
===> src/os/unix
gcc -c -I../../os/unix -I../../include -DSOLARIS2=2100 -DUSE_HSREGEX -DUSE_EXPAT -I../../lib/expat-lite -DNO_DL_NEEDED os.c
In file included from /usr/include/sys/wait.h:24,
from ../../include/ap_config.h:1079,
from os.c:21:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:294: error: parse error before '}' token
/usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
/usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
/usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
/usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
/usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
/usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
/usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
/usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
/usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
/usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
/usr/include/sys/siginfo.h:426: error: parse error before '}' token
/usr/include/sys/siginfo.h:428: error: parse error before '}' token
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
In file included from /usr/include/sys/procset.h:24,
from /usr/include/sys/wait.h:25,
from ../../include/ap_config.h:1079,
from os.c:21:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from ../../include/ap_config.h:1079,
from os.c:21:
/usr/include/sys/wait.h:86: error: parse error before "siginfo_t"
In file included from ../../include/ap_config.h:1096,
from os.c:21:
/usr/include/signal.h:111: error: parse error before "siginfo_t"
/usr/include/signal.h:113: error: parse error before "siginfo_t"
*** Error code 1
make: Fatal error: Command failed for target `os.o'
Current working directory /web-download/apache_1.3.33/src/os/unix
*** Error code 1
The following command caused the error:
for i in regex os/unix ap main lib modules; do \
echo "===> src/$i"; \
case ".Solaris 2100" in \
.OS390 | .TPF) ( cd $i && make SDP='src/' OPTIM='') || exit 1;; \
*) ( cd $i && make SDP='src/' CC='gcc' AUX_CFLAGS=' -DSOLARIS2=2100 -DUSE_HSREGEX -DUSE_EXPAT -I./lib/expat-lite -DNO_DL_NEEDED ' RANLIB='ranlib' OPTIM='') || exit 1;; \
esac; \
echo "<=== src/$i"; \
done
make: Fatal error: Command failed for target `subdirs'
Current working directory /web-download/apache_1.3.33/src
*** Error code 1
The following command caused the error:
case "xi86pc-sun-solaris2.2100" in \
x*390*) C89STEPS="0xffffffff"; export C89STEPS;; \
esac; \
cd ./src; make SDP=src/ all
make: Fatal error: Command failed for target `build-std'
Current working directory /web-download/apache_1.3.33
*** Error code 1
The following command caused the error:
make -f ./Makefile root= build-std
make: Fatal error: Command failed for target `build'
I am newbie with Solaris and gcc so I have no so much idea what is missing there.
Thanks,
Juan

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.

SUNWspro iostream error while compiling with SunStudio 10

We are getting the following error when we try to compile the C++ code using SunStudio 10 on Sun Solaris Sparc server.
We made couple of changes in the source code 1) whereever we have stream.h we replaced it with iostream.h and 2) include fstream.h whereever required.
Can anyone tell us where did it go wrong.
+ /opt/SUNWspro/bin/CC -g -O -DHAWK -mt -lclntsh -lsocket -lnsl -I/export/home/StandardComponents/SC/include -I../../mylib -I../../include -I/opt/SUNWspro/prod/include/CC/Cstd -I. -I- -D_TRACE_ -c collectDborMtoInfo.c
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: Use ";" to terminate declarations.
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: A declaration was expected instead of "'\n'".
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: Use ";" to terminate declarations.
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: A declaration was expected instead of "'\n'".
4 Error(s) detected.

Remove the -I directive that points into the compiler installation. You should not have have -I or -L options that point into the compiler installation area, into /usr/include, or into /usr/lib. The CC compiler driver knows where to find system headers and libraries, and in what order to search the directories. If you force a different search order, you can break something.
If removing -I/opt/SUNWspro/prod/include/CC/Cstd does not fix the problem, compiling with -P or -E will show you the preprocessor output, and looking at the lines with the errors will usually show the source of the problem quickly.
BTW, you should be aware that the ".h" form of the C++ headers, like <iostream.h> and <fstream.h>, is not standard. Using them is not portable, because not all C++ implementations provide them, and those that do often have different content.

Building Net-SNMP with gcc and Solaris 10's Forte-built Perl

The 5.0.9 Net-SNMP that come with Solaris SPARC is too old for our users. Building the latest version appears to be basically impossible and I'm just about to bail and just build yet another version of Perl for Solaris 10 so it will work. But on the chance that someone has done this:
I am trying to build Net-SNMP 5.4.1.2 with the Sunfreeware gcc. The configure script seems to ignore the --disable-perl-cc-checks flag:
./configure with-perl-modules disable-perl-cc-checks
configure: error: This build is using a GNU C compiler (gcc) while Perl has been compiled with a non-GNU (or non-working) compiler (cc). This likely won't work for building with Perl support. Either specify a different compiler (--with-cc=PATH), disable this check (--disable-perl-cc-checks) or build without Perl (--without-perl-modules).
Has anyone successfully done this? I was hoping to get a successful configure run, then build the binaries, and then further tweak the perl makefiles with "GCC=/usr/perl5/5.8.4/bin/perlgcc" or something.

configure: error: This build is using a GNU C compiler (gcc) while Perl has been compiled with a non-GNU (or non-working) compiler (cc). This likely won't work for building with Perl support. Either specify a different compiler (--with-cc=PATH), disable this check (--disable-perl-cc-checks) or build without Perl (--without-perl-modules).The perl supplied by Sun should be compiled with Sun Studio and the error mentioned above seems to reflect this.
So, either build perl first with sunfreeware's gcc and then move on to net-snmp or install and use Sun Studio instead of gcc so perl is happy.
alan

Bad performance of PARI when compiling with GCC for SPARC 4.2.0

Hi,
I've compiled pari (2.3.3) with gcc 4.2.0 and with an old gcc 3.3.2 on a Sun Fire V240 and Solaris 10.
The performance of pari compiled with gcc 4.2.0 is terrible. I've tried it with '-O3 -fast' and without this flags with the same result.
First compiled with gcc 3.3.2 without any special CFLAGS and run make bench:
* Testing objets for gp-sta..TIME=4 for gp-dyn..TIME=4
* Testing analyz for gp-sta..TIME=82 for gp-dyn..TIME=80
* Testing number for gp-sta..TIME=63 for gp-dyn..TIME=62
* Testing polyser for gp-sta..TIME=19 for gp-dyn..TIME=19
* Testing linear for gp-sta..TIME=30 for gp-dyn..TIME=29
* Testing elliptic for gp-sta..TIME=50 for gp-dyn..TIME=51
* Testing sumiter for gp-sta..TIME=45 for gp-dyn..TIME=47
* Testing graph for gp-sta..TIME=25 for gp-dyn..TIME=25
* Testing program for gp-sta..TIME=94 for gp-dyn..TIME=94
* Testing trans for gp-sta..TIME=228 for gp-dyn..TIME=225
* Testing nfields for gp-sta..TIME=434 for gp-dyn..TIME=433
+++ Total bench for gp-sta is 726
+++ Total bench for gp-dyn is 722
Then compiled with gcc 4.2.0 again without any special flags and run make bench:
* Testing objets for gp-sta..TIME=4 for gp-dyn..TIME=4
* Testing analyz for gp-sta..TIME=82 for gp-dyn..TIME=83
* Testing number for gp-sta..TIME=62 for gp-dyn..TIME=65
* Testing polyser for gp-sta..TIME=19 for gp-dyn..TIME=19
* Testing linear for gp-sta..BUG [1686975] for gp-dyn..BUG [1608146]
* Testing elliptic for gp-sta..TIME=50 for gp-dyn..TIME=52
* Testing sumiter for gp-sta..TIME=51 for gp-dyn..TIME=50
* Testing graph for gp-sta..TIME=28 for gp-dyn..TIME=28
* Testing program for gp-sta..TIME=98 for gp-dyn..TIME=97
* Testing trans for gp-sta..BUG [613000] for gp-dyn..BUG [606558]
* Testing nfields for gp-sta..BUG [3648091] for gp-dyn..BUG [3716170]
+++ [BUG] Total bench for gp-sta is 3029987
+++ [BUG] Total bench for gp-dyn is 2958336
Do anybody know this problem or can tell me what the problem could be?
Thanks!!
Rainer W.

Here are the compiler options I used to compile it with gcc4.
C compiler is /usr/local/gcc4/gcc/bin/gcc -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer
Executable linker is /usr/local/gcc4/gcc/bin/gcc -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer
Dynamic Lib linker is /usr/local/gcc4/gcc/bin/gcc -shared -mimpure-text $(CFLAGS) $(DLCFLAGS) -Wl,-G,-h,$(LIBPARI_SONAME)
If I use the -fast option I get the same result may be a little bit worse.
Here are some compilation lines:
Making gp in Osolaris-sparcv9
make[2]: Entering directory `/no_backup/pari/pari-2.3.3/Osolaris-sparcv9'
File ../src/funclist not changed.
../config/genkernel ../src/kernel/sparcv8_micro/asm0-common.h ../src/kernel/sparcv8_micro/asm0.h > parilvl0.h
cat ../src/kernel/none/tune.h ../src/kernel/none/int.h ../src/kernel/none/level1.h > parilvl1.h
cat parilvl0.h parilvl1.h > pariinl.h
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -I../src/language -I/usr/local/include -o gp.o ../src/gp/gp.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -I../src/graph -o gp_init.o ../src/gp/gp_init.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -I../src/language -I/usr/local/include -o gp_rl.o ../src/gp/gp_rl.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -DDL_DFLT_NAME=NULL -o highlvl.o ../src/gp/highlvl.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o whatnow.o ../src/gp/whatnow.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -I/usr/openwin/include -o plotX.o ../src/graph/plotX.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o anal.o ../src/language/anal.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o compat.o ../src/language/compat.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o default.o ../src/language/default.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o errmsg.o ../src/language/errmsg.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o es.o ../src/language/es.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o init.o ../src/language/init.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o intnum.o ../src/language/intnum.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o members.o ../src/language/members.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o sumiter.o ../src/language/sumiter.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o aprcl.o ../src/modules/aprcl.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o elldata.o ../src/modules/elldata.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o elliptic.o ../src/modules/elliptic.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o galois.o ../src/modules/galois.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o groupid.o ../src/modules/groupid.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o kummer.o ../src/modules/kummer.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o mpqs.o ../src/modules/mpqs.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o nffactor.o ../src/modules/nffactor.c
/usr/local/gcc4/gcc/bin/gcc -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer -I. -I../src/headers -o part.o ../src/modules/part.c

Unable to compile using rmic

Hello all
I have successfully compiled files using javac. The path is set, so I just need to open a command prompt and simply type javac AddServerImpl.java and it compiles with out errors. I do not have to specify any path at all.
But when I try to compile using rmic, that is where I have the problem. It simply says "error: Class AddServerImpl$.java not found. 1 error."
I simply don't understand what the problem is. If the path can work with javac <name>, why can't it work with rmic.
I have even tried copying the java files, to where the rmic file is present and then tried running rmic AddServerImpl. But it still does not work. I have even included the following line under the environment variables "setclass path = %classpath%c:\rmiproject\"
A bit desparate of ideas.
Thankyou

If the path can work with javac <name>, why can't it work with rmic.Because javac takes a path to a filename. rmic takes a package-qualified classname. Different strokes.

An oci program compiled with oracle 9 run in a machine has oracle client 10

Hello,
I would like to know if an OCI program compiled with Oracle 9 client libraries can communicate with Oracle 9 and Oracle 8 database servers by using the oracle client 10 on Solaris? Is there any known problem of this combination?
Many thanks,

It largely depends on what your program does. If the program uses features which are only available in Oracle 9i and not in Oracle 8i then you are likely to get some errors. For the latter case, ie, compiling the program with Oracle 9 libs and runnig with Oracle 10 libs, talking to 9i server should be fine while 8i server may give you some unexpected behaviour.
Thanks,
Sumit

IdcApache2Auth.so Compiled With Large File Support

Hi, I'm installing UCM 10g on solaris 64 Bit plattform and Apache 2.0.63 , everything went fine until I update configuration in the httpd.conf file. When I query server status it seems to be ok:
+./idcserver_query+
Success checking Content Server idc status. Status: Running
but in the apache error_log and I found the next error description:
Content Server Apache filter detected a bad request_rec structure. This is possibly a problem with LFS (large file support). Bad request_rec: uri=NULL;
Sizing information:
sizeof(*r): 392
+[int]sizeof(r->chunked): 4+
+[apr_off_t]sizeof(r->clength): 4+
+[unsigned]sizeof(r->expecting_100): 4+
If the above size for r->clength is equal to 4, then this module
was compiled without LFS, which is the default on Apache 1.3 and 2.0.
Most likely, Apache was compiled with LFS, this has been seen with some
stock builds of Apache. Please contact Support to obtain an alternate
build of this module.
When I search at My Oracle Support for suggestions about how to solve my problem I found a thread which basically says that Oracle ECM support team could give me a copy IdcApache2Auth.so compiled with LFS.
What do you suggest me?
Should I ask for ECM support team help? (If yes please tell me How can I do it)
or should I update the apache web server to version 2.2 and use IdcApache22Auth.so wich is compiled with LFS?
Thanks in advance, I hope you can help me.

Hi ,
Easiest approach would be to use Apache2.2 and the corresponding IdcApache22Auth.so file .
Thanks
Srinath

Using GDB to debug a code compiled with Sun cc

When using gdb to debug C code compiled with Sun's cc, the step-into doesn't work, i can only "step into" a function if i put a breakpoint on it. Also, sometimes if i set a breakpoint on a function name, like "break foo", gdb indeed breaks when foo is reached, but without showing the source code (this i could not reproduce with a small demo program).
I am using Sun Studio 12 on a SunOS 5.10 sun4u sparc machine.
My demo program is:
#include <stdio.h>
#include <strings.h>
void func1(str)
char str;
printf("This is the first line\n");
printf("STR: %s\n",str);
int main()
char str[10];
strcpy(str,"lalalal");
printf("Calling func1\n");
func1(str);
printf("Returned from func1\n");
The compilation command i run is:
cc -c -g step_into.c -o step_into.o
cc -g -o step_into step_into.o
When running the program with gdb, the "step" command does not step into func1, but runs it like "next".
I know there's the dbx debugger, but if there's a way to fix this with gdb - it is much preferable for us. Switching to dbx is not really feasible for us.
Regards,
Yael

Hello Yael,
I tried your example on my laptop (OpenSolaris x86/x64) with Sun Studio 12 update 1
and GDB 6.3.50 - it works properly:
$ gdb dist/Debug/SunStudio-Solaris-x86/forum_c_20091230
GNU gdb 6.3.50_2004-11-23-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.11"...
(gdb) break main
Breakpoint 1 at 0x8050a87: file src/args.c, line 15.
(gdb) run
Starting program: /export/home/nikm/SunStudioProjects/Forum_C_20091230/dist/Debug/SunStudio-Solaris-x86/forum_c_20091230
Breakpoint 1, main () at src/args.c:15
15         printf("Calling func1\n");
Current language: auto; currently minimal
(gdb) next
Calling func1
16         func1(str);
(gdb) step
This is the first line
func1 (str=0x80477ba "lalalal") at src/args.c:7
7         printf("STR: %s\n",str);
(gdb) Could you please download and try Sun Studio 12 update 1?
It is available for free. Here is the web page:
http://developers.sun.com/sunstudio/
BTW, which GDB version do you use?
I'll try it on a sparc system and let you know.
Thanks.
Nik
P.S.: there is a typo in the source code:
void func1(str)
*char *str;I think it should be:
void func1(char *str)Probably a copy-paste problem.
Please use "CODE" mode when you copy-paste source lines (selected text, press 'CODE' button).

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.

Can't find library when compiled with debugging

Hi all,
Compiling this code segment cannot find a library when using -g
bash-3.2$ cat tester.cc
#include <iostream>
#include <string>
using namespace std ;
static void
myRoutine()
string str= "this is in routine" ;
string str3 ;
str3 = str.substr(11,7) ;
if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
cout << "this is str3 - " << str3 << endl ;
int main(int argc, char **argv)
string str = "this is a test" ;
string str1, str2 ;
str1 = str.substr(0,4) ;
str2 = str.substr(10,4) ;
cout << "this is str1 - " << str1 << endl ;
cout << "this is str2 - " << str2 << endl ;
myRoutine() ;
return 0 ;
bash-3.2$ CC -g -o tester tester.cc
bash-3.2$ ldd tester
     libCstd.so.1 =>     /usr/lib/libCstd.so.1
     libCstd.so.1 (SUNW_1.4.2) =>     (version not found)
     libCrun.so.1 =>     /usr/lib/libCrun.so.1
     libm.so.2 =>     /usr/lib/libm.so.2
     libc.so.1 =>     /usr/lib/libc.so.1
If I comment out:
if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
bash-3.2$ cat tester.cc
#include <iostream>
#include <string>
using namespace std ;
static void
myRoutine()
string str= "this is in routine" ;
string str3 ;
str3 = str.substr(11,7) ;
// if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
cout << "this is str3 - " << str3 << endl ;
int main(int argc, char **argv)
string str = "this is a test" ;
string str1, str2 ;
str1 = str.substr(0,4) ;
str2 = str.substr(10,4) ;
cout << "this is str1 - " << str1 << endl ;
cout << "this is str2 - " << str2 << endl ;
myRoutine() ;
return 0 ;
bash-3.2$ CC -g -o tester tester.cc
bash-3.2$ ldd tester
     libCstd.so.1 =>     /usr/lib/libCstd.so.1
     libCrun.so.1 =>     /usr/lib/libCrun.so.1
     libm.so.2 =>     /usr/lib/libm.so.2
     libc.so.1 =>     /usr/lib/libc.so.1
Or if I remove -g:
bash-3.2$ cat tester.cc
#include <iostream>
#include <string>
using namespace std ;
static void
myRoutine()
string str= "this is in routine" ;
string str3 ;
str3 = str.substr(11,7) ;
if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
cout << "this is str3 - " << str3 << endl ;
int main(int argc, char **argv)
string str = "this is a test" ;
string str1, str2 ;
str1 = str.substr(0,4) ;
str2 = str.substr(10,4) ;
cout << "this is str1 - " << str1 << endl ;
cout << "this is str2 - " << str2 << endl ;
myRoutine() ;
return 0 ;
bash-3.2$ CC -o tester tester.cc
bash-3.2$ ldd tester
     libCstd.so.1 =>     /usr/lib/libCstd.so.1
     libCrun.so.1 =>     /usr/lib/libCrun.so.1
     libm.so.2 =>     /usr/lib/libm.so.2
     libc.so.1 =>     /usr/lib/libc.so.1
then I can run successfully
Any thoughts or hints?
bash-3.2$ CC -V
CC: Sun Ceres C++ 5.10 SunOS_i386 2008/07/10
Usage: CC [ options ] files. Use 'CC -flags' for details
bash-3.2$ uname -a
SunOS alpha 5.11 snv_86 i86pc i386 i86pc
Thanks,
Jim

Ack! Please ignore my earlier posting. I did not play close enough attention to details in your post. I apologize for the confusion. Let me start over:
The Studio Express release you have contains a newer version of the C++ runtime library libCstd.so.1 than is available yet in Solaris patches. We bump the internal version number when we add new interfaces. The internal version number of the Studio Express library is SUNW_1.3.2. The version of the latest release Solaris patch is SUNW_1.3.1.
Some new string class operator functions are in version SUNW_1.3.2. I think these are also defined as inline functions in the compiler headers. When you compile with -g, inlining is disabled, and you create a dependency on library version SUNW_1.3.2. (Compiling with -g0 allows function inlining, and might resolve your problem, but read on.)
We have not released a libCstd.so.1 with internal version SUNW_1.4.2, so I don't understand how that version number could appear in an error message. Did you really see that version, or is it a transcription error? For now, let's assume it is a transcription error.
When you compile and link with CC, the program gets a runpath pointing into the compiler installation area. At program run time, the loader looks for libraries in directories listed in the runpath, with /lib and /usr/lib as last resort. The "ldd" command reports what the runtime loader will do regarding dependent libraries.
If the compiler is installed in /opt, a 32-bit program gets a runpath that includes /opt/SUNWspro/lib. In that directory in Sun Studio Express is a symbolic link that points to ../prod/usr/lib/libCstd.so.1, the library with version SUNW_1.3.2.
If you try this:
% /opt/SUNWspro/bin/CC hello.cc
% ldd a.out
you should see, among other things,
libCrun.so.1 => /opt/SUNWspro/lib/libCstd.so.1
(Depending on the OS version, you might see
libCrun.so.1 => /opt/SUNWspro/prod/usr/lib/libCstd.so.1 instead.)
But if ldd can't resolve the library, you probably have a corrupted Sun Studio Express installation. In that case, uninstall it, and reinstall from a fresh download.
If you run the program on a different computer where Sun Studio Express is not installed, the loader won't be able to find the right library version, and you will get "not found" results. I addressed this issue in another thread:
http://forums.sun.com/thread.jspa?threadID=5340163

Problems with rmic v1.1

Hi,
I have to use the JDK1.1.8, if I compiled the interface and the implementation of the interface everything was fine.
But when I try to create my stub and skeleton with rmic, I get this message:
rmic prog
error: File ./prog.class does not contain type prog as expected, but type my.test.prog.prog. Please remove the
file, or make sure it appears in the correct subdirectory of the class path.
error: Class prog not found.
java.lang.IllegalArgumentException: Argument # > Arg length
at java.text.MessageFormat.format(Compiled Code)
at java.text.MessageFormat.format(MessageFormat.java)
at java.text.MessageFormat.format(MessageFormat.java)
at sun.rmi.rmic.Main.getText(Main.java:489)
at sun.rmi.rmic.Main.getText(Main.java:464)
at sun.rmi.rmic.Main.doCompile(Compiled Code)
at sun.rmi.rmic.Main.compile(Main.java:107)
at sun.rmi.rmic.Main.main(Main.java:422)
----

By convention, most java tools expect to find a "packaged" class in a directory hierarchy that relects the packaging. In other words, a class defined like
com.myco.myapp.ImportantApplication.class
will be placed under a base directory, in a subordinate directory thus:
/basedir/com/myco/myapp
In turn, java tools will find this class if you suppli classpaths such as
java -classpath basedir/
Note the trailng slash. This tells java that this is a directory name.
rmic works the same way.

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.

Compiling with rmic on Solaris

Similar Messages

Maybe you are looking for