FIXINCLUDES OPERATION
=====================
-See also: http://autogen.linuxbox.com/fixincludes
+See also: http://autogen.SourceForge.net/fixincludes
The set of fixes required was distilled down to just the data required
to specify what needed to happen for each fix. Those data were edited
into a file named gcc/fixinc/inclhack.def. A program called
-AutoGen (http://autogen.linuxbox.com) uses these definitions to
-instantiate several different templates (gcc/fixinc/*.tpl) that then
+AutoGen (http://autogen.SourceForge.net, ver 4.x) uses these definitions
+to instantiate several different templates (gcc/fixinc/*.tpl) that then
produces a fixincludes replacement shell script (inclhack.sh), a
-replacement binary program (fixincl.x) and a script to drive the
-binary fixincl.sh).
+replacement binary program (fixincl.x).
If there is no special purpose script, then mkfixinc.sh will try to
-compile, link and test execute the binary version. If it cannot be
-successfully built, the shell version will be used instead. If
-mkfixinc.sh determines that your system needs machine-specific fixes
-that have not yet been applied to inclhack.def, it will install and
-use the current fixinc.* for that system instead.
+compile, link and execute the fixincl program. Otherwise, it will
+install and use the current fixinc.* for that system instead.
+Also, on certain platforms (viz. those that do not have functional
+bidirectional pipes), the fixincl program is split into two.
+This should only concern you on DOS and BeOS.
Regards,
- Bruce <autogen@linuxbox.com>
+ Bruce <bkorb@gnu.org>