[ptx] Hugin - compilation problems

[Steve Wesemeyer]

On Wednesday 12 January 2005 08:23, douglas wilkins wrote:
<snip>
> > - Uninstall the SUSE 9.2 fftw2 packages as the
> > configure script would not find
> > the libraries (even when I specified the path in
> > --with-fftw-libraries) and
> > compile and install them from source.
>
> As far as I know, Suse provides double precision fftw
> (dfftw) packages only, so at the moment you _have_ to
> compile fftw2 yourself :-(
>

You are right. I should have noticed that. Thanks for pointing that out.
>
> I have just committed some changes to CVS (will
> probably take a while to show up on the anonymous
> mirrors) which should cure some of these problems. If
> you could download the changes and try again, that
> would be great. If it still does not compile, could
> you please send me your config.log so that I can
> diagnose further.
>
> You should download and compile the latest panotools
> libpano as well, since there are changes for the 64
> bit linux platform there as well.

Just downloaded the latest cvs snapshot and managed to compiled it.
However, I had to explicitly tell configure where the fftw libraries were 
installed whereas the previous snapshot ./configure still finds them, eg

./configure output with tonight's snapshot:
  FFTW_INCLUDES  = -I/usr/local/include
  FFTW_LDFLAGS   =
  BOOST_VERSION  = 1.31
  BOOST_CFLAGS   =
  BOOST_LIBS     =
  BOOST_TEST_LIB =
  BUILD          = linux
  CPU            = amd64

./configure output with 20050107 snapshot:

  FFTW_INCLUDES  = -I/usr/local/include
  FFTW_LDFLAGS   = -L/usr/local/lib
  BOOST_VERSION  = 1.31
  BOOST_CFLAGS   = -I/usr/include
  BOOST_LIBS     = -L/usr/lib
  BOOST_TEST_LIB =
  BUILD          = linux

As you can see, the first one hasn't found the libraries whereas the second 
one did.

I traced it to the ax_fftw macro (which is probably one of the ones you 
changed) and I saw that there is now an explicit check for amd64 in there and 
it then looks for fftw in /usr/lib64. However, when I did the 
normal ./configure;make;make install for fftw on my AMD64 they were placed 
in /usr/lib by default. I guess I should have specified a different target 
directory...

Boost libs provide another slight oddity. In the previous CVS version I 
compiled the actual Boost_Libs path is wrong, it should be /usr/lib64 but it 
didn't affect the compilation.The new snapshot looks as if it didn't find 
them at all but obviously does. Again I looked at the diffs and the new code 
checks for the stuff in the right places (AFAICT) but then sets the variables 
to "" so they don't show up in the output of the config. Not really a problem 
as the compilation still works fine but it got me a bit worried especially 
after finding out that fftw wasn't detected anymore.

> Must admit that checkinstall would not be my personal
> choice, since it so often gets it wrong. Perhaps you
> could take a look at brunos' rpm spec file and adapt
> it for Suse?

I haven't had any problems with checkinstall so far and the previous versions 
of hugin that I compiled (around summer time last year) used to work with it 
as well. I'm sure once the build process has settled across the various 
architectures that hugin runs on, it might work again. But I'll have a look 
at building an rpm by hand as well...

> > Thanks to everyone for your help. I really
> > appreciate hugin. It's a great tool
> > and definitely worth the pain to get it to compile.
>
> Less pain soon :-)

Already much better! Thanks a lot!

Cheers,
 Steve