Re: [OpenIndiana-discuss] use cases of Sun Studio-compiled C++ libraries on OI
On 11/28/14 06:25 PM, Richard L. Hamilton wrote: If it’s C++, the name mangling is different; look up the options for the Sun > and GNU versions of nm respectively, use each version of nm with its > demangling option, and whichever has sensible output corresponds to the > compiler used. Even with Studio, there are now at least 7 different binary incompatible options for building C++ code: -compat=4 - pre-C++98 SunPro 4.x compiler ABI (only in Studio 12.2 & older) -compat=5 (aka -std=sun03) - C++03 Sun compiler ABI -compat=g (aka -std=c++03) - C++03 with g++ extensions/ABI -std=c++11 - C++11 features & g++ library/ABI (only in Studio 12.4 & later) -library=Cstd - C++03 with Studio libCstd library -library=stdcxx4 - C++03 with Apache stdcxx library -library=stlport4 - C++03 with STLport library As you'll see in the CC man page, all C++ code in a program must use the same -compat, -std, & -library flags - you can't use a library built with different ones than the program itself uses. -alan- "A strange game. The only winning move is not to play. How about a nice game of chess?" ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] use cases of Sun Studio-compiled C++ libraries on OI
Wouldn't this break the binary compatibility guarantee that Solaris had been traditionally marketed on? I'm no kernel engineer, so I wouldn't know. " 'With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' Those words were uttered by Judge Aaron Satie as wisdom and warning... The first time any man's freedom is trodden on, we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron Satie, Star Trek: TNG episode "The Drumhead" - Alex Smith - Huntsville, Alabama metropolitan area USA On Sun, Dec 7, 2014 at 12:51 PM, Alan Coopersmith < alan.coopersm...@oracle.com> wrote: > On 11/28/14 06:25 PM, Richard L. Hamilton wrote: > >> If it’s C++, the name mangling is different; look up the options for the >> Sun >> > > and GNU versions of nm respectively, use each version of nm with its > > demangling option, and whichever has sensible output corresponds to the > > compiler used. > > Even with Studio, there are now at least 7 different binary incompatible > options for building C++ code: > > -compat=4 - pre-C++98 SunPro 4.x compiler ABI (only in Studio 12.2 & > older) > -compat=5 (aka -std=sun03) - C++03 Sun compiler ABI > -compat=g (aka -std=c++03) - C++03 with g++ extensions/ABI > -std=c++11 - C++11 features & g++ library/ABI (only in Studio 12.4 & > later) > -library=Cstd - C++03 with Studio libCstd library > -library=stdcxx4 - C++03 with Apache stdcxx library > -library=stlport4 - C++03 with STLport library > > As you'll see in the CC man page, all C++ code in a program must use the > same -compat, -std, & -library flags - you can't use a library built with > different ones than the program itself uses. > > -alan- > > "A strange game. The only winning move is not to play. > How about a nice game of chess?" > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] use cases of Sun Studio-compiled C++ libraries on OI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/7/2014 5:26 PM, Alex Smith (K4RNT) wrote: > Wouldn't this break the binary compatibility guarantee that Solaris > had been traditionally marketed on? > > I'm no kernel engineer, so I wouldn't know. No. The guarantee has always been that *IF* your application complies strictly with the ABI *THEN* it won't be broken on future releases without adequate notice. This doesn't in any way guarantee that you can produce such an application in the first place by linking together arbitrary (and incompatible) objects. Producing an ABI compliant application can be a difficult job, particularly if you choose to work in a hostile environment such as C++. - -- James Carlson 42.703N 71.076W -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iEYEARECAAYFAlSE2agACgkQ6TIHA1NkzvAeTgCbBlnMVHo6L9gduQQLqfXFgepK wpcAnRH8T957+0iiDjruaPDg2nZvnMRf =24p+ -END PGP SIGNATURE- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] use cases of Sun Studio-compiled C++ libraries on OI
On 12/ 7/14 02:50 PM, James Carlson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/7/2014 5:26 PM, Alex Smith (K4RNT) wrote: Wouldn't this break the binary compatibility guarantee that Solaris had been traditionally marketed on? I'm no kernel engineer, so I wouldn't know. No. The guarantee has always been that *IF* your application complies strictly with the ABI *THEN* it won't be broken on future releases without adequate notice. This doesn't in any way guarantee that you can produce such an application in the first place by linking together arbitrary (and incompatible) objects. Producing an ABI compliant application can be a difficult job, particularly if you choose to work in a hostile environment such as C++. Right - the binary compatibility guaranteed is with previous versions of the OS, not arbitrary compilation options. Similarly you can't link 32-bit & 64-bit C code together, nor SPARC & i386 - they're all binary incompatible with each other. As to whether OpenIndiana cares about Sun's marketing programs is a completely different question - maintaining binary compatibility can be a lot of work, and OI's clearly not overflowing with excess developers with oodles of spare time to offer. -alan- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] openindiana-discuss Digest, Vol 53, Issue 2
On Wednesday, December 3, 2014, wrote: > Send openindiana-discuss mailing list submissions to > openindiana-discuss@openindiana.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://openindiana.org/mailman/listinfo/openindiana-discuss > or, via email, send a message with subject or body 'help' to > openindiana-discuss-requ...@openindiana.org > > You can reach the person managing the list at > openindiana-discuss-ow...@openindiana.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openindiana-discuss digest..." > > > Today's Topics: > >1. Re: /hipster-2014.1 strange behave (update picks up 2014.1.2 > but repository has 2014.1.3 version available) (Alexander Pyhalov) >2. Re: /hipster-2014.1 strange behave (update picks up 2014.1.2 > but repository has 2014.1.3 version available) > (Predrag Zecevic [Unix Systems Administrator]) >3. [HEADSUP] Sun Studio-compiled C++ libraries are no longer > supported (Alexander Pyhalov) >4. Re: [oi-dev] [HEADSUP] Sun Studio-compiled C++ libraries are > no longer supported (Udo Grabowski (IMK)) >5. Re: [oi-dev] [HEADSUP] Sun Studio-compiled C++ libraries are > no longer supported (Udo Grabowski (IMK)) >6. Re: [oi-dev] [HEADSUP] Sun Studio-compiled C++ libraries are > no longer supported (Alexander Pyhalov) > > > -- > > Message: 1 > Date: Tue, 02 Dec 2014 16:35:53 +0300 > From: Alexander Pyhalov > > To: predrag.zece...@2e-systems.com > Cc: Discussion list for OpenIndiana > > > Subject: Re: [OpenIndiana-discuss] /hipster-2014.1 strange behave > (update picks up 2014.1.2 but repository has 2014.1.3 version > available) > Message-ID: <547dc039.1010...@rsu.ru > > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 12/02/2014 11:35, Predrag Zecevic [Unix Systems Administrator] wrote: > > Hi Alexander, > > > > what about incorporations? > > > > > So, my question is: do I need to (may I) remove consolidation from > > "0.5.11,5.11-0.151.1.8" time (all of them)? > > No, if they are not explicitly marked obsolete. In this case IPS would > do it for you. > > > -- > Best regards, > Alexander Pyhalov, > system administrator of Southern Federal University IT department > > > > -- > > Message: 2 > Date: Tue, 02 Dec 2014 14:41:26 +0100 > From: "Predrag Zecevic [Unix Systems Administrator]" > > > To: Alexander Pyhalov > > Cc: Discussion list for OpenIndiana > > > Subject: Re: [OpenIndiana-discuss] /hipster-2014.1 strange behave > (update picks up 2014.1.2 but repository has 2014.1.3 version > available) > Message-ID: <547dc186.5050...@2e-systems.com > > Content-Type: text/plain; charset=utf-8; format=flowed > > > On 12/ 2/14 02:35 PM, Alexander Pyhalov wrote: > > On 12/02/2014 11:35, Predrag Zecevic [Unix Systems Administrator] wrote: > >> Hi Alexander, > >> > >> what about incorporations? > >> > > > >> So, my question is: do I need to (may I) remove consolidation from > >> "0.5.11,5.11-0.151.1.8" time (all of them)? > > > > No, if they are not explicitly marked obsolete. In this case IPS would > do it for you. > > > > > Many thanks for nice explanation and your time... > Regards. > > -- > Predrag Ze?evi?, Technical Support Analyst, 2e Systems GmbH > > Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 > Mobile:+49 174 3109 288, Skype: predrag.zecevic > E-mail:predrag.zece...@2e-systems.com > > Headquarter: 2e Systems GmbH, K?nigsteiner Str. 87, >65812 Bad Soden am Taunus, Germany > Company registration: Amtsgericht K?nigstein (Germany), HRB 7303 > Managing director:Phil Douglas > > http://www.2e-systems.com/ - Making your business fly! > > [***]===--- > To iterate is human, to recurse, divine. -- Robert Heller > > > > -- > > Message: 3 > Date: Tue, 02 Dec 2014 20:17:01 +0300 > From: Alexander Pyhalov > > To: OpenIndiana Developer mailing list >, > Discussion list for OpenIndiana < > openindiana-discuss@openindiana.org > > Subject: [OpenIndiana-discuss] [HEADSUP] Sun Studio-compiled C++ > libraries are no longer supported > Message-ID: <547df40d.7050...@rsu.ru > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello. > > This post is to inform you that OpenIndiana Hipster will cease > supporting Sun Studio-compiled software. Note, this move doesn't affect > OpenIndiana /dev. > > We currently support following C++ libraries compiled with Studio: > database/postgres/library/c++/libpqxx > developer/icu > library/c++/glibmm > library/c++/libxml++ > library/c++/net6 > library/c++/obby > library/c++/sigcpp > library/c++/stdcxx > library/desktop/c++/cairomm > library/desktop/c++/gtkmm > library/desktop/c++/pangomm > l
