From: Rafael C <groups.r2@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: cp: cannot stat `misc/syscall-list.h': No such file or directory
Date: Sat, 09 Feb 2013 10:35:00 -0000 [thread overview]
Message-ID: <CAGYho3_F88ae7kCobC5sLH+yD+=VY-JG_Ci78m54R0Y6LGZ+-g@mail.gmail.com> (raw)
In-Reply-To: <CAGYho3-uZvkAq_PJ+ZCe_io-Z844XJoY5E3RyWP_qwKdcQNiqw@mail.gmail.com>
Since I got no replies and found no previous documentation of this
error. I tinkered with the source code and found that in
lib/ct-ng.1.18.0/scripts/build/libc/glibc-eglibc.sh-common line 407
the path should be:
"misc/bits/syscall.h"
instead of:
misc/syscall-list.h
I'd have written a patch but I'm fairly new to this. I hope this
manual fix helps others stuck with the same issue. Thanks.
On Mon, Feb 4, 2013 at 10:13 PM, Rafael C <groups.r2@gmail.com> wrote:
> Hi all. I'm trying to build an x86_64 toolchain with crosstool-ng
> 1.18.0 and ran across the following error (this didn't happen with
> 1.17.0 on the same machine):
>
> cp: cannot stat `misc/syscall-list.h': No such file or directory
>
> Here is the pertinent portion of the log:
>
> [ALL ] `bits/stdio_lim.h' ->
> `/opt/xtool/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sysroot/usr/include/bits/stdio_lim.h'
> [DEBUG] ==> Executing: 'cp' '-v' 'misc/syscall-list.h'
> '/opt/xtool/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sysroot/usr/include/bits/syscall.h'
> [ALL ] cp: cannot stat `misc/syscall-list.h': No such file or directory
> [ERROR]
> [ERROR] >>
> [ERROR] >> Build failed in step 'Installing C library headers & start files'
> [ERROR] >> called in step '(top-level)'
> [ERROR] >>
> [ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
> [ERROR] >> called from:
> do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@407]
> [ERROR] >> called from:
> do_libc_backend[scripts/build/libc/glibc-eglibc.sh-common@143]
> [ERROR] >> called from:
> do_libc_start_files[scripts/build/libc/glibc-eglibc.sh-common@60]
> [ERROR] >> called from: main[scripts/crosstool-NG.sh@632]
> [ERROR] >>
> [ERROR] >> For more info on this error, look at the file: 'build.log'
> [ERROR] >> There is a list of known issues, some with workarounds, in:
> [ERROR] >> '/opt/crosstool/share/doc/crosstool-ng/ct-ng.1.18.0/B
> - Known issues.txt'
> [ERROR]
> [ERROR] (elapsed: 25:13.19)
>
> Any help is greatly appreciated. Thanks.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-02-09 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGYho3_jaW2gcz6LO+iJ6Bec1zFf1Rq6Ym6L3dTdLqEqSgZncQ@mail.gmail.com>
2013-02-05 3:13 ` Fwd: " Rafael C
2013-02-09 10:35 ` Rafael C [this message]
2013-02-15 9:55 ` [patch] " Jérôme BARDON
2013-02-16 23:56 ` Yann E. MORIN
2013-02-26 1:48 ` Daniel Price
2013-03-03 21:13 ` Yann E. MORIN
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='CAGYho3_F88ae7kCobC5sLH+yD+=VY-JG_Ci78m54R0Y6LGZ+-g@mail.gmail.com' \
--to=groups.r2@gmail.com \
--cc=crossgcc@sourceware.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.
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).