public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Changing CFLAGS
Date: Sat, 28 Apr 2007 03:40:04 +0200	[thread overview]
Message-ID: <20070428014004.GA1617@zone.wonkology.org> (raw)

Hi there!

My motherboard or CPU just died, I am using a replacement system 
for a while. It's an Athlox-XP, while I had an AMD-64 before.
I did not use 64 bit mode, but I have -march=k8 in my CFLAGS, 
and get lots of illegal instructions. Seems I need to re-compile
everything with different CFLAGS, maybe -mcpu=k8 maybe this time 
as I am planning to re-activate the old system some time.

What would be the best way to do this? I thought about unpacking
a stage1 tarball, changing CFLAGS, calling bootstrap.sh and doing
an emerge -e world, but this would overwrite things in /etc and 
clutter my file system with more things I do not really want, 
like creating entries in /dev. I would rather like to keep the
current setup as it is.

I think that I saw a howto once about what to do in such a case,
but at that time I did not need it, and now I cannot find it.


BTW: What exactly are the benefits from using march instead of 
mcpu? Is there a noticeable difference in speed anyway? With mcpu 
I would not have the trouble I am having now...

	Alex
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2007-04-28  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28  1:40 Alex Schuster [this message]
2007-04-28  5:07 ` [gentoo-user] Changing CFLAGS Hemmann, Volker Armin
2007-04-28 14:04   ` [gentoo-user] " Alexander Skwar
2007-04-28 14:22     ` Hemmann, Volker Armin
2007-05-03 20:40   ` [gentoo-user] " Csányi András
2007-05-03 22:19     ` Ryan Sims
2007-05-04  6:11       ` Csányi András
2007-05-04  6:12         ` Csányi András

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=20070428014004.GA1617@zone.wonkology.org \
    --to=wonko@wonkology.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