Instaling gimmie from source in intrepid

PClOStinspace · 06-27-2009, 08:59 AM

I have just downloaded 'Gimmie' as I fancy trying it out, I am encountering difficulties instaling. Below is where I am at, and I am now out of my depth!!

Code:

gregg@kubuntu:~/Desktop/gimmie-0.2.8$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking for intltool >= 0.33... 0.35.5 found
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking for iconv... /usr/bin/iconv
checking for msgfmt... /usr/bin/msgfmt
checking for msgmerge... /usr/bin/msgmerge
checking for xgettext... /usr/bin/xgettext
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... ar ca cs da de dz el en_GB es fi fr gl hu ja lv mk nb oc pt_BR ru sv vi zh_CN
checking for gconftool-2... /usr/bin/gconftool-2
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for python... /usr/bin/python
checking for python version... 2.5
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.5/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages
checking for headers required to compile python extensions... found
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GIMMIE... configure: error: Package requirements (gtk+-2.0 >= 2.6
pygtk-2.0 >= 2.6
libgnome-menu >= 2.18) were not met:

No package 'pygtk-2.0' found
No package 'libgnome-menu' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GIMMIE_CFLAGS
and GIMMIE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

I have tried to find pygtk-2.0 and libgnome-menu and it looks like they are installed according to synaptic. I am not experienced in cli so I am not sure what to do now!

PClOStinspace · 06-27-2009, 10:35 AM

Just found:-

http://www.linuxquestions.org/questi...gimmie-731995/

I'm giving it a whirl now, sorry to be a time waster!!

jdkaye · 06-27-2009, 10:41 AM

Any particular reason why you're compiling gimmie from source rather than just installing the package? If you're running kubuntu from the command line do:

Code:

sudo aptitude update

and then

Code:

sudo aptitude install gimmie

and that's it.
If your'e trying to gain experience in the art of compiling, then that's fine and ignore the above.
cheers,
jdk

PClOStinspace · 06-27-2009, 10:44 AM

I'm also having to use synaptic to install some python dev stuff, I'll let you know what if it works!

PClOStinspace · 06-27-2009, 10:48 AM

Quote:

Originally Posted by jdkaye

Any particular reason why you're compiling gimmie from source rather than just installing the package? If you're running kubuntu from the command line do:

Code:

sudo aptitude update

and then

Code:

sudo aptitude install gimmie

and that's it.
If your'e trying to gain experience in the art of compiling, then that's fine and ignore the above.
cheers,
jdk

We must have been typing at the same time!!

I was not trying to gain experience, although I am glad of it, I simply hadn't realised I could get it that simply with aptitude. I am going to persevere now as I am so far through!

Thanks for letting me know, when it all goes wrong in ten minutes, I may plump for the easy option

jdkaye · 06-27-2009, 11:40 AM

Quote:

Originally Posted by PClOStinspace

We must have been typing at the same time!!

I was not trying to gain experience, although I am glad of it, I simply hadn't realised I could get it that simply with aptitude. I am going to persevere now as I am so far through!

Thanks for letting me know, when it all goes wrong in ten minutes, I may plump for the easy option

That's the spirit! Good luck to you.
cheers,
jdk

PClOStinspace · 06-28-2009, 02:50 AM

I did have to install some python bit n bobs, I wont post what as they were fairly obvious when I went into my PM.

I also installed the gimmie screenlet, this was less succesful. it ran the first time, but when I re-booted, it wont run anymore, I found the .py file and tried executing that, no joy. any tips??

jdkaye · 06-28-2009, 03:02 AM

I'm not at all familiar with gimmie but can you run it from a command line? There's often information to be gleaned if you run it that way. You could also run it from a debugger like gdb and maybe that will give even more info.

Other than that you'll have to wait from someone who knows something about gimmie.
Cheers,
jdk

PClOStinspace · 06-28-2009, 03:16 AM

Quote:

Originally Posted by jdkaye

I'm not at all familiar with gimmie but can you run it from a command line? There's often information to be gleaned if you run it that way. You could also run it from a debugger like gdb and maybe that will give even more info.

Other than that you'll have to wait from someone who knows something about gimmie.
Cheers,
jdk

How would I run "GimmieScreenlet.py" from thr command line? I am in it's directory in a terminal now.

Thanks.

jdkaye · 06-28-2009, 04:04 AM

Do you invoke gimmie like this?

Code:

python GimmieScreenlet.py

jdk

PClOStinspace · 06-28-2009, 05:07 AM

Quote:

Originally Posted by jdkaye

Do you invoke gimmie like this?

Code:

python GimmieScreenlet.py

jdk

Tried and this happened:-

Code:

gregg@kubuntu:~/.screenlets/Gimmie$ GimmieScreenlet.py
bash: GimmieScreenlet.py: command not found           
gregg@kubuntu:~/.screenlets/Gimmie$ python GimmieScreenlet.py
 !!! net.sf.gaim.GaimService D-BUS service not available.    
 !!! Error parsing ~/.gaim/accounts.xml: No such file or directory
 !!! im.pidgin.purple.PurpleService D-BUS service not available.  
Traceback (most recent call last):                                
  File "GimmieScreenlet.py", line 568, in <module>                
    screenlets.session.create_session(GimmieScreenlet)            
  File "/usr/lib/python2.5/site-packages/screenlets/session.py", line 471, in create_session                                                    
    session = ScreenletSession(classobj, backend_type=backend)          
  File "/usr/lib/python2.5/site-packages/screenlets/session.py", line 85, in __init__                                                           
    self.path = BaseDirectory.save_config_path('Screenlets/' + p)       
  File "/var/lib/python-support/python2.5/xdg/BaseDirectory.py", line 59, in save_config_path
    os.makedirs(path, 0700)
  File "/usr/lib/python2.5/os.py", line 171, in makedirs
    mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/home/gregg/.config/Screenlets/Gimmie/default/'

Again, out of my depth!!!!

jdkaye · 06-28-2009, 05:14 AM

I'd suggest you get the pre-compiled version or else learn python programming.

There appears to be a huge load of dev packages you'd need to install in order to compile this.
Cheers,
jdk

PClOStinspace · 06-28-2009, 05:20 AM

Quote:

Originally Posted by jdkaye

I'd suggest you get the pre-compiled version or else learn python programming.

There appears to be a huge load of dev packages you'd need to install in order to compile this.
Cheers,
jdk

AFAIK there is no precomp' version of the screenlet!! If I use my PM to install all the python dev packages I can find, is it likely to cause me other issues?

jdkaye · 06-28-2009, 07:30 AM

Quote:

Originally Posted by PClOStinspace

AFAIK there is no precomp' version of the screenlet!! If I use my PM to install all the python dev packages I can find, is it likely to cause me other issues?

You're wrong. There is. At least Debian has it which should mean that Buntu has it too. Check out

Code:

aptitude search gimmie

and you should find it.
cheers,
jdk

PClOStinspace · 06-28-2009, 07:41 AM

Quote:

Originally Posted by jdkaye

You're wrong. There is. At least Debian has it which should mean that Buntu has it too. Check out

Code:

aptitude search gimmie

and you should find it.
cheers,
jdk

Gimmie is the main app, I have that working, this is what I compiled to start off with. The GimmieScreenlet is a separate entity, thats what I can't get to work now and only comes as a .tar.gz from:-

http://gnome-look.org/content/show.p...?content=79792

I think I may have been confusing this point!

Also:-

Code:

gregg@kubuntu:~$ aptitude search gimmie
gregg@kubuntu:~$

No joy there anyways!!