[aur-general] [google-talkplugin] How to build an older version of openssl

[Denis A. Altoé Falqueto]

On Wed, Oct 27, 2010 at 6:42 AM, Ionuț Bîru <ibiru at archlinux.org> wrote:
> On 10/27/2010 04:47 AM, Denis A. Altoé Falqueto wrote:
>>
>> Hello, guys.
>>
>> Google Talk Plugin for GMail is not working anymore for me (and
>> others...) because it relies on libssl.so.0.9.8. But for my surprise,
>> the binary GoogletalkPlugin is a 32 bits executable, even for the 64
>> bits package. It comes right after the original deb package, provided
>> by Google.
>>
>> To make things short, I tried to "downgrade" the lib32-openssl
>> PKGBUILD to version 0,9,8n. It compiles fine, but the resulting
>> libraries (libcrypto.so.0.9.8 and libssl.so.0.9,8) are ELF64, when
>> they should be ELF32. You can view the PKGBUILD in
>> http://pastebin.com/04xsippr
>>
>> So, should I need a 32 bits chroot for that? Shouldn't the multilib
>> compiler be enough?
>>
>
> sorry but if you think that downgrading lib32-openssl will solve this, you
> are wrong. just get the PKGBUILD from AUR and it would have the right
> dependencies for it.
>
> https://aur.archlinux.org/packages.php?ID=40056
>
> as you see it has libpng12, openssl-compatibility as dependencies.

Yes, but they are not enough. If you check with readelf -h
/opt/google/talkplugin/GoogleTalkPlugin, you'll see that it is a ELF32
binary, and it depends on libssl.so.0.9.8. I could use the package on
AUR, but it is not compiled with the the new multilib compiler. I
would like to do it in the new right way.

In fact, after searching the forums, I found that calling linux32
make, instead of just make, in the PKGBUILD, generates a ELF32
library. It is working fine in my laptop, but I'll investigate it
further.

Any comments are welcome.

-- 
A: Because it obfuscates the reading.
Q: Why is top posting so bad?

-------------------------------------------
Denis A. Altoe Falqueto
Linux user #524555
-------------------------------------------