dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

I tried to install automake 1.9 (1.9.6) and now I get the same
problem. Looks like something has changed. I'll see if I can find out
what goes wrong.

/Anders

On Fri, Oct 28, 2005 at 05:52:05PM +0200, Garth N. Wells wrote:
> 
> Quoting Anders Logg <logg@xxxxxxxxx>:
> 
> > Strange. What versions of automake and autoconf do you have?
> > 
> 
> # automake --version
> automake (GNU automake) 1.9.5
> 
> # autoconf --version
> autoconf (GNU Autoconf) 2.59
> 
> I think that this is the issue. I did two clean check outs, and on one I ran
> scripts/preconfigure, and one I didn't. I did a diff on the two directories and
> only differences were in Makefile and Makefile.in.
> 
> I didn't have a problem with this version of automake before. Any ideas which
> changes may have affected it?
> 
> Garth
> 
> > # automake --version
> > automake (GNU automake) 1.4-p4
> > 
> > # autoconf --version
> > autoconf (GNU Autoconf) 2.59
> > 
> > /Anders
> > 
> > On Fri, Oct 28, 2005 at 05:34:56PM +0200, Garth N. Wells wrote:
> > > I still have a problem. If I check out a clean version and do
> > > 
> > > ./configure.local
> > > make
> > > make install
> > > make demo
> > > 
> > > everything works. But when I do
> > > 
> > > scripts/preconfigure
> > > ./configure.local
> > > make
> > > make install
> > > 
> > > all the header files get dumped in $DOLFIN_DIR/local/include.
> > > 
> > > Garth
> > > 
> > > Quoting Anders Logg <logg@xxxxxxxxx>:
> > > 
> > > > Yes, the header files got installed in the wrong place. I don't know
> > > > why it happened but everything went back to normal after running
> > > > 
> > > >     scripts/preconfigure
> > > > 
> > > > and then ./configure[.local] again.
> > > > 
> > > > Maybe someone checked in code from some old version that still had the
> > > > old build system and CVS merged in the changes wrong.
> > > > 
> > > > Everyone should check out a clean version before checking anything
> > > > more in.
> > > > 
> > > > /Anders
> > > > 
> > > > On Fri, Oct 28, 2005 at 04:56:34PM +0200, Garth N. Wells wrote:
> > > > > The header files are being placed in $DOLFIN_DIR/local/include, and not
> > in
> > > > > $DOLFIN_DIR/local/include/dolfin (the directory 'dolfin' is being made
> > > > however).
> > > > > Also, in a demo directory, the include directory paths provided by
> > > > > "dolfin-config --cflags" are incorrect.
> > > > > 
> > > > > I didn't notice the problem until I changed the name of a header file
> > > > because
> > > > > old files from $DOLFIN_DIR/include/dolfin were being included.
> > > > > 
> > > > > Garth
> > > > > 
> > > > > 
> > > > > Quoting Anders Logg <logg@xxxxxxxxx>:
> > > > > 
> > > > > > I'll take a look. It worked fine when I tested it, but something
> > must
> > > > > > have broken along the way.
> > > > > > 
> > > > > > /Anders
> > > > > > 
> > > > > > On Fri, Oct 28, 2005 at 04:06:11PM +0200, Garth N. Wells wrote:
> > > > > > > There are some serious issues with the new build system. Rather
> > than a
> > > > > > > convoluted attempt at an explanation, try checking out a fresh
> > version
> > > > > > (because
> > > > > > > in old working copies things will work due to old files lying
> > around)
> > > > and
> > > > > > doing
> > > > > > > ./configure.local
> > > > > > > make
> > > > > > > make install
> > > > > > > make demo (which will break)
> > > > > > > 
> > > > > > > The location of the header file seems all messed up. I don't know
> > > > exactly
> > > > > > what
> > > > > > > changes were made to the build system, so it's hard to track down.
> > > > > > > 
> > > > > > > Garth
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > DOLFIN-dev mailing list
> > > > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > > > http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> 

-- 
Anders Logg
Research Assistant Professor
Toyota Technological Institute at Chicago
http://www.tti-c.org/logg/