public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@cvs.gentoo.org>
Subject: AW: [Re: [gentoo-dev] https protocol is not supported in KDE2.2?!]
Date: Tue Sep 11 00:42:01 2001	[thread overview]
Message-ID: <BLEMKJBINAFGJOKNKPIFKEKBCBAA.sebastian@werner-productions.de> (raw)
In-Reply-To: <200109101806.AXC92939@balder.inter.net.il>

Hello,

i was the guy how told you the LD_BIND_NOW problem. ;-)
Now i used gcc-3.01 to compile kde-2.2 with objprelink. It works with all
features... AA, ALSA everything. I use this flags:

"-march=i686 -mcpu=i686 -O3 -pipe"

I have send the ebuild for gcc-3.0.1
to the build list one week ago.

Sebastian


-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@cvs.gentoo.org
[mailto:gentoo-dev-admin@cvs.gentoo.org]Im Auftrag von Dan Armak
Gesendet: Montag, 10. September 2001 20:06
An: gentoo-dev@cvs.gentoo.org
Betreff: Re: [Re: [gentoo-dev] https protocol is not supported in
KDE2.2?!]


Hm. No immediate idea. I know my way around kde, but not around openssl so
much. I don't have time to look into this until tomorrow. Does anyone else
know what lib is supposed to provide -lRSAglue? Checking should be easy
enough, but I really have to go.

--

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

_______________________________________________
gentoo-dev mailing list
gentoo-dev@cvs.gentoo.org
http://cvs.gentoo.org/mailman/listinfo/gentoo-dev




      reply	other threads:[~2001-09-11  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10  5:48 [Re: [gentoo-dev] https protocol is not supported in KDE2.2?!] Viktor Lakics
2001-09-10 11:12 ` Dan Armak
2001-09-10 11:47   ` Viktor Lakics
2001-09-10 12:08     ` Dan Armak
2001-09-11  0:42       ` Sebastian Werner [this message]

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=BLEMKJBINAFGJOKNKPIFKEKBCBAA.sebastian@werner-productions.de \
    --to=sebastian@werner-productions.de \
    --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