>> While troubleshooting the previously
>> reported "No such file or directory" errors, I noticed many
>> "/opt/trinity/bin" duplications in the configure files. For
>> example:
>>
>> arts/admin/acinclude.m4.in:
>>
>> kde_default_bindirs="/usr/bin /usr/local/bin /opt/local/bin
>> /usr/X11R6/bin /opt/kde/bin /opt/trinity/bin
>> /opt/trinity/bin /usr/kde/bin /usr/local/kde/bin"
>>
>> arts/admin/cvs.sh:
>>
>> export PATH=$PATH:/opt/trinity/bin:/opt/trinity/bin
>>
>> Harmless I think, but unless there is a reason to duplicate
>> those paths a quick sed through the GIT tree would clean
>> everything :)
>
> Um, not harmless. :(
>
> I tried deleting those second instances and none of the automake packages
> would build. The build process would create the make files and run
> configure, but then repeat that process, thereby corrupting the files.
>
> Perhaps somebody will explain why that is necessary, but oops! Never mind!

I have no idea.  Autotools can be a magic black box, which is one reason
of many for the desire to move to CMake.  I'm probably not going to patch
Autotools files unless they don't build, as there is too much danger of
making a "simple" change and breaking something obscure later on.

Tim