[ghemical-devel] support for MPQC v2 was added

Tommi Hassinen thassine@messi.uku.fi
Tue, 21 May 2002 13:44:36 +0300 (WET)


On Tue, 21 May 2002, Michael Banck wrote:

> Hi,
> 
> On Tue, May 21, 2002 at 10:23:00AM +0300, Tommi Hassinen wrote:
> > It looks quite good, but now I have some problems with autoconf here.
> > Is it so that one should use autoconf just by running
> > 
> > 	autoconf
> > 
> > at the source top directory, right? It updated the configure script, and
> > the script worked OK otherwise except that in the resulting Makefile the
> > top_builddir variable was not set:
> > 
> > 	top_builddir=
> 
> Hmm, strange. I get
> 	top_builddir=   /home/mbanck/src/ghemical-test
> 
> here. What does
> grep top_builddir configure
> tell you? I get top_builddir=`pwd`, besides else.

It's there, somewhere, but is apparently not working:

$ grep top_builddir configure |grep pwd
ac_abs_top_builddir=`cd "$ac_dir" && cd $ac_top_builddir && pwd`
top_builddir=`pwd`
ac_abs_top_builddir=`cd "$ac_dir" && cd $ac_top_builddir && pwd`

> Ah, I didn't know that you need MPQC stuff in graphics, too. This has 
> canged since 0.82, hasn't it?

I think it's not changed, and it's safest just to put MPQC stuff
everywhere. You see, the "higher" directories like

	src/graphics
	src/target3

might include some files from the "lower" one

	src/common

and if the MPQC settings are not set in the "higher" directories as well,
it will not work (that's what just happened).

> We need to add
> 	@SC_CPPFLAGS@
> 
> to src/graphics/Makefile.in's INCS= variable then. 

Ok, done.

Now everything seems to work for me here, except that I still need to
set the top_builddir variable manually (due to obsolete autoconf).

> > Did I do something wrong with the autoconf, or is it a wrong version or
> > something like that?
> 
> No idea. Just strange that you used autoconf 2.13, configure.in says
> AC_PREREQ(2.48)
> 
> and I couldn't even run autoconf2.13 successfully when I commented that
> out, AC_PROG_CC_STDC was undefined. But even then top_builddir was set
> correctly :-/

Well, it then just looks that my autoconf is not new enough, right?
I add the other stuff to CVS but keep the current configure script.

	Tommi