public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Can't fetch distfiles in chroot
Date: Mon, 23 Apr 2018 11:57:27 +0100	[thread overview]
Message-ID: <1868368.OlHHBdhxBY@dell_xps> (raw)
In-Reply-To: <1686478.OYGqcQaqzQ@peak>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

On Monday, 23 April 2018 10:52:57 BST Peter Humphrey wrote:
> On Sunday, 22 April 2018 12:13:53 BST Mick wrote:
> > On Sunday, 22 April 2018 10:21:16 BST Peter Humphrey wrote:
> > > That first thought was prompted by the instruction to "mount -o bind
> > > /lib/
> > > modules /foo/lib/modules" in this page:
> > > 
> > > https://wiki.gentoo.org/wiki/Project:X86/Chroot_Guide
> > 
> > I didn't do a detailed comparison, but you may want to take a look at the
> > Handbook, the chroot mounts appear to be different.
> 
> I think I've found the problem. It's in the -march setting, which of course
> has to be specific in the chroot, not "native." I had it set to
> "silvermont," but now I can't see why I did that. The target CPU is a
> celeron N3150, which according to an Intel site is "Products formerly
> Braswell" [1]. None of the Gentoo or GCC optimisation sites I could find
> even mention braswell, silvermont or model 76.

If you check 'man gcc' you will find "silvermont" is mentioned as a cpu_type 
you could set for march, but not the graphics core Braswell.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-04-23 10:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-22  5:13 [gentoo-user] Can't fetch distfiles in chroot Peter Humphrey
2018-04-22  6:20 ` [gentoo-user] " Jonathan Callen
2018-04-22  8:39   ` Peter Humphrey
2018-04-22  9:21     ` Peter Humphrey
2018-04-22 11:07       ` Peter Humphrey
2018-04-22 11:13       ` Mick
2018-04-23  9:52         ` Peter Humphrey
2018-04-23 10:57           ` Walter Dnes
2018-04-23 15:23             ` Peter Humphrey
2018-04-23 17:53               ` Walter Dnes
2018-04-24  8:40                 ` Peter Humphrey
2018-04-24 19:02                   ` Walter Dnes
2018-04-25  7:43                     ` Peter Humphrey
2018-04-23 10:57           ` Mick [this message]
2018-04-23 15:25             ` Peter Humphrey
2018-04-24  8:43 ` [gentoo-user] " Peter Humphrey
2018-04-26  7:59   ` Peter Humphrey
2018-04-26  8:07     ` Neil Bothwick
2018-04-26 10:11       ` Peter Humphrey
2018-04-26  8:12     ` Peter Humphrey
2018-04-27 10:21       ` Tom H

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=1868368.OlHHBdhxBY@dell_xps \
    --to=michaelkintzios@gmail.com \
    --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