nothing in config.log, but had to do '/bin/ksh config.status' by hand to gen Makefile

[Toni L. Harbaugh-Blackford]

It is not in the config.log file, but for some reason configure stops
before executing config.status, which is what really creates the
Makefile.

So running '/bin/ksh config.status' by hand created the Makefile and
other files.

make ran, and everything compiled.  So now I can test it.

On Thu, 29 Aug 2002, Wendy Palm wrote:

  > "Toni L. Harbaugh-Blackford" wrote:
  > > 
  > > I did both 'autoconf' and 'autoheader', then I ran 'configure' with my settings.
  > > 
  > > But no Makefile is generated.
  > > 
  > > So you are saying that 'configure' *SHOULD* have created the Makefile?
  > 
  > 
  > yes, configure is what creates the makefiles.  if it didn't, there was
  > at least one fatal error.  check config.log and see what it says.
  > 
  > 
  > 
  > -- 
  > wendy palm
  > Cray OS Sustaining Engineering, Cray Inc.
  > wendyp at cray.com, 651-605-9154
  > 

-----------------------------------------------------------------------
Toni Harbaugh-Blackford                     harbaugh at nciaxp.ncifcrf.gov
AlphaServer 8400 System Administrator
SAIC/NCI Frederick Advanced Biomedical Computing Center