mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: Compile error with --target=i386
Date: Tue, 16 Feb 2016 13:10:58 +0300 (MSK)	[thread overview]
Message-ID: <alpine.LNX.2.20.1602161305001.32308@monopod.intra.ispras.ru> (raw)
In-Reply-To: <56C2E94C.7000705@gkmsoft.ru>

On Tue, 16 Feb 2016, Petr Petrov wrote:
> I'm trying to build the latest musl-libc 1.1.13 on i386 architecture.
> I'm using the following line:
> 
> ./configure --target=i386
> make
> 
> and I got:
> gcc -std=c99 -nostdinc -ffreestanding -ffloat-store -frounding-math
> -Wa,--noexecstack -D_XOPEN_SOURCE=700 -I./arch/i386 -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 -mtune=generic
> -Werror=implicit-function-declaration -Werror=implicit-int
> -Werror=pointer-sign -Werror=pointer-arith -include vis.h  -c -o
> obj/src/fenv/i386/fenv.o src/fenv/i386/fenv.s
> src/fenv/i386/fenv.s: Assembler messages:
> src/fenv/i386/fenv.s:12: Error: suffix or operands invalid for `pop'

It seems you'd like to compile a 32-bit musl on an x86-64 glibc-based system
using the dual-abi (x86-64 + i386) capability of the host GCC.

If so, you need to pass -m32 on the gcc command line to generate 32-bit code:

./configure --target=i386 CC=gcc\ -m32

Alexander


  reply	other threads:[~2016-02-16 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  9:18 Petr Petrov
2016-02-16 10:10 ` Alexander Monakov [this message]
2016-02-16 10:31   ` Petr Petrov
2016-02-16 10:39     ` Alexander Monakov
2016-02-16 16:54       ` Rich Felker
2016-02-16 19:12         ` Alexander Monakov
2016-02-16 19:49           ` Rich Felker

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=alpine.LNX.2.20.1602161305001.32308@monopod.intra.ispras.ru \
    --to=amonakov@ispras.ru \
    --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).