From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Locate and Fix .text Relocations (TEXTRELs)
Date: Fri, 14 Jul 2006 01:30:49 -0700 [thread overview]
Message-ID: <7573e9640607140130x4bd66f65l2a95078da747df5b@mail.gmail.com> (raw)
In-Reply-To: <20060714095741.7b36081c@lx-arnau.pic.es>
On 7/14/06, Arnau Bria <arnau@emergetux.net> wrote:
> CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -mtune=i686"
> CXXFLAGS="-O2 -mcpu=i686 -pipe"
Hrm, these are really not sane. -march is telling gcc to build C code
that will only run on a p4, and then you have -mtune specifying to run
on everything back to a pentium-II. I *think* -march takes precedence
here....
But for C++ code, you are specifying that should run on any P-II. So
C and C++ code is being compiled in very different ways on your
system. This is bad. I have no idea whether these are causing your
problems with akregator or not however...
BTW, the TEXTREL messages are directly attributable to your CXXFLAGS.
I built akregator with the same flags, and get the same messages.
So what I recommend you set in /etc/make.conf is:
CFLAGS="-march=pentium4 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
Then re-merge akregator. If you still have trouble, try renaming
~/.kde3.5 to ~/.kde3.5.old and start it. If that works then some
akregator configuration in .kde3.5.old is responsible.
Finally, may want to recompile your entire system with the fixed
compiler flags. This can usually be done with an "emerge -e world",
but this will take a long time! You can also grep the CFLAGS/CXXFLAGS
files in the /var/db/pkg/ database to see what packages you merged
with particular flags. For example: "grep -r --include=CXXFLAGS --
-mcpu=i686 /var/db/pkg/".
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-14 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 7:43 [gentoo-user] Locate and Fix .text Relocations (TEXTRELs) Arnau Bria
2006-07-13 9:22 ` Arnau Bria
2006-07-13 18:12 ` Richard Fish
2006-07-14 7:57 ` Arnau Bria
2006-07-14 8:30 ` Richard Fish [this message]
2006-07-14 9:18 ` Arnau Bria
2006-07-14 11:03 ` Graham Murray
2006-07-14 16:43 ` Richard Fish
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=7573e9640607140130x4bd66f65l2a95078da747df5b@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@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