From: "Jc García" <jyo.garcia@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compiling for different CPU but same architecture
Date: Fri, 1 Aug 2014 07:04:43 -0600 [thread overview]
Message-ID: <CAGQH77fGsa+jXa0SDapDfj2qfrBT8d_xDu0kfNa-4OJE3pG5jw@mail.gmail.com> (raw)
In-Reply-To: <1406895736.1362.1.camel@nileshgr.com>
2014-08-01 6:22 GMT-06:00 Nilesh Govindrajan <me@nileshgr.com>:
>
> Why it shouldn't matter? What if a package's building process depends on
> some other package? Though the build process isn't for a completely
> different arch, it might matter. That's my doubt.
>
>
If you want to build packages(tbz2), especifically for one machine,
and you setup a container to do the building there you will have
everything you need and you can have /etc/portage in sync, the issue
might be if you want to reuse packages on both machines you would have
to ensure the package and dependencies use -mtune=generic, but you
still can have use flags differing that's more trouble.
I wanted to do the same as you, but my resources are more constrained,
I have an i3 desktop, where I have a container building for an
amd-e2100 netbook(mostly for large packages), I didn't use distcc
since building in the netbook doesn't really make the building much
faster, but if I had more resources I would try to use distcc in pump
mode.
next prev parent reply other threads:[~2014-08-01 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 3:53 [gentoo-user] Compiling for different CPU but same architecture Nilesh Govindrajan
2014-08-01 5:46 ` Canek Peláez Valdés
2014-08-01 5:59 ` wraeth
2014-08-01 7:53 ` Neil Bothwick
2014-08-01 8:01 ` Nilesh Govindrajan
2014-08-01 8:09 ` Neil Bothwick
2014-08-01 8:23 ` wraeth
2014-08-01 8:25 ` Nilesh Govindrajan
2014-08-01 8:37 ` wraeth
2014-08-01 11:45 ` Jc García
2014-08-01 11:51 ` Neil Bothwick
2014-08-01 12:00 ` Jc García
2014-08-01 12:22 ` Nilesh Govindrajan
2014-08-01 13:04 ` Jc García [this message]
2014-08-01 12:29 ` Nilesh Govindrajan
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=CAGQH77fGsa+jXa0SDapDfj2qfrBT8d_xDu0kfNa-4OJE3pG5jw@mail.gmail.com \
--to=jyo.garcia@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