unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: problem with building gcc-cross-4.8.3 for i686-pc-gnu
Date: Sat, 03 Jan 2015 22:27:27 +0100	[thread overview]
Message-ID: <87fvbr8shs.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzN3Tu4+n5ku7wNqxKXm4e1D5O64OamZWN2-Gni8Aza_eA@mail.gmail.com> (Manolis Ragkousis's message of "Tue, 30 Dec 2014 16:28:54 +0200")

Manolis Ragkousis <manolis837@gmail.com> skribis:

> When trying to build coreutils for i686-pc-gnu, building
> cross-gcc-4.8.3 with glibc-hurd fails with:
>
> In unknown file:
>    ?: 0 [string-append
> "/gnu/store/1hl59s1pikplwfgclw4mlk38pkx3pc72-glibc-hurd-cross-i686-pc-gnu-2.18"
> ...]
>
> ERROR: In procedure string-append:
> ERROR: In procedure string-append: Wrong type (expecting string): #f
>
> It shouldn't fail because glibc/hurd is in the path.

From the log you sent, it’s the ‘set-cross-path’ phase (of the
cross-gcc) that’s failing.

In cross-base.scm (in master), one of them is like this:

                   (setenv "CROSS_CPATH"
                           (string-append libc "/include:"
                                          linux "/include"))

Could it be that in your case ‘linux’ above is #f, hence the error?

HTH,
Ludo’.

  reply	other threads:[~2015-01-03 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 14:28 problem with building gcc-cross-4.8.3 for i686-pc-gnu Manolis Ragkousis
2015-01-03 21:27 ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-31 10:27 Marek Benc
2015-01-31 22:13 ` Marek Benc
2015-02-01 18:56   ` Marek Benc
2015-02-05 12:44     ` Ludovic Courtès
     [not found]       ` <54D3A92A.6060209@gmx.com>
     [not found]         ` <87h9v014wk.fsf@gnu.org>
2015-02-05 20:32           ` Marek Benc
2015-02-07 23:24             ` Ludovic Courtès
2015-02-05 12:38   ` 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=87fvbr8shs.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Guix-devel@gnu.org \
    --cc=manolis837@gmail.com \
    /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).