mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: lowrisc-dev@lists.lowrisc.org
Subject: Re: [musl] Weekly Report of Porting musl to RISC-V Project #5
Date: Sun, 3 Jul 2016 16:24:46 +0200	[thread overview]
Message-ID: <20160703142445.GF19691@port70.net> (raw)
In-Reply-To: <CAA-4+je7YYMTMjTXCSVNop+N6oSO7ckvK-JsmReop0hUgk2sWQ@mail.gmail.com>

* Masanori Ogino <masanori.ogino@gmail.com> [2016-07-03 09:42:00 +0900]:
> Some failures are expected since musl on x86_64 also does the same
> ones (e.g. errors in src/api/fcntl.c), but there are some unexpected
> errors too. I guess that the "warning: <the name of a header> is
> shorter than expected" warning indicates bugs in arch-dependent part
> of I/O functions or system calls (or kernel?) and it causes syntax
> errors in the same compilation unit.

try to figure out this error:

cc1: warning: src/regression/printf-fmt-g-zeros.c is shorter than expected
In file included from src/regression/printf-fmt-g-zeros.c:3:0:
/usr/include/stdio.h:8:22: warning: /usr/include/features.h is shorter than expected
 #include <features.h>
                      ^
In file included from /usr/include/stdio.h:22:0,
                 from src/regression/printf-fmt-g-zeros.c:3:
/usr/include/bits/alltypes.h:46:19: error: missing ')' after "defined"
 #if defined(__NEED_suseconds_t) && !defined(__DEFINED_suseconds_t)
                   ^

is this a native toolchain?
i thought you would cross compile things first
(although libc-test is not set up to easily run
the tests in a simulator after cross compiling)

it might be some filesystem issue if there are
truncated files.



  reply	other threads:[~2016-07-03 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-03  0:42 Masanori Ogino
2016-07-03 14:24 ` Szabolcs Nagy [this message]
2016-07-06  7:37   ` Masanori Ogino

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=20160703142445.GF19691@port70.net \
    --to=nsz@port70.net \
    --cc=lowrisc-dev@lists.lowrisc.org \
    --cc=musl@lists.openwall.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.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).