From: Richard B. <ra...@xs...> - 2003-10-22 01:16:34
|
Got suse-9.0 and once again suse does not build gramps succesfully, this is the error I get: **** The python bindings for gconf (gnome-python2-gconf) could not be found. error: Bad exit status from /tmp/rpm-tmp.63219 (%build) RPM build errors: Bad exit status from /tmp/rpm-tmp.63219 (%build) Which is for the following configure check: echo "$as_me:$LINENO: checking Python bindings for gconf" >&5 echo $ECHO_N "checking Python bindings for gconf... $ECHO_C" >&6 cat > conftest.py <<EOF $pygtk_require try: import gconf out("YES") except ImportError: out("NO") EOF $PYTHON conftest.py By which project is the python gconf module/library provided? I assume that this one needs to be recompiled. I assume it is provided by the project/rpm python-gnome, which provides: /usr/lib/python2.3/site-packages/gtk-2.0/gnome/gconf.so I have the following python stuff installed: python-2.3-43 python-gnome-2.0.0-28 python-gtk-2.0.0-31 python-numeric-23.0-72 python-orbit-2.0.0-25 python-tk-2.3-43 python-devel-2.3-43 Now I edited configure to pass the python bindings for gconf check. The rest of configure passed without problems. Next, make of course now problems. Than I executed: make DESTDIR=/usr/tmp/GRAMPS install This works fine in itself, but gramps contains an incorrectly (hardcoded) defined prefix. I thinks that prefix should be prefix=${prefix} as well, just as exec_prefix.... richard@pilchard:/usr/tmp/GRAMPS> cat ./usr/local/bin/gramps #! /bin/sh # gramps.sh. Generated from gramps.sh.in by configure. <license skipped> # prefix=/usr/local <<<<==== exec_prefix=${prefix} Once I was able to launch gramps the result is this: richard@pilchard:/usr/tmp/GRAMPS> ./usr/local/bin/gramps Traceback (most recent call last): File "/usr/tmp/GRAMPS/usr/local/share/gramps/gramps.py", line 71, in ? import gramps_main File "/var/tmp/GRAMPS/usr/local/share/gramps/gramps_main.py", line 53, in ? import PedView File "/var/tmp/GRAMPS/usr/local/share/gramps/PedView.py", line 40, in ? import GrampsCfg File "/var/tmp/GRAMPS/usr/local/share/gramps/GrampsCfg.py", line 39, in ? import gconf ImportError: No module named gconf Now, that I recognize. Does someone has a suggestion to get this resolved? -- Richard Bos Without a home the journey is endless |
From: <dpe...@si...> - 2003-10-22 02:28:32
|
On Tue, 21 Oct 2003, Richard Bos had this to say: >Got suse-9.0 and once again suse does not build gramps succesfully, this is >the error I get: >**** The python bindings for gconf (gnome-python2-gconf) could not be found. Hi Richard, I can't really comment on the missing python-gnome bindings, but will try to address your other issues below... >Next, make of course now problems. >Than I executed: make DESTDIR=/usr/tmp/GRAMPS install > >This works fine in itself, but gramps contains an incorrectly (hardcoded) >defined prefix. I thinks that prefix should be prefix=${prefix} as well, >just as exec_prefix.... Nope. Gramps does not hardcode "prefix". You can verify this for yourself by looking at the gramps.sh.in file. prefix and exec_prefix are defined by the @...@ macro substitution which is performed when you run configure. In most setups, configure will default to setting $prefix to /usr/local. This can be overridden by specifying the --prefix= flag to configure's invocation (e.g. "./configure --prefix=/usr/tmp/GRAMPS"). Using "prefix=${prefix}" in the gramps.sh script would be equivalent to using "prefix=" since at that point $prefix is not defined. The point is that when you run "configure", you need to specify where you want and expect gramps to be installed. Of course the UNIX way is that programs compiled/installed by users or after-the-fact, go under the /usr/local/tree, hence the default behavior of configure... >richard@pilchard:/usr/tmp/GRAMPS> cat ./usr/local/bin/gramps >#! /bin/sh ># gramps.sh. Generated from gramps.sh.in by configure. ><license skipped> ># > >prefix=/usr/local <<<<==== >exec_prefix=${prefix} Right. As it should be. Generally, configure set the prefix to /usr/local and the executables are in the same tree. >Once I was able to launch gramps the result is this: > >richard@pilchard:/usr/tmp/GRAMPS> ./usr/local/bin/gramps > >Traceback (most recent call last): > File "/usr/tmp/GRAMPS/usr/local/share/gramps/gramps.py", line 71, in ? > import gramps_main > File "/var/tmp/GRAMPS/usr/local/share/gramps/gramps_main.py", line 53, in ? > import PedView > File "/var/tmp/GRAMPS/usr/local/share/gramps/PedView.py", line 40, in ? > import GrampsCfg > File "/var/tmp/GRAMPS/usr/local/share/gramps/GrampsCfg.py", line 39, in ? > import gconf >ImportError: No module named gconf > >Now, that I recognize. Does someone has a suggestion to get this resolved? I'm wondering if your PYTHONPATH or PYTHONHOME environment is not set properly to the gconf module. Two things to check: 1) Execute 'locate gconfmodule.so' to ensure that it really is on your system. 2) From an interactive python shell, just type 'import gconf' to see if you can load it. It seems as though this should be supplied by python-gnome-1.99.14 or higher... Hope this helps, -Don -- ________________________________________________ Donald A. Peterson | dpe...@si... Ph.D. Research Associate | Dept. of Chemistry | PH: (541) 737-7079 Oregon St. University | FAX: (541) 737-0480 ------------------------------------------------ |
From: Richard B. <ra...@xs...> - 2003-10-22 21:24:13
|
Hello Don(s), Op woensdag 22 oktober 2003 04:26, schreef dpe...@si...: > On Tue, 21 Oct 2003, Richard Bos had this to say: > >Got suse-9.0 and once again suse does not build gramps succesfully, this > > is the error I get: > >**** The python bindings for gconf (gnome-python2-gconf) could not be > > found. > > Hi Richard, > > I can't really comment on the missing python-gnome bindings, but will try > to address your other issues below... > > >Next, make of course now problems. > >Than I executed: make DESTDIR=/usr/tmp/GRAMPS install > > > >This works fine in itself, but gramps contains an incorrectly (hardcoded) > >defined prefix. I thinks that prefix should be prefix=${prefix} as well, > >just as exec_prefix.... > > Nope. Gramps does not hardcode "prefix". You can verify this for > yourself by looking at the gramps.sh.in file. prefix and exec_prefix are > defined by the @...@ macro substitution which is performed when you > run configure. In most setups, configure will default to setting $prefix > to /usr/local. This can be overridden by specifying the --prefix= flag to > configure's invocation (e.g. "./configure --prefix=/usr/tmp/GRAMPS"). > > Using "prefix=${prefix}" in the gramps.sh script would be equivalent to > using "prefix=" since at that point $prefix is not defined. The point is > that when you run "configure", you need to specify where you want and > expect gramps to be installed. Of course the UNIX way is that programs > compiled/installed by users or after-the-fact, go under the > /usr/local/tree, hence the default behavior of configure... > > >richard@pilchard:/usr/tmp/GRAMPS> cat ./usr/local/bin/gramps > >#! /bin/sh > ># gramps.sh. Generated from gramps.sh.in by configure. > ><license skipped> > ># > > > >prefix=/usr/local <<<<==== > >exec_prefix=${prefix} > > Right. As it should be. Generally, configure set the prefix to > /usr/local and the executables are in the same tree. Okay, --prefix should do it. > >Once I was able to launch gramps the result is this: > > > >richard@pilchard:/usr/tmp/GRAMPS> ./usr/local/bin/gramps > > > >Traceback (most recent call last): > > File "/usr/tmp/GRAMPS/usr/local/share/gramps/gramps.py", line 71, in ? > > import gramps_main > > File "/var/tmp/GRAMPS/usr/local/share/gramps/gramps_main.py", line 53, > > in ? import PedView > > File "/var/tmp/GRAMPS/usr/local/share/gramps/PedView.py", line 40, in ? > > import GrampsCfg > > File "/var/tmp/GRAMPS/usr/local/share/gramps/GrampsCfg.py", line 39, in > > ? import gconf > >ImportError: No module named gconf > > > >Now, that I recognize. Does someone has a suggestion to get this > > resolved? > > I'm wondering if your PYTHONPATH or PYTHONHOME environment is not set > properly to the > gconf module. Two things to check: > > 1) Execute 'locate gconfmodule.so' to ensure that it really is on your It's not on the system... > system. 2) From an interactive python shell, just type 'import gconf' to > see if you can load it. This would be redundant see above (twice). > It seems as though this should be supplied by python-gnome-1.99.14 or > higher... I installed the python-gnome-2.0.0 that comes with suse. This pkg provides python-gnome 1.4 and 2.0. The rpmbuild fails in the 1.4 directory. I went to the unpacked BUILD/gnome-python-2.0 and started ./configure and make there. The build completes succesfully. After that I installed the products with make DESTDIR=/usr/tmp/PYTHON and did a find in that directory, there is no gconfmodule :( In the gconf build dir there is: gnome-python-2.0.0/gconf> find . -name "*.lo" ./gconf_la-gconf.lo ./gconf_la-gconf-fixes.lo ./gconf_la-gconfmodule.lo Is this as expected, should there be more? Should these products be converted into gconfmodule.so? I hope you have a clue. -- Richard Bos Without a home the journey is endless |
From: <dpe...@si...> - 2003-10-23 01:28:31
|
On Wed, 22 Oct 2003, Richard Bos had this to say: >> >ImportError: No module named gconf >> > >> >Now, that I recognize. Does someone has a suggestion to get this >> > resolved? >> >> I'm wondering if your PYTHONPATH or PYTHONHOME environment is not set >> properly to the >> gconf module. Two things to check: >> >> 1) Execute 'locate gconfmodule.so' to ensure that it really is on your > >It's not on the system... > >I installed the python-gnome-2.0.0 that comes with suse. This pkg provides >python-gnome 1.4 and 2.0. The rpmbuild fails in the 1.4 directory. I went >to the unpacked BUILD/gnome-python-2.0 and started ./configure and make >there. The build completes succesfully. After that I installed the products >with make DESTDIR=/usr/tmp/PYTHON and did a find in that directory, there is >no gconfmodule :( > >In the gconf build dir there is: >gnome-python-2.0.0/gconf> find . -name "*.lo" >./gconf_la-gconf.lo >./gconf_la-gconf-fixes.lo >./gconf_la-gconfmodule.lo > >Is this as expected, should there be more? Should these products be >converted into gconfmodule.so? > >I hope you have a clue. Well, I don't have much of one, but this is starting to look like a packaging error. I just went to rpmfind.net and searched for python-gnome for a suse system. It returns several matches, all dealing with SuSE 8.2 updates. The packages are all version 1.99.14-73, not 2.0.0. For fun, I downloaded the i586 rpm: 4:08pm> rpm -qpl python-gnome-1.99.14-73.i586.rpm |grep gconf warning: python-gnome-1.99.14-73.i586.rpm: V3 DSA signature: NOKEY, key ID 9c800aca /usr/lib/python2.2/site-packages/gtk-2.0/gconfmodule.la /usr/lib/python2.2/site-packages/gtk-2.0/gconfmodule.so /usr/share/doc/packages/python-gnome/gnome-2.0/examples/gconf /usr/share/doc/packages/python-gnome/gnome-2.0/examples/gconf/basic-gconf-app.py /usr/share/doc/packages/python-gnome/gnome-2.0/examples/gconf/simple-controller.py /usr/share/doc/packages/python-gnome/gnome-2.0/examples/gconf/simple-view.py Of course, this was from a binary rpm rather than a source rpm, but it seems that at one time the SuSE packages had the right stuff. I couldn't find any references to python-gnome-2.0.0. Even my RH9 dist. only has version 1.99.14 on it.<shrug> I know this doesn't help much, but maybe adds a little clue to the mystery? Cheers, -Don -- ________________________________________________ Donald A. Peterson | dpe...@si... Ph.D. Research Associate | Dept. of Chemistry | PH: (541) 737-7079 Oregon St. University | FAX: (541) 737-0480 ------------------------------------------------ |
From: Don A. <dal...@us...> - 2003-10-23 04:40:18
|
This library is typically provided by the gnome-python-gconf package. This can be built from the gnome-python.tar.gz source file. I would imagine that it would come with the python-gnome packages. Are these included with the SuSE 9 distribution? Don On Tue, 2003-10-21 at 15:15, Richard Bos wrote: > Got suse-9.0 and once again suse does not build gramps succesfully, this = is=20 > the error I get: > **** The python bindings for gconf (gnome-python2-gconf) could not be fou= nd. > error: Bad exit status from /tmp/rpm-tmp.63219 (%build) >=20 >=20 > RPM build errors: > Bad exit status from /tmp/rpm-tmp.63219 (%build) >=20 > Which is for the following configure check: >=20 > echo "$as_me:$LINENO: checking Python bindings for gconf" >&5 > echo $ECHO_N "checking Python bindings for gconf... $ECHO_C" >&6 > cat > conftest.py <<EOF > $pygtk_require > try: > import gconf > out("YES") > except ImportError: > out("NO") > EOF > $PYTHON conftest.py >=20 > By which project is the python gconf module/library provided? I assume t= hat=20 > this one needs to be recompiled. >=20 > I assume it is provided by the project/rpm python-gnome, which provides: > /usr/lib/python2.3/site-packages/gtk-2.0/gnome/gconf.so >=20 > I have the following python stuff installed: > python-2.3-43 > python-gnome-2.0.0-28 > python-gtk-2.0.0-31 > python-numeric-23.0-72 > python-orbit-2.0.0-25 > python-tk-2.3-43 > python-devel-2.3-43 >=20 > Now I edited configure to pass the python bindings for gconf check. The = rest=20 > of configure passed without problems. >=20 > Next, make of course now problems. > Than I executed: make DESTDIR=3D/usr/tmp/GRAMPS install >=20 > This works fine in itself, but gramps contains an incorrectly (hardcoded)= =20 > defined prefix. I thinks that prefix should be prefix=3D${prefix} as wel= l,=20 > just as exec_prefix.... >=20 > richard@pilchard:/usr/tmp/GRAMPS> cat ./usr/local/bin/gramps > #! /bin/sh > # gramps.sh. Generated from gramps.sh.in by configure. > <license skipped> > # >=20 > prefix=3D/usr/local <<<<=3D=3D=3D=3D > exec_prefix=3D${prefix} >=20 >=20 > Once I was able to launch gramps the result is this: >=20 > richard@pilchard:/usr/tmp/GRAMPS> ./usr/local/bin/gramps >=20 > Traceback (most recent call last): > File "/usr/tmp/GRAMPS/usr/local/share/gramps/gramps.py", line 71, in ? > import gramps_main > File "/var/tmp/GRAMPS/usr/local/share/gramps/gramps_main.py", line 53, = in ? > import PedView > File "/var/tmp/GRAMPS/usr/local/share/gramps/PedView.py", line 40, in ? > import GrampsCfg > File "/var/tmp/GRAMPS/usr/local/share/gramps/GrampsCfg.py", line 39, in= ? > import gconf > ImportError: No module named gconf >=20 > Now, that I recognize. Does someone has a suggestion to get this resolv= ed? --=20 Don Allingham <dal...@us...> GRAMPS OpenSource Genealogy |