unofficial mirror of bug-guix@gnu.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 01:00:59 +0400	[thread overview]
Message-ID: <87boa38cj8.fsf@karetnikov.org> (raw)
In-Reply-To: <878v57r6f4.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 28 Mar 2013 14:38:07 +0100")

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

> Can you run ‘file’ on libgcc.a (or one of the .o files it contains)?
> Can you check in the glibc log whether a -mabi flag is passed?

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

> You may need to explicitly add -mabi=64 for glibc.  It should be
> possible to do it with something like:

>   #:configure-flags '("CFLAGS=-mabi=64 -g -O2")

Which 'glibc' should be used?

I tried to use

       ((#:configure-flags flags)
        `(cons ,(string-append "CFLAGS=-mabi=64 -g -O2 " "--host=" target)
               ,flags))

in 'cross-libc' ('cross-base.scm'), but it failed:

checking for suffix of object files... configure: error: in `/tmp/nix-build-glibc-cross-mips64el-linux-gnu-2.17.drv-3/build':
configure: error: cannot compute suffix of object files: cannot compile

I reread the quasiquote-related part of the manual, but I still fail to
understand how to add 'CFLAGS' properly.

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

  reply	other threads:[~2013-03-28 20:59 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 [this message]
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

  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=87boa38cj8.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 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).