mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Cc: ian@zenhack.net
Subject: Re: Compile error doing cross build on arm
Date: Mon, 8 Jul 2013 14:35:17 -0400	[thread overview]
Message-ID: <20130708183517.GJ29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130708195152.0704f577@ralda.gmx.de>

On Mon, Jul 08, 2013 at 07:51:52PM +0200, Harald Becker wrote:
> Hi Ian !
> 
> 08-07-2013 11:58 Ian Denhardt <ian@zenhack.net>:
> 
> > So I just hit a compilation error trying to cross compile musl
> > for arm:
> > -fno-stack-protector  -c -o src/stdio/vfwprintf.o
> > src/stdio/vfwprintf.c src/stdio/vfwprintf.c: In function
> > 'wprintf_core': src/stdio/vfwprintf.c:195:3: error: pointer
> > targets in passing argument 2 of 'wcsspn' differ in signedness
> > [-Werror=pointer-sign] In file included from
> > src/stdio/vfwprintf.c:7:0: ./include/wchar.h:62:8: note:
> > expected 'const wchar_t *' but argument is of type 'int *' cc1:
> 
> > CFLAGS= -Os -pipe -fomit-frame-pointer -fno-unwind-tables
> > -fno-asynchronous-unwind-tables -Wa,--noexecstack
> > -falign-functions=1 -falign-labels=1 -falign-loops=1
> > -falign-jumps=1 -Werror=implicit-function-declaration
> > -Werror=implicit-int -Werror=pointer-sign -Werror=pointer-arith
> > -fno-stack-protector CFLAGS_C99FSE = -std=c99 -nostdinc
> > -ffreestanding -fexcess-precision=standard -frounding-math
> 
> It is curious, but I had similar compile error on native ARM
> compile (gcc 4.6.4). They vanished after removing some of the
> option on my CFLAGS list. Didn't analyze this, but probable
> candidates the unwind-tables and math options. So play a bit with
> your CFLAGS list, try "CFLAGS=-Os" if problem vanishes.

The direct source of this error is that the compiler's wchar_t is
defined as int rather than unsigned. ARM EABI requires (stupidly) that
wchar_t be unsigned, so we follow that.

The indirect cause of the error, and the real problem, is almost
surely that the compiler was configured for old, pre-EABI ARM ABI.
This ABI is NOT supported by musl, and will lead to various major
problems that could otherwise go undetected for a long time, like
misaligned structures (the old ABI only had 4-byte alignment for
64-bit types, for example). So this issue needs to be checked and
fixed before moving ahead.

Rich


  reply	other threads:[~2013-07-08 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 15:58 Ian Denhardt
2013-07-08 17:51 ` Harald Becker
2013-07-08 18:35   ` Rich Felker [this message]
2013-07-08 22:32     ` Ian Denhardt

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=20130708183517.GJ29800@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=ian@zenhack.net \
    --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).