| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
We need such a thing definitely!!! |
| 5 |
|
| 6 |
I would do it, but I don't have time now... |
| 7 |
|
| 8 |
Am 06.11.2011 21:30, schrieb Konstantin Tokarev: |
| 9 |
> |
| 10 |
> |
| 11 |
> 06.11.2011, 11:42, heroxbd@×××××.com: |
| 12 |
>> Jeremy Olexa <darkside@g.o> writes: |
| 13 |
>> |
| 14 |
>>> It isn't really a surprise to me. I've NEVER had gcc problems on RHEL4 |
| 15 |
>>> (glibc-2.3.4 or so). But there are reports of problems with RHEL5. |
| 16 |
>>> Gotta love linux, huh? =P |
| 17 |
>> |
| 18 |
>> I see. Then we really need a compatibility matrix tracking success and |
| 19 |
>> failure for each version combination of glibc and gcc. Sounds interesting? |
| 20 |
> |
| 21 |
> Surely! |
| 22 |
> |
| 23 |
|
| 24 |
- -- |
| 25 |
Moritz Schlarb |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 28 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 29 |
|
| 30 |
iQEcBAEBAgAGBQJOuA1KAAoJEEXT29373YiISd4H/iGOkGiT8RAijKtaIYOiLQUB |
| 31 |
MQBZW+2uXYQzedwCqIaA9KQHpt8j5d8+o4Ab1liPLrz/OTt5/s0//aeVM5JxZNHU |
| 32 |
jLginS8l/QuJ9aZmNkDJ9HjTSFkZUqklfV/Al0LswwteZeRlHqsFSqk+w7JvKPb5 |
| 33 |
DuaCXzRFUfqlWoJIs15fREHqkPIQkeXz4TKisunSpz6SzOSXmhNX04N+9lhej0UI |
| 34 |
z4o5Koa3pOwMz6kZIVUXXtuwXU3+JVcRlmsDEFJFAnd3vUsluisXYb3cghdTOp/S |
| 35 |
3Lvqs//t06sD+HEnreS3TZPwW7ZQ6nfAPgRvqtE2VwEz8fE+siE17/4Qgr+SepI= |
| 36 |
=T3+t |
| 37 |
-----END PGP SIGNATURE----- |
Archives