Can a program which is built by Workshop 4.2 use a dynamic library build by Workshop 6.1?

Can a program which is built by Workshop 4.2 use a dynamic library build by Workshop 6.1?

Post by Dennis Ka » Sun, 28 Apr 2002 06:53:38



I wrote a very small program built by workshop4.2 which can use a
small dynamic library (self-contained, use -zdefs to link). But when i
build a more complex dynamic library, it wouldn't work for me.

Can workshop4.2 application use workshop6.1 libraries?

Dennis.

 
 
 

Can a program which is built by Workshop 4.2 use a dynamic library build by Workshop 6.1?

Post by Alan Coopersmi » Mon, 29 Apr 2002 04:31:48



|I wrote a very small program built by workshop4.2 which can use a
|small dynamic library (self-contained, use -zdefs to link). But when i
|build a more complex dynamic library, it wouldn't work for me.
|
|Can workshop4.2 application use workshop6.1 libraries?

Depends on the language.  It should work for C just fine, otherwise you
wouldn't be able to run old apps on new Solaris releases compiled with
newer Solaris compilers.

If you're using C++, you probably need to compile with the -compat=4
flag on 6.1.

If you want more help, post more details, including exact error
messages/failure states, not just "it wouldn't work".

--
________________________________________________________________________


  Working for, but definitely not speaking for, Sun Microsystems, Inc.

 
 
 

1. compiler warnings going from WorkShop 4.2 to WorkShop 6 update 1

We are in the process of re-compiling our programs using WorkShop 6
update 1 and I keep getting a lot of annoying warning messages.  One
is:

"String literal converted to char* in initialization"

and others are complaining about function pointers as arguments to
functions, like for signal, thr_create, and atexit.  A typical warning
states:

Warning (Anachronism): Formal argument 2 or type extern "C"
void(*)(int) in call to std::signal(int, extern "C" void (*)(int)) is
being passed void(*)(int).

The calls are being made in a C++ program.

Is there anyway to correct this warnings?  I used the "-w" option for
the compiler to silence the string literal warnings, but I am afraid
it is silencing other warnings as well.  I am assuming that the
"extern C" warning is coming up because it is a C++ program.  I know
they are just warnings, but I like to have clean compiles.  Any help
would be greatly appreciated.

       -Diana Coppenbarger
       Lead Programmer/Analyst
       University of Rochester
          Laboratory for Laser Energetics

2. Using onboard IDE and PCI IDE at the same time

3. Building libraries with Workshop 5

4. Which ISDN apater for Linux 1.2.13ELF ??

5. MicroFocus Cobol 4.1 compiler /w SUN Workshop Pro C 4.2 library question ?

6. Which IDE with Solaris-Intel

7. Sun Visual Workshop C++ for building Motif and MFC based UI's?

8. Second network card

9. How to debug using workshop when my program uses Xerces parser

10. WORKSHOP: 9th DARESBURY MACHINE EVALUATION WORKSHOP

11. Sell me your C++ Workshop or Visual Workshop

12. Building a library that can be used by C and C++ programs

13. Sun C++ Workshop 4.2, bool and mutable