This is a discussion on Older gcc using a library compiled with a different compiler? within the comp.unix.solaris forums, part of the Solaris Operating System category; --> I have an application that has me forced to use gcc 2.95.3 on solaris/ SPARC. I am wondering, is ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have an application that has me forced to use gcc 2.95.3 on solaris/ SPARC. I am wondering, is there any problem with and older gcc like this using a library that was compiled with gcc 3.4? What if I get a version of this library compiled with sun pro? Is it an issue then if I use this old gcc and attempt to call functions in this library? Thanks much, mohan |
| ||||
| Mohan Khurana <mohankhurana@gmail.com> writes: > I have an application that has me forced to use gcc 2.95.3 on solaris/ > SPARC. How can an application force you to do anything? Did it put a gun to your head? Now, if the app fails to compile with newer gcc, and you are too lazy to fix its source so it does, that's another story. > I am wondering, is there any problem with and older gcc like > this using a library that was compiled with gcc 3.4? If the library is "pure C", then it will most likely work. If the library is "C++", it will not. > What if I get a version of this library compiled with sun pro? Exact same deal -- "C" will most likely work, "C++" -- no way. Cheers, -- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email. |