public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gold is Heavy <aeoo@garbled.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] merging gaim was even worse than pan
Date: Wed Oct 10 13:06:01 2001	[thread overview]
Message-ID: <auto-000008682936@front2.mail.megapathdsl.net> (raw)

Hi Gentoo Hackers,

I've read Martin's post, and I am going to follow Martin's suggestions later.

But before I followed Martin's suggestions, I wanted to try to emerge one 
more thing that I really can't live without -- gaim.  The reason for this is 
simple: I feel I should be able to emerge gnome apps without actually 
emerging gnome itself.  There might be technical reasons why this could be 
impossible, but I am 95% sure that it should be possible to compile and use 
gaim without gnome.  So I did:

emerge net-im/gaim

And what followed was pretty uneventful, except the following bits:

---
config.status: creating po/Makefile

gaim 0.45

Allow Multiple Connections.. : yes
Build Protocol Plugins...... : yes
Protocols to link statically : oscar toc

Build with GNOME bits....... : yes
Use GdkPixbuf for Icons..... : yes
Build as GNOME applet....... : yes

Build with Plugin support... : yes
Build with Perl support..... : yes

Use XScreenSaver Extension.. : yes

Build with ESD.............. : yes
Build with NAS.............. : no
Build with ArtsC............ : yes

Print debugging messages.... : no

Gaim will be installed in /usr/bin.

configure complete, now type 'make'
---

Ok, here we see that config is totally wrong.  I don't want 'GNOME bits' and 
I don't want to build gaim as 'GNOME applet' as I have no intention of 
running GNOME (at least not soon).

So, it finishes compiling without any errors, and now I have useless 
/usr/bin/gaim_applet.  Obviously if I try to run it, it gives me a corba 
error, and although I am sure it's pointless, I will cut and paste the error 
for the sake of completeness:

** WARNING **: file applet-widget.c: line 955: Corba Exception: type = 2 exid 
= IDL:CORBA/COMM_FAILURE:1.0

For the sake of completeness, here is my USE variable, as defined in 
/etc/make.conf:

USE="slang readline gpm berkdb gdbm tcpd pam libwww ssl
    lm_sensors lvm pcmcia-cs alsa
    nls mmx mitshm
    esd lcms gif sdl vorbis ogg
    gnome gtk X qt kde motif opengl mozilla
    3dnow perl python tcltk java guile ruby mysql postgres ldap odbc
    ggi fbcon svga tex bonobo nas qtmt aalib oss arts libg++"

How I ended up with these USE flags is very simple.  I simply edited the 
default /etc/make.conf, and in addition to the USE flags already defined 
there, I have added every single flag from the "Other stable USE flags" 
section.

If my USE flags are wrong, it may be a good idea to either change the rc6 
docs, or provide a better default /etc/make.conf, or maybe both?

Offtopic: I just noticed something else, KMail fails to invoke ispell.  
Weird.  ispell is there and it is in my PATH.  I did start KMail from KDE 
application launcher instead of my shell, maybe that's the problem?

--Leo



             reply	other threads:[~2001-10-10 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 13:06 Gold is Heavy [this message]
2001-10-10 13:13 ` [gentoo-dev] merging gaim was even worse than pan Mikael Hallendal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=auto-000008682936@front2.mail.megapathdsl.net \
    --to=aeoo@garbled.org \
    --cc=gentoo-dev@cvs.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox