From: | "Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx> |
Date: | Sun, 3 Jul 2005 01:42:12 +0200 |
Lately Jeroen Ruigrok/asmodai <asmodai@xxxxxxxxxxxxx> said: > -On [20050702 20:14], Simon Schubert (corecode@xxxxxxxxxxxxxxxxxxxxxxx) wrote: > > Lots of third party programs declare > > extern int errno; > > > > This breaks when errno is declared as > > extern __thread int errno; > This change is bogus and I ask you to reverse it. > > Read up on: > http://standards.ieee.org/reading/ieee/interp/1003-1-90_int/pasc-1003.1-54.html then we were broken since ever, because __thread extern int errno is different from extern int errno could you please elaborate on the bogusness and the proper fix regarding the fact that we need to support a) threaded implementation b) programs that #include <errno.h> and erroneously do extern int errno; as therere are more than a dozen *major* programs out there doing this (perl, ruby, maybe python, just to mention some) c) best ABI compatibility to -Devel cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low $$$ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Attachment:
pgp00000.pgp
Description: PGP signature