pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: pkgsrc/devel/zlib



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 19/09/14 22:25, Joerg Sonnenberger a écrit :
> On Fri, Sep 19, 2014 at 12:38:15PM +0200, Richard PALO wrote:
>> BTW taking distros that don't support ssp in libc hostage
>> without communicating any explicit technical nor administrative
>> reasons seems abusive. Not to mention additionally blocking
>> upstream gcc implementation requirements for -Bdirect on SunOS
>> 64-bit without communicating, as of yet, any viable (tested)
>> alternative.
> 
> This is bullshit. I gave you a suggestion on how to address either 
> properly. libgcc_s should not override the libc unwind, which is
> easily done by adding a few weak attributes in the right places for
> Solaris and/or checking that none of the GNU extensions leak
> through. Similary should the stack protector callbacks be provided
> as weak versions in libgcc(_s) without the crappy separate library.
> I will never understand the GCC mentality of "we rule the world
> with our runtime, except when we don't want to". The amount of
> breakage the misguided versioning in libgcc_s alone has created...
> 
> Joerg
> 
> 

Joerg, bullshit or no, the last I heard from you was:
> -------- Message original -------- Sujet: Re: Fwd: CVS commit:
> pkgsrc/devel Date : Tue, 03 Jun 2014 07:29:23 +0200 De : Richard
> PALO <richard.palo%free.fr@localhost> Organisation : Mas KIRANNE Pour : Joerg
> Sonnenberger <joerg%britannica.bec.de@localhost>
> 
> Le 16/05/14 19:13, Richard PALO a écrit :
>> Le 16/05/14 18:42, Joerg Sonnenberger a écrit :
>>> Sorry for having been a short lately, been busy working on a
>>> project for a customer. I'll try to sort things out at most
>>> early next week.
>>> 
>>> Joerg
>>> 
>> okay.. richard
> Hi Joerg, relancing...  please take the time to help get this
> resolved. cheers, richard
> 
> 
Actually I relanced you once again the 26/6 but did not receive the
courtesy of a even a minimal reply.

This info you provide now is rather scant, so if you can give more
details/sample code I'm more than willing to work on it... (I'm sure
I'm not alone) but telepathy does not work - at all!

The solution already provided does seem to work in a tested manner
without unwished for side effects, hence the frustration remaining
thus blocked.

Sometimes 'good enough' is just that, while an optimal solution can be
provided later.

Dans cette attente,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUHJjQAAoJECAB22fHtp27I0oH/3I4p8bLwYpYo0ef2dUgLauE
MncXJIAw+mjges9WwvPejZ8SLd8sfcl0gwQJe5nm4ASW5Xobe1sK/57Ai/Qx04UZ
BWnydHGYkupVmTSB2QJXuWXrJgBZ6qNDhpI+2QqsIUp8A/7wofH25+AIG89QYUmO
P9DttTlW0fqsNb1ftNPvon78gU0ZVZXX+CuetfiaIfeGOtpGaJhsp+K2B/g8DB0e
pcyKnaM5QIqLIxv9A6XgRfWAKxt6N7aCYYs5Ds5yQuWO5Ou5AEloYb6qeQcAWS91
8iq4cZ7pn3/V++ypyuzoLW1NktSNn5R8mJsLcjUmrJpE0RSZiW69FBuGmBegP0k=
=9JEN
-----END PGP SIGNATURE-----



Home | Main Index | Thread Index | Old Index