From: "Paweł Hajdan, Jr." <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] crossdev: installing _host_ build dependencies not automatic?
Date: Wed, 3 May 2017 12:05:48 +0200 [thread overview]
Message-ID: <5509f224-2aa4-6d58-dbfd-84e92cb99270@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 489 bytes --]
I encountered <https://bugs.gentoo.org/show_bug.cgi?id=617276> while
working on some cross-compiling project.
Admittedly, it may not be that easy to handle host package dependencies
fully automatically.
I'm wondering - is it documented what portage guarantees, and what I'm
expected to just manually handle to provide host build dependencies?
Any other advice about properly using crossdev would also be
appreciated. I'd be happy to test and help improve things.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2017-05-03 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:05 Paweł Hajdan, Jr. [this message]
2017-05-03 15:56 ` [gentoo-dev] crossdev: installing _host_ build dependencies not automatic? Alexis Ballier
2017-05-03 21:47 ` James Le Cuirot
2017-05-04 8:21 ` Alexis Ballier
2017-05-13 19:41 ` Paweł Hajdan, Jr.
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=5509f224-2aa4-6d58-dbfd-84e92cb99270@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@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