Re: failed to re-find parent key

Поиск
Список
Период
Сортировка
Искать
От
Greg Stark
Тема
Re: failed to re-find parent key
Дата
Msg-id
871xq3ck8g.fsf@stark.xeocode.com
Ответ на
Список
Дерево обсуждения
failed to re-find parent key Dave Cramer <pg@fastcrypt.com>
Re: failed to re-find parent key Dave Cramer <pg@fastcrypt.com>
Re: failed to re-find parent key Tom Lane <tgl@sss.pgh.pa.us>
Re: failed to re-find parent key Dave Cramer <pg@fastcrypt.com>
Re: failed to re-find parent key Tom Lane <tgl@sss.pgh.pa.us>
Re: failed to re-find parent key Dave Cramer <pg@fastcrypt.com>
Re: failed to re-find parent key Tom Lane <tgl@sss.pgh.pa.us>
Re: failed to re-find parent key Dave Cramer <pg@fastcrypt.com>
Re: failed to re-find parent key Tom Lane <tgl@sss.pgh.pa.us>
Re: failed to re-find parent key Greg Stark <gsstark@mit.edu>

Tom Lane  writes:

> Hmm.  Compiler bug maybe?  I can't recall if gcc 2.96 had a good
> reputation or not.  

2.96's reputation is of being *THE* canonical bad version of gcc.

mplayer for example has a configure check that specifically makes it difficult
to compile with 2.96 without reading large warnings because they've had too
many bug reports get tracked down to it:
   Note for gcc 2.96 users: Some versions of this compiler are known to miscompile   mplayer and lame (which is used for mencoder).  If you get compile errors,   first upgrade to the latest 2.96 release (minimum 2.96-85) and try again.   If the problem still exists, try with gcc 3.x (or 2.95.x) *BEFORE* reporting   bugs!
           GCC 2.96 IS NOT AND WILL NOT BE SUPPORTED BY US !

-- 
greg


В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Dave Cramer
Дата:
FAQ