all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nikita Karetnikov <nikita@karetnikov.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Initial cross-compilation support
Date: Fri, 29 Mar 2013 05:49:42 +0400	[thread overview]
Message-ID: <8738vf6kll.fsf@karetnikov.org> (raw)
In-Reply-To: 87y5d7w3j5.fsf@gnu.org

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

>> Oh, I forgot to add the -K option.  There are no logs.

> -K has nothing to do with logs.  :-)

I meant the build tree.

I can't find 'libgcc.a':

/tmp/nix-build-gcc-cross-sans-libc-mips64el-linux-gnu-4.7.2.drv-0/build/build-i686-pc-linux-gnu/fixincludes# file fixincl.o
fixincl.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped

> You did it right.  :-)

I don't think so.

config.log:

configure:2785: gcc -c -mabi=64 -g -O2 --host=mips64el-linux-gnu  conftest.c >&5
gcc: error: unrecognized argument in option '-mabi=64'
gcc: note: valid arguments to '-mabi=' are: ms sysv
gcc: error: unrecognized command line option '--host=mips64el-linux-gnu'

[...]

ac_cv_env_CFLAGS_value='-mabi=64 -g -O2 --host=mips64el-linux-gnu'

Then I tried to use #:make-flags instead:

       ((#:configure-flags flags)
        `(cons ,(string-append "--host=" target)
               ,flags))

       ;; MIPS64
       ((#:make-flags flags)
        `(cons "CFLAGS=-mabi=64 -g -O2"
               ,flags))

       ((#:phases phases) ...)

And got the same collect2 error as before:

collect2: error: ld returned 1 exit status
make[2]: *** [/tmp/nix-build-glibc-cross-mips64el-linux-gnu-2.17.drv-8/build/libc.so] Error 1
make[2]: Leaving directory `/tmp/nix-build-glibc-cross-mips64el-linux-gnu-2.17.drv-8/glibc-2.17/elf'
make[1]: *** [elf/subdir_lib] Error 2
make[1]: Leaving directory `/tmp/nix-build-glibc-cross-mips64el-linux-gnu-2.17.drv-8/glibc-2.17'
make: *** [all] Error 2

I checked 'config.log' and found out that 'ac_cv_env_CFLAGS_value=' is
empty.  Does it mean that #:make-flags are not honored?

I tried to add the above 'CFLAGS' to GCC's #:make-flags, but it also
failed.

I also tried the same with '-march=mips64'.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-03-29  1:47 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 [this message]
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=8738vf6kll.fsf@karetnikov.org \
    --to=nikita@karetnikov.org \
    --cc=bug-guix@gnu.org \
    --cc=ludo@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.