From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Cross-building GHC
Date: Fri, 15 Mar 2013 00:20:30 +0100 [thread overview]
Message-ID: <8738vxh8ld.fsf@gnu.org> (raw)
In-Reply-To: <87obelg5iu.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 14 Mar 2013 23:12:09 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> You mean it _tries_ to use it, because it’s not available in chroot
>> builds, right?
>
> It'll try to use '/usr/bin/ld' if I run 'unset COMPILER_PATH'. I guess
> that it's trying to autodetect the right linker during './configure'.
>
> However, if I run
>
> export COMPILER_PATH=/nix/store/khdyz3i5aih56lxfk6hjvp3884apm7qb-gcc-cross-mips64el-linux-gnu-4.7.2/libexec/gcc/mips64el-linux-gnu:/nix/store/khdyz3i5aih56lxfk6hjvp3884apm7qb-gcc-cross-mips64el-linux-gnu-4.7.2/libexec/gcc/mips64el-linux-gnu/4.7.2
>
> to specify the location of subprograms, it'll complain about
> unrecognized opcodes. For example:
Yes, because COMPILER_PATH will influence both the native and the
cross-compiler. Same problem as discussed at
<http://gcc.gnu.org/ml/gcc/2013-02/msg00124.html>. That makes
COMPILER_PATH unusable in this context.
We need to check how to collect2 finds the cross ld, and adjust our
cross-GCC accordingly.
(That’s admittedly very vague, but finding out the details is left as an
exercise to the reader. ;-)).
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-03-14 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 12:23 Cross-building GHC Nikita Karetnikov
2013-03-14 17:32 ` Ludovic Courtès
2013-03-14 19:12 ` Nikita Karetnikov
2013-03-14 23:20 ` Ludovic Courtès [this message]
2013-05-16 8:04 ` Nikita Karetnikov
2013-05-16 18:16 ` Ludovic Courtès
2013-05-17 4:03 ` Nikita Karetnikov
2013-05-17 13:31 ` 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=8738vxh8ld.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 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.