From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] getdev host packages
Date: Thu, 13 Feb 2014 10:08:05 -0500 [thread overview]
Message-ID: <CAMwGMjzXqsYnBUGCNSd=Q2gtYnRLsgbLf8087HXLXLxJMorZ-g@mail.gmail.com> (raw)
In-Reply-To: <20140213145734.GD17120@pengutronix.de>
On Thu, Feb 13, 2014 at 9:57 AM, Michael Olbrich
<m.olbrich@pengutronix.de> wrote:
> Hi,
>
> On Thu, Feb 13, 2014 at 09:40:13AM -0500, Jon Ringle wrote:
>> One issue that I've run across is that most of our developers have x86
>> machines and our build machine is x86_64, so the host-*-dev.tar.gz
>> packages don't work because they are built for the wrong kind of host.
>
> I never thought about that. Maybe we should add the host arch to the file
> name here?
That's a good idea. Do it for cross-* packages too. Then we won't try
to download {cross,host}-*-dev.tar.gz if the file names don't match
with the host arch.
>
>> However, is there any reason to think that the other non host
>> *-dev.tar.gz would be ok to use on x86 if they were built on x86_64
>> that are target arm?
>
> Well, all "cross-*" packages will have the same problems. Other than that,
> I don't think so. Some packages may create host tools, but those should not
> be visible past the install stage. You can verify that easily: Just check
> the architecture of all executables in the devpkgs with 'file'. Anything
> !arm will be a problem.
>
> Michael
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-02-13 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 14:40 Jon Ringle
2014-02-13 14:57 ` Michael Olbrich
2014-02-13 15:08 ` Jon Ringle [this message]
2014-02-13 15:32 ` Jon Ringle
2014-02-13 16:46 ` Michael Olbrich
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='CAMwGMjzXqsYnBUGCNSd=Q2gtYnRLsgbLf8087HXLXLxJMorZ-g@mail.gmail.com' \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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