aclocal and sinclude

[Kirk McKelvey]

At our company, we have a homegrown build harness that is still back on automake v1.5.  Wanting to get multiple binary targets into a single makefile.am I have been attempting to upgrade to 1.9.4.  Unfortunately aclocal does not seem to honor "sinclude", which we use to include an optional m4 file.  When I say it does not honor "sinclude", I mean that it makes it equivalent to "include", requiring the target file to be present.  But "sinclude" should quietly fail if its target file is not present.

Searching the archives has not shown any mention of sinclude since 2003, and what I find there makes me think "sinclude" is intentionally not distinguished from "include".  Is this true?

Kirk McKelvey