Thank you; your suggestion appears to work perfectly.
I hadn't realized the name of the autogenerated file was under my control
in this way. Perhaps a future revision of the autotools might incorporate
the underlying logic (to avoid generating files with multiple dots in the
filename) in the interest of portability. Alas, I do not (yet?) have the
autotools expertise to propose a patch to do this.
Nonetheless, I do appreciate your kind assistance. Now I have only three
questions remaining :) Thank you again.
- WEB
--
Walter E. Brown, Ph.D. voice: +1 630 840-2784
CEPA Department, Mail Station 234
Fermi National Accelerator Laboratory
Batavia, IL 60510-0500
USA
----- Original Message -----
From: "Bernd Jendrissek" <[EMAIL PROTECTED]>
To: "Walter E. Brown" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, February 10, 2003 4:04 AM
Subject: Re: Four questions
| On Fri, Feb 07, 2003 at 02:41:07PM -0600, Walter E. Brown wrote:
| > 3) I read that it is recommended (for portability reasons) to avoid
use of
| > filenames that contain more than one dot; however, I see that a file
named
| > defs.h.in is being generated on my behalf. Is there a way to avoid
this
| > behavior?
|
| AC_CONFIG_HEADERS([defs.h:defs.hin]) maybe?
