From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@cvs.gentoo.org>
Subject: AW: [gentoo-dev] KDE 2.2 questions
Date: Mon Aug 20 00:18:01 2001 [thread overview]
Message-ID: <BLEMKJBINAFGJOKNKPIFIEEACBAA.sebastian@werner-productions.de> (raw)
In-Reply-To: <E15YaPI-00049M-00.2001-08-19-22-46-58@cmailg2.svr.pol.co.uk>
I think it's not enables - the prelinking. You need the program objprelink
and
must patch all objects with this. While this program does't support
many files at the commandline i would try with a small script extension
between
'make' and 'make install' in the kde ebuild files:
for obj in `find . -name "*.o"`; do
objprelink $obj
touch $obj
done
When ebuild executes make install, make will detect that the objects have
changed
and will relink all the files.
I like that we can enable/disable this with a USE-flag
Thanks,
Sebastian
-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@cvs.gentoo.org
[mailto:gentoo-dev-admin@cvs.gentoo.org]Im Auftrag von Viktor Lakics
Gesendet: Sonntag, 19. August 2001 23:42
An: gentoo-dev@cvs.gentoo.org
Betreff: [gentoo-dev] KDE 2.2 questions
Dear Gentoers,
I have just emerged KDE2.2 (kdebase and kdenetwork) and konqi does not know
about SSL. It says (at the config options) this module was not linked with
OpenSSL. I have openssl installed, KDE2.1.1 worked with it just fine. How
can I make KDE2.2 aware of my openssl?
Also, is the object-file prelinking enabled after installation? How can I
enable it? My "senior" machine needs some faster KDE program startup
badly...
Thanks in advance for any help...
Viktor
_______________________________________________
gentoo-dev mailing list
gentoo-dev@cvs.gentoo.org
http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-08-20 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 15:47 [gentoo-dev] KDE 2.2 questions Viktor Lakics
2001-08-20 0:18 ` Sebastian Werner [this message]
2001-08-20 10:15 ` 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=BLEMKJBINAFGJOKNKPIFIEEACBAA.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