On Tuesday, 24 April 2018 20:02:37 BST Walter Dnes wrote:
> On Tue, Apr 24, 2018 at 09:40:52AM +0100, Peter Humphrey wrote
>
> > Anyway, this all leaves unanswered the question whether getting the
> > -march setting right in a chroot matters to the operation of the
> > chroot itself, as distinct
On Monday, 23 April 2018 18:53:09 BST Walter Dnes wrote:
> https://en.wikipedia.org/wiki/Celeron
>
> > Celeron is a brand name given by Intel to a number of different
> > low-end IA-32 and x86-64 computer microprocessor models targeted
> > at budget personal computers.
>
> Looking at that
On Mon, Apr 23, 2018 at 04:23:18PM +0100, Peter Humphrey wrote
> Ah, that was it. My searching didn't turn that one up - thanks.
>
> $ gcc -c -Q -march=native --help=target | grep march=
> -march= silvermont
https://en.wikipedia.org/wiki/Celeron
> Celeron is a
On Monday, 23 April 2018 11:57:27 BST Mick wrote:
> 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
On Monday, 23 April 2018 11:57:12 BST Walter Dnes wrote:
> > 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,
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
> 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
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
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
On Sunday, 22 April 2018 10:21:16 BST Peter Humphrey wrote:
> On Sunday, 22 April 2018 09:39:23 BST Peter Humphrey wrote:
> > On Sunday, 22 April 2018 07:20:28 BST Jonathan Callen wrote:
> > > Generally, this would indicate a problem resolving DNS. This is
> > > normally caused by not having a
On Sunday, 22 April 2018 09:39:23 BST Peter Humphrey wrote:
> On Sunday, 22 April 2018 07:20:28 BST Jonathan Callen wrote:
> > Generally, this would indicate a problem resolving DNS. This is
> > normally caused by not having a correct /etc/resolv.conf inside the
> > chroot (it generally will need
On Sunday, 22 April 2018 07:20:28 BST Jonathan Callen wrote:
> Generally, this would indicate a problem resolving DNS. This is
> normally caused by not having a correct /etc/resolv.conf inside the
> chroot (it generally will need to be the same as the file outside the
> chroot).
Yes, I'd
12 matches
Mail list logo
