public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Henk Schurink <mail228673@gmail.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: Asm errors when cross-compiling to arm-eabi
Date: Sun, 10 Nov 2019 08:20:00 -0000	[thread overview]
Message-ID: <877e4887mu.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAE_vUKFFGFMhT8hCwBYZecUc6T3Mk4uu_2V7hJnQXVX_0iPEWw@mail.gmail.com>	(Henk Schurink's message of "Sun, 10 Nov 2019 01:50:09 +0100")

* Henk Schurink:

> I keep encountering an error when trying to cross-compile libffi for
> ARM-eabi:
>
> $ git clone https://github.com/libffi/libffi && cd libffi
> $ ./configure --build=x86_64-linux-gnu --host=arm-eabi --prefix=/data/build
> --enable-static
> $ make
> ...
> ../src/arm/sysv.S: Assembler messages:
> ../src/arm/sysv.S:111: Error: unknown pseudo-op: `.syntax'
> ../src/arm/sysv.S:151: Error: unknown pseudo-op: `.arm'
> ../src/arm/sysv.S:151: Error: junk at end of line, first unrecognized
> character is `@'
> ../src/arm/sysv.S:152: Error: no such instruction: `stmfd sp!,{r0-r3,fp,lr}'
> ../src/arm/sysv.S:153: Error: junk at end of line, first unrecognized
> character is `@'
> ...
> ../src/arm/sysv.S:440: Error: no such instruction: `ldr pc,[pc]'
> Makefile:1335: recipe for target 'src/arm/sysv.lo' failed

This suggests that the native assembler is running, not the
cross-assembler.  Unfortunately, you did not include the output line
with the invocation of the assembler.

  reply	other threads:[~2019-11-10  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10  0:50 Henk Schurink
2019-11-10  8:20 ` Florian Weimer [this message]
2019-11-10 11:35   ` Henk Schurink
2019-11-10 17:41     ` Florian Weimer

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=877e4887mu.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=libffi-discuss@sourceware.org \
    --cc=mail228673@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.
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).