From: Reiner Herrmann <reiner@reiner-h.de>
To: musl@lists.openwall.com
Subject: musl 1.1.16 build failure on armhf
Date: Wed, 4 Jan 2017 21:51:24 +0100 [thread overview]
Message-ID: <20170104205123.GH19319@reiner-h.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Hi,
when trying to build musl on armhf, the build fails with the following
error (gcc 6.3.0), which is also seen on the Debian build servers [0]:
> gcc -std=c99 -nostdinc -ffreestanding -fexcess-precision=standard -frounding-math -Wa,--noexecstack -D_XOPEN_SOURCE=700 -I./arch/arm -I./arch/generic -Iobj/src/internal -I./src/internal -Iobj/include -I./include -Os -pipe -fomit-frame-pointer -fno-unwind-tables -fno-asynchronous-unwind-tables -ffunction-sections -fdata-sections -Werror=implicit-function-declaration -Werror=implicit-int -Werror=pointer-sign -Werror=pointer-arith -include vis.h -Wa,-mimplicit-it=always -Wa,-mthumb -fPIC -c -o obj/src/thread/arm/atomics.lo src/thread/arm/atomics.s
> src/thread/arm/atomics.s: Assembler messages:
> src/thread/arm/atomics.s:59: Error: invalid constant (1) after fixup
> src/thread/arm/atomics.s:74: Error: invalid constant (1) after fixup
> Makefile:158: recipe for target 'obj/src/thread/arm/atomics.lo' failed
On other architectures it builds fine.
Does someone know what the issue is?
Kind regards,
Reiner
(Please keep me in CC)
[0]: https://buildd.debian.org/status/fetch.php?pkg=musl&arch=armhf&ver=1.1.16-1&stamp=1483481970
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-01-04 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 20:51 Reiner Herrmann [this message]
2017-01-04 21:06 ` Rich Felker
2017-01-04 21:13 ` Reiner Herrmann
2017-01-04 21:27 ` Reiner Herrmann
2017-01-04 21:36 ` Rich Felker
2017-01-07 15:19 ` Reiner Herrmann
2017-01-09 13:02 ` Szabolcs Nagy
2017-02-04 14:19 ` [PATCH] use .object_arch to declare the architecture of the object file Reiner Herrmann
2017-02-05 23:40 ` Rich Felker
2017-02-06 10:21 ` Szabolcs Nagy
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=20170104205123.GH19319@reiner-h.de \
--to=reiner@reiner-h.de \
--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).