From: Viktor Lakics <lakicsv@usa.net>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] https protocol is not supported in KDE2.2?!
Date: Mon Sep 10 11:07:02 2001 [thread overview]
Message-ID: <E15gUVM-0000bT-00.2001-09-10-18-05-53@cmailg6.svr.pol.co.uk> (raw)
In-Reply-To: <200109100535.AXC69520@freya.inter.net.il>
On Monday 10 September 2001 6:35 am, you wrote:
On Sunday 09 September 2001 22:27, you wrote:
> Hm, look in /var/tmp/portage/kdebase-2.2/work/kdebase2.2/config.log
> for messages about ssl/openssl. See what reason it gives for not compiling
> against the openssl libs. It may be that portage deleted your temp dir
> after merging, in which case you'll have to ebuild unpack/compile to get a
> temp dir again. You can set MAINTAINER in /etc/make.conf to avoid that.
Hi Dan, I have set MAINTAINER=yes, then remerged kdebase again, there is no
/var/tmp/portage/.... dir... /var/tmp exists, but it is empty. What now?!
In addition, my old problem came back after remerging kdebase2.2, namely AA
is only showing up in certain apps and not in the k menu. I know that this is
my old problem with KDE2.1.1, because if I change LD_BIND_NOW=true, then AA
is OK again...
Strange...
> > BTW, will we have kde2.2 precompiled binaries in RC6?
>
> As soon as all kde2.2/rc6 problems are resolved, we should. It'll probably
> be kde 2.2.1 (to be released Sep 17) by that time, which should solve some
> problems on its own.
next prev parent reply other threads:[~2001-09-10 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 11:11 [gentoo-dev] https protocol is not supported in KDE2.2?! Viktor Lakics
2001-09-09 13:01 ` Dan Armak
2001-09-09 13:28 ` Viktor Lakics
2001-09-09 23:38 ` Dan Armak
2001-09-10 1:07 ` Viktor Lakics
2001-09-10 3:47 ` Dan Armak
2001-09-10 11:07 ` Viktor Lakics [this message]
2001-09-10 11:41 ` Dan Armak
2001-09-10 11:58 ` [gentoo-dev] AA pointer problem and solution in KDE2.2 Viktor Lakics
2001-09-10 12:04 ` Dan Armak
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=E15gUVM-0000bT-00.2001-09-10-18-05-53@cmailg6.svr.pol.co.uk \
--to=lakicsv@usa.net \
--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