[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Constantly changing libtool
From: |
Laurence Marks |
Subject: |
Re: Constantly changing libtool |
Date: |
Thu, 15 Apr 2021 09:41:26 -0500 |
As you say, it has files generated by autotools in a cvs (anonymous), so
when checking out there is a clash.
---
The software is at http://www.numis.northwestern.edu/Software/, mainly edm
& semper-7.0beta. They are both old, not so great but I still use them
every year or so for teaching, and there are a few others who use them.
They are updated via cvs (yes, they are that old). I am updating them
currently (for a class) so they may be changing.
At least for edm most of the problems are with fftw-2.1.5 (
http://www.fftw.org/download.html) which is also somewhat old. (Updating
the code to use more recent fftw would be a pain.)
On Thu, Apr 15, 2021 at 9:27 AM Peter Johansson <trojkan@gmail.com> wrote:
> Hi Laurence,
>
> On 15/4/21 6:35 am, Bob Friesenhahn wrote:
> > Most problems seem to stem from packages providing the generated files
> > from Autoconf, Automake, and libtool so that end users don't need to
> > have the tools available.
>
> It will be easier for people here to help if you provide a bit more
> information about your set-up. Is the problem when building from a
> tarball or when building from git/subversion? If the latter, do have you
> checked in files generated by autotools into git/subversion, so when
> checking out/cloning the source to a system with other autotools
> versions, there becomes a clash between versions?
>
> Cheers,
>
> Peter
>
>
>
>
--
Professor Laurence Marks
Department of Materials Science and Engineering
Northwestern University
www.numis.northwestern.edu
"Research is to see what everybody else has seen, and to think what nobody
else has thought" Albert Szent-Györgyi