public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Alexander Smirnov <asmirnov@ilbers.de>,
	 isar-users@googlegroups.com
Subject: Re: [RFC] [PATCH 0/9] Initial cross-compilation support
Date: Thu, 14 Jun 2018 14:55:39 +0200	[thread overview]
Message-ID: <dbc5d1b8c5d94d8245752ee362b154a7825742dd.camel@denx.de> (raw)
In-Reply-To: <1a4f5309433280bf0e3531d673ecdf86094316eb.camel@denx.de>

[-- Attachment #1: Type: text/plain, Size: 2701 bytes --]

On Thu, 2018-06-14 at 14:42 +0200, Claudius Heine wrote:
> Hi Jan,
> 
> On Thu, 2018-06-14 at 14:30 +0200, Jan Kiszka wrote:
> > On 2018-06-14 14:04, Claudius Heine wrote:
> > > Hi,
> > > 
> > > On Wed, 2018-06-13 at 15:07 +0200, Alexander Smirnov wrote:
> > > > Hi all,
> > > > 
> > > > this series introduces basic cross-compilation support for
> > > > Isar.
> > > > The
> > > > implementation
> > > > is based around new entity - buildchroot-cross, which is quite
> > > > similar to original
> > > > buildchroot, but has host architecture.
> > > 
> > > Here is a crazy idea from me and Henning:
> > > Have you tried just installing an amd64-arm cross toolchain into
> > > the
> > > existing arm buildchroot, then switch to it from the 'native'
> > > toolchain
> > > using a combination of PATH variable entries, symlinks and/or
> > > wrapper
> > > scripts and let binfmt deal with calling the amd64 binaries of
> > > the
> > > toolchain in the arm chroot environment?
> > > 
> > > This way the arm system would think that you are compiling
> > > nativly
> > > while in fact you are using a cross compiler that is not
> > > emulated.
> > > 
> > > Would that work?
> > 
> > I just heard some story from SUSE folks doing something probably
> > similar
> > in the past, but they had to patch binfmt to inject the native
> > tools
> > into the chroot.
> > 
> > How would you ensure in your proposal that the native compiler
> > finds
> > its
> > libraries?
> 
> I would try using the wrapper scripts. Setting all the paths to the
> toolchain root directory and then calling gcc and friends with '
> --sysroot /'.
> 
> I would have to try to find out if that works.

There is also chrpath...

As a more conventional method, you could have a cross-buildchroot with
only the cross compiler and distcc and make it that way available to
the buildchroot.

Claudius

> 
> Cheers,
> Claudius
> 
> -- 
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
> 
>             PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808
> B153
>                               Keyserver: hkp://pool.sks-
> keyservers.net
> 
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-06-14 12:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 13:07 Alexander Smirnov
2018-06-13 13:07 ` [PATCH 1/9] isar-bootstrap: Add routin to determine host arch Alexander Smirnov
2018-06-14 11:23   ` Henning Schild
2018-06-15 11:11     ` Alexander Smirnov
2018-06-15 11:15       ` Jan Kiszka
2018-06-13 13:08 ` [PATCH 2/9] isar-bootstrap: Move common part to include Alexander Smirnov
2018-06-13 13:08 ` [PATCH 3/9] isar-bootstrap: Add host architecture support Alexander Smirnov
2018-06-14 11:27   ` Henning Schild
2018-06-15 11:09     ` Alexander Smirnov
2018-06-13 13:08 ` [PATCH 4/9] isar-bootstrap-helper: Add parameter to set arch Alexander Smirnov
2018-06-13 13:08 ` [PATCH 5/9] buildchroot-cross: Initial implementation Alexander Smirnov
2018-06-14 11:36   ` Henning Schild
2018-06-15 11:16     ` Alexander Smirnov
2018-06-14 15:55   ` Jan Kiszka
2018-06-15 10:56     ` Alexander Smirnov
2018-06-15 11:12       ` Jan Kiszka
2018-06-17 19:28         ` Alexander Smirnov
2018-06-13 13:08 ` [PATCH 6/9] classes/dpkg*: Relocate dependency from buildchroot Alexander Smirnov
2018-06-14  6:44   ` Jan Kiszka
2018-06-15 10:52     ` Alexander Smirnov
2018-06-13 13:08 ` [PATCH 7/9] classes/dpkg*: Drop hardcoded buildchroot blobs Alexander Smirnov
2018-06-13 13:08 ` [PATCH 8/9] classes/dpkg-cross: Initial implementation Alexander Smirnov
2018-06-13 13:08 ` [PATCH 9/9] [FOR TESTING] libhello: Switch to cross compilation Alexander Smirnov
2018-06-13 13:57 ` [RFC] [PATCH 0/9] Initial cross-compilation support Jan Kiszka
2018-06-14 11:20 ` Henning Schild
2018-06-17 19:41   ` Alexander Smirnov
2018-06-18  7:04     ` Henning Schild
2018-06-14 12:01 ` Henning Schild
2018-06-14 12:04 ` Claudius Heine
2018-06-14 12:24   ` Henning Schild
2018-06-14 12:36     ` Claudius Heine
2018-06-14 12:30   ` Jan Kiszka
2018-06-14 12:42     ` Claudius Heine
2018-06-14 12:55       ` Claudius Heine [this message]
2018-06-15 10:50   ` Alexander Smirnov
2018-06-15 13:17     ` Claudius Heine

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=dbc5d1b8c5d94d8245752ee362b154a7825742dd.camel@denx.de \
    --to=ch@denx.de \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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