Re: g++-3.0 library support?
Ulrich Eckhardt [EMAIL PROTECTED] cum veritate scripsit: However, what we really need is a more generic naming-scheme like libnameinterface-version-compilernameABI-version.so Or more like: libname-compilernamecompiler-abi-version.so.interface-version Adding compiler version inside the soname would be a possible, and interesting thing to do, but not something to stuff into FHS right now. Adding support for including compiler version/compiler-abi-version in libtool is the first thing to do, and before that, a method for determining compiler version and compiler-abi-version on any compiler. regards, junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: g++-3.0 library support?
On Sunday 07 April 2002 22:26, King Leo (Martin Oberzalek) wrote: Hello, it's not possible linking a C++ library compiled with g++-2.9x to a C++ application compiled with g++-3.0. We all no the reasons... My question is how I should handle this, on debian distributions that are based on gcc-2.9x? I have a C++ library. And I wan't to create debs for g++.2.9x and g++-3.0. Technically this is no problem. I created 4 debs. 1) libfoo = shared g++-2.9x library 2) libfoo-dev = development files (includes, .a, docu) 3) libfoo-gcc3 = shared g++3.0 library 4) libfoo-gcc3-dev = development files (.a only, since include files and docu are the same) the g++-2.9x library files are called libfoo.so for g++-3.0 libfoo-gcc3.so The files of both packages are located in /usr/lib So if I wanna link an programm with the gcc-3.0 version, -lfoo-gcc3 has to be used and for gcc-2.9x, -lfoo. Are there any better ideas? No, not really. One thing that I could imagine would be the dynamic linker auto-picking the lib with the proper ABI. Another usefule feature would be if the autotools could be extended to that extent. However, what we really need is a more generic naming-scheme like libnameinterface-version-compilernameABI-version.so The advantage would be that we would have prepared support for any compiler, there are more than just g++ 2.x and 3.x[1]. Also, to provide some stability for software-developers, I would suppose moving that naming-scheme to the FHS[2]. uli [1]: Yes, I know that some people will not move a finger to provide proper infrastructure for eg Intel's compiler. However, providing a generic framework will enable a smooth upgrade to g++ 3.1 and other distros that are less reluctant to include non-free software will be more motivated to share that scheme. [2]: Is there anyone here who is following their development ? I wouldn't like to crash in there unprepared with such a proposal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: g++-3.0 library support?
Am Son, 2002-04-07 um 21.35 schrieb Matthias Klose: King Leo (Martin Oberzalek) writes: Hello, it's not possible linking a C++ library compiled with g++-2.9x to a C++ application compiled with g++-3.0. We all no the reasons... My question is how I should handle this, on debian distributions that are based on gcc-2.9x? use only gcc-2.95. I have a C++ library. And I wan't to create debs for g++.2.9x and g++-3.0. Technically this is no problem. Are there any better ideas? yes, use only one version. Which package does require this setup? Currently non existing one; But I'll create a package of an application that won't compile with gcc-2.95. Patching the package will be very difficult. The alternative will be packing all required libraries of this package into this package too. Or maybe creating a package bar-shared which contains all required libraries and the package bar will then depend on the shared package. The third possibility is linking these libraries statically. Which method would you suggest? -- Da Gandalfs Kopf jetzt heilig ist, laßt uns einen anderen finden, den zu spalten richtig ist! (Gimli in LOTR) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: g++-3.0 library support?
King Leo (Martin Oberzalek) [EMAIL PROTECTED] cum veritate scripsit: The alternative will be packing all required libraries of this package into this package too. This would be rather painful. Or maybe creating a package bar-shared which contains all required libraries and the package bar will then depend on the shared package. The third possibility is linking these libraries statically. Probably the easiest, and probably the most possible solution to do it right now would be to link it statically, until Debian as a whole decides to start moving towards a gcc-3 transition. regards, junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: g++-3.0 library support?
King Leo (Martin Oberzalek) writes: Hello, it's not possible linking a C++ library compiled with g++-2.9x to a C++ application compiled with g++-3.0. We all no the reasons... My question is how I should handle this, on debian distributions that are based on gcc-2.9x? use only gcc-2.95. I have a C++ library. And I wan't to create debs for g++.2.9x and g++-3.0. Technically this is no problem. I created 4 debs. 1) libfoo = shared g++-2.9x library 2) libfoo-dev = development files (includes, .a, docu) 3) libfoo-gcc3 = shared g++3.0 library 4) libfoo-gcc3-dev = development files (.a only, since include files and docu are the same) the g++-2.9x library files are called libfoo.so for g++-3.0 libfoo-gcc3.so The files of both packages are located in /usr/lib how about compatibility of sonames across distributions? So if I wanna link an programm with the gcc-3.0 version, -lfoo-gcc3 has to be used and for gcc-2.9x, -lfoo. Are there any better ideas? yes, use only one version. Which package does require this setup? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: g++-3.0 library support?
So if I wanna link an programm with the gcc-3.0 version, -lfoo-gcc3 has to be used and for gcc-2.9x, -lfoo. Are there any better ideas? unfortunately not, the ABI is different between the two. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
