all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: bug-guix@gnu.org
Subject: Re: Initial cross-compilation support
Date: Sun, 3 Mar 2013 17:26:08 +0100	[thread overview]
Message-ID: <201303031726.08488.andreas@enge.fr> (raw)
In-Reply-To: <87txoxv7x9.fsf@gnu.org>

Am Mittwoch, 27. Februar 2013 schrieb Ludovic Courtès:
> Commit 827d289 of the ‘core-updates’ branch adds cross-base.scm, which
> builds a cross tool chain.
> 
> So if you type ‘guix build gcc-cross-mips64el-linux-gnu’, you get a
> cross-compiler (+ libc, binutils) for that platform.  The compiler is
> slightly modified by this patch:

Congratulations! I tried the build and it worked without problem.

Am Sonntag, 3. März 2013 schrieb Nikita Karetnikov:
> > I’m making progress, but it may still be a week before it’s all in
> > place.
> 
> I'm willing to try this [1].  What should I adjust to build with n64?

Currently, "file /nix/store/bxxk1jih4qy1hs7s22hp4f0i98b1ldn6-gcc-cross-
mips64el-linux-gnu-4.7.2/mips64el-linux-gnu/lib/libgcc_s.so.1" returns

ELF 32-bit LSB shared object, MIPS, N32 MIPS-III version 1 (SYSV), 
dynamically linked, with unknown capability 0xf41 = 0x756e6700, with 
unknown capability 0x70100 = 0x1040000, not stripped

I think one needs to add the configure parameters "--with-arch=mips64 --
with-abi=64" to the cross build of gcc; and maybe "-march=mip64 -mabi=64" 
to the binutils and glibc. Ludovic should know best where to do it in the 
code. And then, if one wishes to extract bootstrap binaries for arbitrary 
target architectures (which are still needed, I suppose?), I assume one 
would have to modify bootstrap.scm to use the cross gcc instead of the 
native one.

Andreas

  reply	other threads:[~2013-03-03 16:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 20:05 Initial cross-compilation support Ludovic Courtès
2013-03-03 16:26 ` Andreas Enge [this message]
2013-03-03 21:32   ` Ludovic Courtès
2013-03-28  9:35     ` Nikita Karetnikov
2013-03-28 13:38       ` Ludovic Courtès
2013-03-28 21:00         ` Nikita Karetnikov
2013-03-28 22:41           ` Ludovic Courtès
2013-03-29  1:49             ` Nikita Karetnikov
2013-03-29  9:46               ` Ludovic Courtès
2013-03-29 21:20                 ` Nikita Karetnikov
2013-03-29 21:39                   ` Ludovic Courtès
2013-03-29 22:06                     ` Nikita Karetnikov
2013-05-20 19:40                       ` Ludovic Courtès
2013-05-21 18:46                         ` Nikita Karetnikov
2013-05-21 20:04                           ` Ludovic Courtès
2013-05-21 20:23                             ` Nikita Karetnikov
2013-05-21 20:54                               ` Nikita Karetnikov
2013-05-21 21:00                               ` Ludovic Courtès
2013-03-04  0:19   ` Nikita Karetnikov
2013-03-04 10:10     ` Ludovic Courtès
2013-03-04 16:56       ` Nikita Karetnikov
2013-03-09  9:56         ` Nikita Karetnikov
2013-05-24 21:30           ` Ludovic Courtès
2013-05-24 21:59             ` Nikita Karetnikov
2013-05-24 22:26               ` Ludovic Courtès
2013-05-27 21:49                 ` Ludovic Courtès
2013-05-24 22:04 ` Ludovic Courtès

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=201303031726.08488.andreas@enge.fr \
    --to=andreas@enge.fr \
    --cc=bug-guix@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.