-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 understood. but an OS update could lead to updated C runtime headers?
Am 23.01.2010 17:39, schrieb Richard Guenther: > On Sat, Jan 23, 2010 at 5:34 PM, Franz Fehringer <feh...@t-online.de> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> I have two hopefully not too dull questions about the gcc fixincludes >> mechanism: >> 1) When after the initial fixinclude run (parts of) new software is >> installed into /usr/include, the fixincludes run has to be repeated (at >> least in principle), is this true? > > As we generally only fixinclude pieces of the C runtime and the C > runtime is required to build GCC this is not true. fixincludes may of > course match in random header files as well, but that is not > intended in general. > >> 2) IIRC several years ago there were plans to abandon fixincludes and to >> do the header fixing in realtime on every gcc run, what happened to the >> pertaining efforts? > > That would surely be slow. > > Richard. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLWycyAAoJEETPNNlkrKDyO0gH/jyNqPGiDw1KZ60pXi8x64xl KfymWY4sarWK+Uovqyh1kty0gsHu+lkB9QIpb+XlJPvme2Y6XUX5k4KTRj3rvB/i YcAY+LJgjjZZruxkhyxL4HoXU7TLa4OaiJcuWQqp/9dTZbjCWULnOHuGv1uxEgF+ yZrsGv9FQo2WnrCDt5+ltwvDS5cxkLnyQUh89bokPfujKcvu6tDKF7wMUfbxs16n 1exf7nlCJqKNl7xhrEiWCKQZuu3ke3ApUjOWMVlUF8IneukaP2PbynMP00bSDcNJ RvrgF/9CQ9DqWbCOeBojWJaDLcGBy2K5hUI5iHb5fKiId7l8bOWzYMZHVTqR8jo= =S2NG -----END PGP SIGNATURE-----
