From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Initial cross-compilation support
Date: Fri, 29 Mar 2013 22:39:29 +0100 [thread overview]
Message-ID: <87a9plc2cu.fsf@gnu.org> (raw)
In-Reply-To: <87hajtq4xe.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sat, 30 Mar 2013 01:20:13 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> The absolute file name appeared in your previous message:
>
>> /nix/store/g9js73bwv1fl92h1nnf50vf1619irnxf-gcc-cross-sans-libc-mips64el-linux-gnu-4.7.2/lib/gcc/mips64el-linux-gnu/4.7.2/libgcc.a
>
> # objdump -a /nix/store/g9js73bwv1fl92h1nnf50vf1619irnxf-gcc-cross-sans-libc-mips64el-linux-gnu-4.7.2/lib/gcc/mips64el-linux-gnu/4.7.2/libgcc.a | grep 'file format' | head
> _m16addsf3.o: file format elf64-little
That’s n64, good.
>> After a bit of research, I found ports/sysdeps/mips/preconfigure (in
>> libc). Apparently, it interprets the OS part of the target triplet to
>> determine the ABI. So, if you specify --target=mips64el-linux-gnuabi64,
>> it should automatically build glibc for n64.
>
> I changed it like this:
>
> diff --git a/gnu/packages/cross-base.scm b/gnu/packages/cross-base.scm
> index 69dc9f5..8cd93e9 100644
> --- a/gnu/packages/cross-base.scm
> +++ b/gnu/packages/cross-base.scm
> @@ -87,6 +87,10 @@ GCC that does not target a libc; otherwise, target that libc."
> "--disable-libssp"
> "--disable-libquadmath"
> "--disable-decimal-float" ; would need libc
> +
> + ;; MIPS64
> + "--with-arch=mips64"
> + "--with-abi=64"
> )))
>
> ,(if libc
> @@ -231,7 +235,8 @@ XBINUTILS and the cross tool chain."
> ;;;
>
> (define-public xgcc-mips64el
> - (let ((triplet "mips64el-linux-gnu"))
> + ;; (let ((triplet "mips64el-linux-gnu"))
> + (let ((triplet "mips64el-linux-gnuabi64"))
> (cross-gcc triplet
> (cross-binutils triplet)
> (cross-libc triplet))))
Looks good.
>> So, if you specify --target=mips64el-linux-gnuabi64,
>> it should automatically build glibc for n64.
>
> But 'guix build' doesn't have '--target'. How can I specify it?
It’s a ‘configure’ flag; it’s passed automatically when libc is
cross-built.
> So I used the following command:
>
> # ./pre-inst-env guix build -K gcc-cross-mips64el-linux-gnuabi64
>
> [...]
>
> mips64el-linux-gnuabi64-gcc -mabi=64 -nostdlib -nostartfiles -r -o /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/libc_pic.os \
> -Wl,-d -Wl,--whole-archive /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/libc_pic.a -o /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/libc_pic.os
> mips64el-linux-gnuabi64-gcc -mabi=64 -nostdlib -nostartfiles -r -o /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/elf/librtld.map.o '-Wl,-(' /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/elf/dl-allobjs.os /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/libc_pic.a -lgcc '-Wl,-)' -Wl,-Map,/tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/elf/librtld.mapT
> /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/libc_pic.a: could not read symbols: Archive has no index; run ranlib to add one
> collect2: error: ld returned 1 exit status
> make[2]: *** [/tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.17.drv-1/build/elf/librtld.map] Error 1
Can you run ‘file’ on the above libc_pic.a, or the files it contains?
Could you paste (from the log) the command that built it?
I think the things you mention in config.log are harmless.
(BTW, note that we’re making actual progress! :-))
HTH,
Ludo’.
next prev parent reply other threads:[~2013-03-29 21:39 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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9plc2cu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).