octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building PyTave on windows - cygwin


From: Mike Miller
Subject: Re: Building PyTave on windows - cygwin
Date: Wed, 15 Jun 2016 14:15:19 -0700
User-agent: Mutt/1.6.0 (2016-04-01)

On Thu, Jun 16, 2016 at 02:08:35 +0530, Abhinav Tripathi wrote:
> Well, I did the configure with the following:
> 
> $ CPPFLAGS='-I/e/octave_dev/include/octave-4.1.0+
> -I/e/octave_dev/include/octave-4.1.0+/octave'
> LDFLAGS=-L/e/octave_dev/lib/octave/4.1.0+ ./configure
> --with-octave=/e/octave_dev

Did the pytave configure give any errors or warnings, everything in the
summary at the end looked like it was detected and correct?

> Probably Mike could help (Assuming that the Makefile part of pytave was
> written by him).. Why are grep and sed being called at the linker stage? At
> what place in the Makefile.am (or any other m4 file) are they called? What
> are they supposed to do? Any suggestion to overwrite the directory they are
> searching in?

These are likely coming from the interaction between libtool and the
lib*.la files that appear to be part of the Windows binary distribution.
In short, libtool libraries install themselves plus a little helper
shell script that stores details about the library, including installed
location and dependencies. These are a hint, strictly unnecessary, and I
usually delete them first thing because they tend to cause more problems
than they solve, in my humble experience.

Try deleting the liboct*.la files and see if that helps.

-- 
mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]