public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE flags and static libs
Date: Sat, 08 Jun 2002 15:49:08 +0200	[thread overview]
Message-ID: <214270000.1023544148@krabat.ahsoftware> (raw)
In-Reply-To: <157640000.1023542200@krabat.ahsoftware>

Just as a hint for developers:

--On Samstag, Juni 08, 2002 15:16:40 +0200 Alexander Holler 
<holler@ahsoftware.de> wrote:

> 1. Building all static libs without march flags.
>
> 2. Introduce a USE flag i386static
> This could be used to build additional static libs with a postfix i386.
> E.g. libncurses.a and libncurses_i386.a.

This could be easily done replacing -march with -mcpu:

CFLAGS=`echo $CFLAGS | sed -e 's/-march/-mcpu/'`

The same applies to the CXXFLAGS.
According to the gcc docs, this leads to binaries which are something 
optimized for the specific cpu but are running on all cpus.

Alexander



  reply	other threads:[~2002-06-08 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08 13:16 [gentoo-dev] USE flags and static libs Alexander Holler
2002-06-08 13:49 ` Alexander Holler [this message]
2002-06-08 15:00 ` Alexander Gretencord

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=214270000.1023544148@krabat.ahsoftware \
    --to=holler@ahsoftware.de \
    --cc=gentoo-dev@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