public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Machine recommendations?
Date: Thu, 12 Mar 2015 02:34:27 +0000 (UTC)	[thread overview]
Message-ID: <pan$841f8$95f26381$6a3e8680$7af7cf1a@cox.net> (raw)
In-Reply-To: 538babce70114f31b62855ce8c2d0cca@junc.eu

Benny Pedersen posted on Thu, 12 Mar 2015 00:03:34 +0100 as excerpted:

> Duncan skrev den 2015-03-11 23:44:
> 
>> But someone else here may know about something I've missed.  Asking
>> can't hurt! =:^)
> 
> raspberry-pi 2 ?

That fails the amd64-based-so-I-can-build-once-deploy-several 
requirement. =:^(  Which was pretty much the whole point of the thread 
for me, since I already know from experience, that even 32-bit x86-only 
doesn't get kept updated here, because it's too much hassle to 90% 
duplicate the same builds for it as for the main amd64 machine.

IOW, I already tried that solution and it won't work, for me. =:^(


But, thanks for the reply anyway.  It's very possible it'll help someone 
else with a somewhat different problem, think outside the x86/amd64 box 
far enough to have a cheap and hopefully effective for his problem, fix. 
=:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2015-03-12  2:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 22:44 [gentoo-amd64] Machine recommendations? Duncan
2015-03-11 23:03 ` Benny Pedersen
2015-03-12  2:34   ` Duncan [this message]
2015-03-13 20:30 ` Thanasis
2015-03-14 11:43   ` [gentoo-amd64] " Duncan
2015-03-14 12:10     ` Rich Freeman
2015-03-15  4:19       ` Duncan
2015-03-14 12:35     ` Thanasis
2015-03-15  6:14       ` Duncan
2015-03-15 11:53         ` Thanasis
2015-03-15 19:08           ` Leonid Eremin
2015-03-15 19:44             ` Thanasis
2015-03-16  6:31               ` Duncan
2015-03-16 20:37                 ` Thanasis
2015-03-17  3:11                   ` Duncan
2015-03-17 12:21                     ` Mark Knecht
2015-03-17 21:09                       ` Randy Barlow
2015-03-17 21:43                         ` Mark Knecht
2015-03-18  2:55                         ` Duncan
2015-03-18  4:29                           ` Randy Barlow
2015-03-18  5:35                             ` Frank Peters
2015-03-18  5:41                             ` Duncan
2015-03-16  6:29             ` Duncan
2015-03-14 13:09     ` Thanasis
2015-03-15  5:43       ` Duncan
2015-03-15 11:31         ` Thanasis
2015-03-16  6:56           ` Duncan
2015-03-15 20:04         ` Thanasis
2015-03-16  6:46           ` Duncan
2015-03-17  9:44             ` Benny Pedersen
2015-03-20 10:03               ` Duncan

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='pan$841f8$95f26381$6a3e8680$7af7cf1a@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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