Panorama Tools

On Wed 30-Aug-2006 at 19:11 -0300, Carlos Eduardo G. Carvalho wrote:

> /home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
> reference to `gtk_widget_grab_default'

I thought this was fixed...

In the sources there is a broken gtk1 interface for dialog boxes.  
When the build script can't identify the system it tries to build 
this and always fails.

The workaround is to find every reference to 'sys_X11' and replace it 
with 'sys_ansi'.

-- 
Bruno

Thanks Bruno, but unfortunately I couldn't solve the problem
completely... I used:=20
> rpl -R sys_X11 sys_ansi *

and now I have fewer undefined references, but still have some (below).
Anybody can help me with a hint of what is missing? Maybe libgcj? (saw
this on README and couldn't install yet)

---------------------------------------------------------------------------=
----------
Making all in tools
/usr/local/bin/bash ../libtool --tag=3DCC --mode=3Dlink gcc  -g -O2  -L..
-o panoinfo      -lpano12
mkdir .libs
gcc -g -O2 -o .libs/panoinfo
-L/home/cartola/lixo/libpano12-2.8.4 /home/cartola/lixo/libpano12-2.8.4/.li=
bs/libpano12.so -L/usr/local/lib -ljpeg -lpng -ltiff -lz -Wl,--rpath -Wl,/u=
sr/local/lib
/usr/lib/crt1.o(.text+0x72): In function `_start':
: undefined reference to `main'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `makePathToHost'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `readPrefs'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `mymalloc'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `SaveFileAs'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `readImage'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `makeTempPath'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `infoDlgIntern'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `FindFile'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `myfree'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `GetFullPath'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `PrintErrorIntern'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `showScript'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `MakeTempName'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `writePrefs'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `ProgressIntern'
/home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
reference to `makePathForResult'
*** Error code 1

Stop in /home/cartola/lixo/libpano12-2.8.4/tools.
*** Error code 1

Stop in /home/cartola/lixo/libpano12-2.8.4.
*** Error code 1

Stop in /home/cartola/lixo/libpano12-2.8.4.
---------------------------------------------------------------------------=
----------


Thank you!

Carlos E. G. Carvalho           OpenIT Solucoes Tecnologicas
Consultor Unix/Internet         Tel. +55 21 2517-6000
http://www.OpenIT.com.br
http://www.MyFreeBSD.com.br

Em Qua, 2006-08-30 =E0s 23:31 +0100, Bruno Postle escreveu:

> On Wed 30-Aug-2006 at 19:11 -0300, Carlos Eduardo G. Carvalho wrote:
>=20
> > /home/cartola/lixo/libpano12-2.8.4/.libs/libpano12.so: undefined
> > reference to `gtk_widget_grab_default'
>=20
> I thought this was fixed...
>=20
> In the sources there is a broken gtk1 interface for dialog boxes. =20
> When the build script can't identify the system it tries to build=20
> this and always fails.
>=20
> The workaround is to find every reference to 'sys_X11' and replace it=20
> with 'sys_ansi'.
>=20

On Wed 30-Aug-2006 at 23:19 -0300, Carlos Eduardo wrote:
>
> Bruno, are you the one with whom I can talk to make some changes 
> part of the original code, making life easyer on future versions?

Patches are welcome, you should send them to the list or you can 
send them to me or one of the developers.

I noticed that you are using CVS, we switched to SVN recently - The 
code for pano12 hasn't changed much snce then.  Instructions for 
checking out the code via SVN are at the bottom of the sourceforge 
page:

http://panotools.sourceforge.net/

-- 
Bruno

Ok, I will try to make a patch to the svn code, but by now I'm going to
finish porting the *.tar.gz version to FreeBSD with some more tests. I
have to use this version to do the port, as it is more easily
downloadable by the freebsd port system.

In fact, the only 2 patches I have made were the configure one, putting
"freebsd*" on the "case" statement and a patch to change sys_X11 to
sys_ansi in some files. Another thing I had to do was setting CPPFLAGS
variable so that some include's could be found.

Thanks again!

--=20
Carlos E. G. Carvalho           OpenIT Solucoes Tecnologicas
Consultor Unix/Internet         Tel. +55 21 2517-6000
http://www.OpenIT.com.br
http://www.MyFreeBSD.com.br

Em Qui, 2006-08-31 =E0s 11:46 +0100, Bruno Postle escreveu:

> On Wed 30-Aug-2006 at 23:19 -0300, Carlos Eduardo wrote:
> >
> > Bruno, are you the one with whom I can talk to make some changes=20
> > part of the original code, making life easyer on future versions?
>=20
> Patches are welcome, you should send them to the list or you can=20
> send them to me or one of the developers.
>=20
> I noticed that you are using CVS, we switched to SVN recently - The=20
> code for pano12 hasn't changed much snce then.  Instructions for=20
> checking out the code via SVN are at the bottom of the sourceforge=20
> page:
>=20
> http://panotools.sourceforge.net/
>=20

Hi people,

I am now having some problems with boost thread lib to compile hugin. I
already have boost lib installed and have compiled hugin 0.5.4 before
(that's the actual version of the freebsd port). Now my compilation
stops on the configure. I bypassed the configure analisys (changing the
configure file) just to try to see if the compilation would go ok and it
didn't. I guess the boost is compiled ok, but don't know if there is
some special option. The boost package seams to be compiled with
threads. This is the default installation and the package gives the
message "You have built the Boost library with thread support. Don't
forget to add -pthread to your linker options when linking your code.".
Well, I guess the -pthread option is beeing used. The config.log shows
"BOOST_CPPFLAGS='-pthread -I/usr/local/include'". The configure result
is as follows. Any help is welcome.

(...)
checking if Panotools package is complete... yes
checking for boostlib >= 1.31... yes
boost found
checking whether the Boost::Thread library is available... yes
checking for main in -lboost_thread-gcc-mt-1_32... no
checking for main in -lboost_thread-gcc-mt-s-1_32... no
checking for main in -lboost_thread-gcc-1_32... no
checking for main in -lboost_thread-gcc-s-1_32... no
checking for main in -lboost_thread-mgw-mt-1_32... no
checking for main in -lboost_thread-mgw-mt-s-1_32... no
checking for main in -lboost_thread-mgw-1_32... no
checking for main in -lboost_thread-mgw-s-1_32... no
checking for main in -lboost_thread-mt-1_32... no
checking for main in -lboost_thread-mt-s-1_32... no
checking for main in -lboost_thread-1_32... no
checking for main in -lboost_thread-s-1_32... no
checking for main in -lboost_thread-gcc-mt... no
checking for main in -lboost_thread-gcc-mt-s... no
checking for main in -lboost_thread-gcc... no
checking for main in -lboost_thread-gcc-s... no
checking for main in -lboost_thread-mgw-mt... no
checking for main in -lboost_thread-mgw-mt-s... no
checking for main in -lboost_thread-mgw... no
checking for main in -lboost_thread-mgw-s... no
checking for main in -lboost_thread-mt... no
checking for main in -lboost_thread-mt-s... no
checking for main in -lboost_thread... no
checking for main in -lboost_thread-s... no
checking for main in -llibboost_thread-gcc-mt-1_32... no
checking for main in -llibboost_thread-gcc-mt-s-1_32... no
checking for main in -llibboost_thread-gcc-1_32... no
checking for main in -llibboost_thread-gcc-s-1_32... no
checking for main in -llibboost_thread-mgw-mt-1_32... no
checking for main in -llibboost_thread-mgw-mt-s-1_32... no
checking for main in -llibboost_thread-mgw-1_32... no
checking for main in -llibboost_thread-mgw-s-1_32... no
checking for main in -llibboost_thread-mt-1_32... no
checking for main in -llibboost_thread-mt-s-1_32... no
checking for main in -llibboost_thread-1_32... no
checking for main in -llibboost_thread-s-1_32... no
checking for main in -llibboost_thread-gcc-mt... no
checking for main in -llibboost_thread-gcc-mt-s... no
checking for main in -llibboost_thread-gcc... no
checking for main in -llibboost_thread-gcc-s... no
checking for main in -llibboost_thread-mgw-mt... no
checking for main in -llibboost_thread-mgw-mt-s... no
checking for main in -llibboost_thread-mgw... no
checking for main in -llibboost_thread-mgw-s... no
checking for main in -llibboost_thread-mt... no
checking for main in -llibboost_thread-mt-s... no
checking for main in -llibboost_thread... no
checking for main in -llibboost_thread-s... no
configure: Could not link against libboost_thread-s !
configure: error:
        the boost thread library must be installed on your system
        but configure could not find it. Use --with-boost to
        specify the location of the boost library and
        --with-boost-version to specify your version.
        On debian based systems, install libboost-thread-dev
    
===>  Script "configure" failed unexpectedly.
Please report the problem to cartola@... [maintainer] and
attach
the
"/sata/ports-mais-novos/graphics/hugin-0.6.1/work/hugin-0.6.1/config.log"
including the output of the failure of your make command. Also, it might
be
a good idea to provide an overview of all packages installed on your
system
(e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /sata/ports-mais-novos/graphics/hugin-0.6.1.

Carlos E. G. Carvalho           OpenIT Solucoes Tecnologicas
Consultor Unix/Internet         Tel. +55 21 2517-6000
http://www.OpenIT.com.br
http://www.MyFreeBSD.com.br

Carlos Eduardo wrote:

> checking if Panotools package is complete... yes
> checking for boostlib >= 1.31... yes
> boost found
> checking whether the Boost::Thread library is available... yes
> checking for main in -lboost_thread-gcc-mt-1_32... no
> checking for main in -lboost_thread-gcc-mt-s-1_32... no
> checking for main in -lboost_thread-gcc-1_32... no
> checking for main in -lboost_thread-gcc-s-1_32... no
> checking for main in -lboost_thread-mgw-mt-1_32... no
> checking for main in -lboost_thread-mgw-mt-s-1_32... no
> checking for main in -lboost_thread-mgw-1_32... no
> checking for main in -lboost_thread-mgw-s-1_32... no
> checking for main in -lboost_thread-mt-1_32... no
> checking for main in -lboost_thread-mt-s-1_32... no
> checking for main in -lboost_thread-1_32... no
> checking for main in -lboost_thread-s-1_32... no
> checking for main in -lboost_thread-gcc-mt... no
> checking for main in -lboost_thread-gcc-mt-s... no
> checking for main in -lboost_thread-gcc... no
> checking for main in -lboost_thread-gcc-s... no
> checking for main in -lboost_thread-mgw-mt... no
> checking for main in -lboost_thread-mgw-mt-s... no
> checking for main in -lboost_thread-mgw... no
> checking for main in -lboost_thread-mgw-s... no
> checking for main in -lboost_thread-mt... no
> checking for main in -lboost_thread-mt-s... no
> checking for main in -lboost_thread... no
> checking for main in -lboost_thread-s... no
> checking for main in -llibboost_thread-gcc-mt-1_32... no
> checking for main in -llibboost_thread-gcc-mt-s-1_32... no
> checking for main in -llibboost_thread-gcc-1_32... no
> checking for main in -llibboost_thread-gcc-s-1_32... no
> checking for main in -llibboost_thread-mgw-mt-1_32... no
> checking for main in -llibboost_thread-mgw-mt-s-1_32... no
> checking for main in -llibboost_thread-mgw-1_32... no
> checking for main in -llibboost_thread-mgw-s-1_32... no
> checking for main in -llibboost_thread-mt-1_32... no
> checking for main in -llibboost_thread-mt-s-1_32... no
> checking for main in -llibboost_thread-1_32... no
> checking for main in -llibboost_thread-s-1_32... no
> checking for main in -llibboost_thread-gcc-mt... no
> checking for main in -llibboost_thread-gcc-mt-s... no
> checking for main in -llibboost_thread-gcc... no
> checking for main in -llibboost_thread-gcc-s... no
> checking for main in -llibboost_thread-mgw-mt... no
> checking for main in -llibboost_thread-mgw-mt-s... no
> checking for main in -llibboost_thread-mgw... no
> checking for main in -llibboost_thread-mgw-s... no
> checking for main in -llibboost_thread-mt... no
> checking for main in -llibboost_thread-mt-s... no
> checking for main in -llibboost_thread... no
> checking for main in -llibboost_thread-s... no
> configure: Could not link against libboost_thread-s !
> configure: error:
>         the boost thread library must be installed on your system
>         but configure could not find it. Use --with-boost to
>         specify the location of the boost library and
>         --with-boost-version to specify your version.
>         On debian based systems, install libboost-thread-dev

Unfortunately, the boost libraries encode various information in the library 
name. Can you tell me how the libboost_thread*.so file is named on FreeBSD?

The configure script/autoconf macros then needs to be modified to look for 
this library.

ciao
   Pablo

Is it that simple? I don't know... it looks like something of the boost
lib have been found:
        checking for boostlib >=3D 1.31... yes
        boost found
        checking whether the Boost::Thread library is available... yes
And on FreeBSD these libs are in a quite standard place (at least in my
point of view :) ):
        /usr/local/lib/libboost_thread.a
        /usr/local/lib/libboost_thread.so
        /usr/local/lib/libboost_thread.so.2
Do I have to change something? I tried to run "./configure
--with-boost=3D/usr/local/lib" but the result has been the same.

Can it be some function available on newer versions? I have boost-1.32.0
and have also tested with 1.33.1 in another machine.

Thanks!

Carlos E. G. Carvalho           OpenIT Solucoes Tecnologicas
Consultor Unix/Internet         Tel. +55 21 2517-6000
http://www.OpenIT.com.br
http://www.MyFreeBSD.com.br

Em Qui, 2006-09-07 =E0s 22:26 +0100, Pablo d'Angelo escreveu:
> Carlos Eduardo wrote:
>=20
> > checking if Panotools package is complete... yes
> > checking for boostlib >=3D 1.31... yes
> > boost found
> > checking whether the Boost::Thread library is available... yes
> > checking for main in -lboost_thread-gcc-mt-1_32... no
> > checking for main in -lboost_thread-gcc-mt-s-1_32... no
> > checking for main in -lboost_thread-gcc-1_32... no
> > checking for main in -lboost_thread-gcc-s-1_32... no
> > checking for main in -lboost_thread-mgw-mt-1_32... no
> > checking for main in -lboost_thread-mgw-mt-s-1_32... no
> > checking for main in -lboost_thread-mgw-1_32... no
> > checking for main in -lboost_thread-mgw-s-1_32... no
> > checking for main in -lboost_thread-mt-1_32... no
> > checking for main in -lboost_thread-mt-s-1_32... no
> > checking for main in -lboost_thread-1_32... no
> > checking for main in -lboost_thread-s-1_32... no
> > checking for main in -lboost_thread-gcc-mt... no
> > checking for main in -lboost_thread-gcc-mt-s... no
> > checking for main in -lboost_thread-gcc... no
> > checking for main in -lboost_thread-gcc-s... no
> > checking for main in -lboost_thread-mgw-mt... no
> > checking for main in -lboost_thread-mgw-mt-s... no
> > checking for main in -lboost_thread-mgw... no
> > checking for main in -lboost_thread-mgw-s... no
> > checking for main in -lboost_thread-mt... no
> > checking for main in -lboost_thread-mt-s... no
> > checking for main in -lboost_thread... no
> > checking for main in -lboost_thread-s... no
> > checking for main in -llibboost_thread-gcc-mt-1_32... no
> > checking for main in -llibboost_thread-gcc-mt-s-1_32... no
> > checking for main in -llibboost_thread-gcc-1_32... no
> > checking for main in -llibboost_thread-gcc-s-1_32... no
> > checking for main in -llibboost_thread-mgw-mt-1_32... no
> > checking for main in -llibboost_thread-mgw-mt-s-1_32... no
> > checking for main in -llibboost_thread-mgw-1_32... no
> > checking for main in -llibboost_thread-mgw-s-1_32... no
> > checking for main in -llibboost_thread-mt-1_32... no
> > checking for main in -llibboost_thread-mt-s-1_32... no
> > checking for main in -llibboost_thread-1_32... no
> > checking for main in -llibboost_thread-s-1_32... no
> > checking for main in -llibboost_thread-gcc-mt... no
> > checking for main in -llibboost_thread-gcc-mt-s... no
> > checking for main in -llibboost_thread-gcc... no
> > checking for main in -llibboost_thread-gcc-s... no
> > checking for main in -llibboost_thread-mgw-mt... no
> > checking for main in -llibboost_thread-mgw-mt-s... no
> > checking for main in -llibboost_thread-mgw... no
> > checking for main in -llibboost_thread-mgw-s... no
> > checking for main in -llibboost_thread-mt... no
> > checking for main in -llibboost_thread-mt-s... no
> > checking for main in -llibboost_thread... no
> > checking for main in -llibboost_thread-s... no
> > configure: Could not link against libboost_thread-s !
> > configure: error:
> >         the boost thread library must be installed on your system
> >         but configure could not find it. Use --with-boost to
> >         specify the location of the boost library and
> >         --with-boost-version to specify your version.
> >         On debian based systems, install libboost-thread-dev
>=20
> Unfortunately, the boost libraries encode various information in the libr=
ary=20
> name. Can you tell me how the libboost_thread*.so file is named on FreeBS=
D?
>=20
> The configure script/autoconf macros then needs to be modified to look fo=
r=20
> this library.
>=20
> ciao
>    Pablo
>=20
>=20
>=20
>=20
>=20
> !DSPAM:45008ceb384315209328925!
>=20

Carlos Eduardo <cartola@...> writes:



> > > checking for main in -llibboost_thread-mt-s... no
> > > checking for main in -llibboost_thread... no
> > > checking for main in -llibboost_thread-s... no
> > > configure: Could not link against libboost_thread-s !
> > > configure: error:
> > >         the boost thread library must be installed on your system
> > >         but configure could not find it. Use --with-boost to
> > >         specify the location of the boost library and
> > >         --with-boost-version to specify your version.
> > >         On debian based systems, install libboost-thread-dev
> > 


Hello

I have no  FreeBSD, but I tried to compile hugin 0.6 on a Gentoo Linux and had
exactly the same error message. 
I reinstalled the boost with thread support ( in gentoo: with a "thread" useflag
) and after that i was able to compile hugin.  

My version of boost:  1.33.1

I hope this infomation will help you.

Ciao
niko

> > > > checking for main in -llibboost_thread-mt-s... no
> > > > checking for main in -llibboost_thread... no
> > > > checking for main in -llibboost_thread-s... no
> > > > configure: Could not link against libboost_thread-s !
> > > > configure: error:
> > > >         the boost thread library must be installed on your system
> > > >         but configure could not find it. Use --with-boost to
> > > >         specify the location of the boost library and
> > > >         --with-boost-version to specify your version.
> > > >         On debian based systems, install libboost-thread-dev
> 
> I have no  FreeBSD, but I tried to compile hugin 0.6 on a Gentoo Linux and had
> exactly the same error message. 
> I reinstalled the boost with thread support ( in gentoo: with a "thread"
> useflag) and after that i was able to compile hugin.  
> 
> My version of boost:  1.33.1
> 
> I hope this infomation will help you.
> 
> Ciao
> niko

Around line 24545 in configure, we have:

if test `eval echo '${'$as_ac_Lib'}'` = yes; then
  BOOST_THREAD_LIB="-l$ax_lib"  link_thread="yes" break 5
else
  link_thread="no"
fi

changing this to:

if test `eval echo '${'$as_ac_Lib'}'` = yes; then
  BOOST_THREAD_LIB="-l$ax_lib"
  link_thread="yes"
  break 5
else
  link_thread="no"
fi

solved the problem for me.

Here's a trivial test that shows the problem:

#!/bin/sh
for i in a b c d ; do
  SOMETHING="that thing" SOMETHINGELSE=$i break
done
echo $SOMETHING
echo $SOMETHINGELSE

When run on FreeBSD 6.1, both SOMETHING and SOMETHINGELSE are not defined.
On OS-X (sorry, only other test platform), they are.  Moving the break to
its own line fixes bsd.

Cheers,
bri

Hi Bri,

> Around line 24545 in configure, we have:
> 
> if test `eval echo '${'$as_ac_Lib'}'` = yes; then
>   BOOST_THREAD_LIB="-l$ax_lib"  link_thread="yes" break 5
> else
>   link_thread="no"
> fi
> 
> changing this to:
> 
> if test `eval echo '${'$as_ac_Lib'}'` = yes; then
>   BOOST_THREAD_LIB="-l$ax_lib"
>   link_thread="yes"
>   break 5
> else
>   link_thread="no"
> fi
> 
> solved the problem for me.

Thanks a lot! I have just fixed that in the hugin CVS.

Btw. further hugin specific bugs/errors are best discussed at the hugin-ptx
list http://groups.google.com/group/hugin-ptx if they don't concern panotools.

ciao
  Pablo