[oi-dev] problem with firefox in hipster
ken mays
maybird1776 at yahoo.com
Fri Jul 19 14:48:50 UTC 2013
Hello,
Yikes!!
Erol - Can you include the older zlib 1.2.3 libraries (32/64-bit ones) in the newer 'library/zlib at 1.2.8,5.11-0.151.1.8.1:20130715T155558Z' package in /hipster for backward compatibility with legacy apps?
~ Ken
________________________________
From: Erol Zavidic <erolms at gmail.com>
To: OpenIndiana Developer mailing list <oi-dev at openindiana.org>
Cc: OpenIndiana Developer mailing list <oi-dev at openindiana.org>
Sent: Friday, July 19, 2013 8:35 AM
Subject: Re: [oi-dev] problem with firefox in hipster
Alex,
I bumped zlib this week so I have a bit of history here. All symbols from 1.2.3 versions have SUNW_1.2 label and newer are labeled with 1.3.
The 64bit calls were introduced after 1.2.3 and now carry 1.3 label, have a look at mapfile in zlib directory.
Cheers,
Erol
Am 19.07.2013 um 12:53 schrieb Alexander Pyhalov <alp at rsu.ru>:
> On 07/19/2013 14:14, Nikola M. wrote:
>> On 07/19/13 12:06 PM, Alexander Pyhalov wrote:
>>> On 07/19/2013 13:57, Jim Klimov wrote:
>>>> On 2013-07-19 11:51, Udo Grabowski (IMK) wrote:
>>>>
>>>>>>> Maybe indeed a C++ incompatibility ?
>>>>
>>>>> Welcome to the world of binary incompatiblitly, now the last
>>>>> fortress has finally been conquered.....
>>>>
>>>> Which moves me to think: would this example mean that legacy
>>>> applications built for Solaris 10 and older, running now on
>>>> obsolete deployments which might be targeted for upgrade to
>>>> OI, would likely not run on newer hipster-based GCC-compiled
>>>> OS releases?
>
>> Please don't try in Hipster, it is rolling release, hot even /dev.
>> Try latest OI /dev, saying 151a7 , that you can upgrade from opensolaris
>> 134, anyway.
>
> There is no longer opensolaris there. Migrated to FreeBSD in 2011 and rarely regret about this ;)
>
> About current problem - Andrzej identified the reason - zlib update. Need advices on fixing this.
>
> If we roll back zlib update, we need some ugly hack to update existing installations.
> The other idea is to identify incompatible changes and isolate them with symbol versioning. I have no idea if it is possible and how hard it is.
> --
> Best regards,
> Alexander Pyhalov,
> system administrator of Computer Center of Southern Federal University
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20130719/f1c5d642/attachment-0005.html>
More information about the oi-dev
mailing list