public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code?
Date: Sun, 22 Mar 2015 07:32:00 -0400	[thread overview]
Message-ID: <20150322113200.GA28858@waltdnes.org> (raw)
In-Reply-To: <CAJ0EP413Qp8LqN4zXjwUCLSkDWiJ1LDSB0U8C_Fbf69opp51Yg@mail.gmail.com>

On Sat, Mar 21, 2015 at 08:46:10AM -0400, Mike Gilbert wrote

> I should warn you against including all of those -mno-xxx flags. This
> has been known to break the build process for packages like chromium,
> which always wants to build with SSE4 support and toggles it off at
> runtime. Passing -mno-sse4.1 causes a build failure as it tries to use
> macros that are not defined.

  Weird.  The Gentoo wiki documents /etc/portage/package.env at...
https://wiki.gentoo.org/wiki/Knowledge_Base:Overriding_environment_variables_per_package
for handling special cases like this.  Not every package tests at
runtime.  Leaving sse4.1 enabled could result in other packages crashing
with illegal instructions.  I don't use chromium.  But if I did, I'd use
package.env to handle it as a special case.  Chromium is plain weird
anyways.  A web browser should not require udev.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


  parent reply	other threads:[~2015-03-22 11:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  1:56 [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code? Walter Dnes
2015-03-19  2:27 ` Fernando Rodriguez
2015-03-19  4:20   ` Walter Dnes
2015-03-19  5:12     ` Fernando Rodriguez
2015-03-21 12:46     ` Mike Gilbert
2015-03-21 19:52       ` Fernando Rodriguez
2015-03-22 14:03         ` Mike Gilbert
2015-03-22 14:05           ` Mike Gilbert
2015-03-23  0:56           ` Fernando Rodriguez
2015-03-23  1:25           ` Fernando Rodriguez
2015-03-24  1:51             ` Walter Dnes
2015-03-23 22:18               ` Mike Gilbert
2015-03-23 22:41                 ` Fernando Rodriguez
2015-03-23 22:48                   ` Mike Gilbert
2015-03-24  0:37                     ` Fernando Rodriguez
2015-03-24  6:06                   ` Walter Dnes
2015-03-24  7:17                 ` Walter Dnes
2015-03-24 17:18                   ` Mike Gilbert
2015-03-24 19:01                   ` Fernando Rodriguez
2015-03-25  2:01                     ` Walter Dnes
2015-03-25  5:20                     ` Walter Dnes
2015-03-25  6:44                       ` Walter Dnes
2015-03-24  0:26               ` Peter Humphrey
2015-03-22 11:32       ` Walter Dnes [this message]
2015-03-28 11:13 ` Frank Steinmetzger
2015-03-28 13:03   ` Walter Dnes

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=20150322113200.GA28858@waltdnes.org \
    --to=waltdnes@waltdnes.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