From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?
Date: Sat, 23 Sep 2006 21:00:31 +0000 (UTC) [thread overview]
Message-ID: <ef479f$rrs$5@sea.gmane.org> (raw)
In-Reply-To: 976cb44f0609230255s14bcc37dj36d53f90cbf765bc@mail.gmail.com
"Greg Bur" <greg.bur@gmail.com> posted
976cb44f0609230255s14bcc37dj36d53f90cbf765bc@mail.gmail.com, excerpted
below, on Sat, 23 Sep 2006 05:55:59 -0400:
> I put my workstation through its paces last weekend using Duncan's flags
> and so far I've only run across one package that gave me problems and that
> was Evolution. It didn't like the LDFLAGS="-Wl,-z,now"
That's reasonable, since I don't use Evolution. (I use kmail for mail,
pan for news, and don't need Evolution's other features.)
You may wish to file a bug on that, altho I can't say you'll get a good
reception. See my related bug on modular-X:
http://bugs.gentoo.org/show_bug.cgi?id=116698
If evolution has anything setuid, as was the case with xorg, it may help,
since portage's handling of that was one thing that eventually turned the
above bug toward satisfactory resolution. I have no idea whether
evolution has anything setuid or not.
As for that ldflag, it's not major, more a personal preference. In most
cases, what it does is force library resolution and function loading at
load time instead of waiting until the functionality is required in some
cases. This results in a slightly longer load time, particularly shortly
after a reboot when nothing's yet in cache or loaded by other apps, and
slightly higher memory usage as well. That's the negatives, along with
the occasional app that has problems with it. The positives are that if the
library isn't found, you know about it at load time instead of possibly
having the app crash later when it tries to load the functions, a bit more
responsiveness after load the first time those functions are used (when
the system would otherwise be loading the library and linking in the
functions on demand), and a bit better security.
All in all, as I said, it's a personal preference. I don't specifically
recommend it as an optimization, and in fact, for those with less than a
gig of memory (as well as those who don't want the occasional hassle with
an app allergic to the setting), I'd tend to recommend NOT using it.
As for LDFLAGS in general, I've mentioned previously that I'm looking for
more documentation on them. There's some others I've seen in bug
reports or mentioned in passing that look interesting, but I simply don't
/begin/ to know enough about them to even /consider/ using them at this
point. Until that changes, I leave well enough alone.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-23 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 19:35 [gentoo-amd64] SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone? Mark Knecht
2006-09-22 23:42 ` [gentoo-amd64] " Duncan
2006-09-23 0:08 ` Mark Knecht
2006-09-23 8:28 ` Christoph Mende
2006-09-23 9:55 ` Greg Bur
2006-09-23 10:03 ` Mark Knecht
2006-09-23 10:16 ` Greg Bur
2006-09-23 10:49 ` Peter Humphrey
2006-09-23 17:40 ` Mark Knecht
2006-09-23 21:00 ` Duncan [this message]
2006-09-25 20:25 ` Sergio Polini
2006-09-25 20:55 ` Piotr Pruszczak
2006-10-08 18:44 ` Sergio Polini
2006-10-08 18:47 ` Peter Davoust
2006-09-26 1:09 ` Mark Knecht
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='ef479f$rrs$5@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.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