[ptx] problems with cvs snapshot of libpano12
Daniel M. German
dmgerman at uvic.ca
Tue May 2 19:21:05 BST 2006
Rich twisted the bytes to say:
Rich> first, thanks for the cvs snapshots - hopefully they will make it easier
Rich> to test new features and problems before releases :)
Rich> using a cvs snapshot downloaded a couple of hours ago.
Rich> now, some problems and questions :
Both seem to be an autoconf problem.
Why I don't understand is slackware creates different configuration
files than, say, Fedora. What architecture were you using? Can you
give us more information about your set up?
uname -a
autoconf --version
automake --version
can you please send me a copy of ./Makefile and ./configure?
Thanks Rich,
daniel
Rich> 1. in slackware, bootstrapping/configuring libpano still requires
Rich> exporting of CFLAGS="-lm";
Rich> 2. compiling of libpano12 fails - possibly because of some libraries,
Rich> invoked with -lm. some last lines :
A quick fix to this is to find InsertFileName and remove the #ifdefs
around it. Windows has exactly the same problem than your
installation.
Rich> gcc: -lm: linker input file unused because linking not done
Rich> /bin/sh ../libtool --tag=CC --mode=link gcc -lm -L.. -o PTmender
Rich> PTmender.o ColourBrightness.o PTcommon.o -lpano12 -ljpeg
Rich> -ltiff
Rich> gcc -o .libs/PTmender PTmender.o ColourBrightness.o PTcommon.o
Rich> -L/install/pano/cvs/libpano /install/pano/cvs/libpano/.libs/l
Rich> ibpano12.so -lpng /usr/lib/libtiff.so -ljpeg -lz -lm -lc
Rich> PTmender.o(.text+0x625): In function `main':
Rich> : undefined reference to `InsertFileName'
Rich> PTmender.o(.text+0x82e): In function `main':
Rich> : undefined reference to `InsertFileName'
Rich> collect2: ld returned 1 exit status
Rich> make[2]: *** [PTmender] Error 1
Rich> make[2]: Leaving directory `/install/pano/cvs/libpano/tools'
Rich> make[1]: *** [all-recursive] Error 1
Rich> make[1]: Leaving directory `/install/pano/cvs/libpano'
Rich> make: *** [all] Error 2
Rich> what could be causing this and what can i do to fix it ?
Rich> i was using ./bootstrap && ./configure && ./make sequence
Rich> 3. i'm thinking about building libpano and hugin with debugging symbols
Rich> included (so that possibly useful backtraces could be gathered), but was
Rich> unable to find anything related to debugging in libpano configure help.
Rich> what steps must i take to ensure debugging information is included in
Rich> the final build ?
Rich> --
A easy way is to define CC=gcc -g before running configure (I think
that will do it)
Rich
--
Daniel M. German ""Geek" is a badge of honor."
Eric Schmidt, CEO of Novell
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
More information about the ptx
mailing list