From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Problem with musl-gcc script. Is it bad installation?
Date: Sun, 6 Mar 2016 02:14:00 +0100 [thread overview]
Message-ID: <20160306011400.GR29662@port70.net> (raw)
In-Reply-To: <20160306010907.GQ29662@port70.net>
* Szabolcs Nagy <nsz@port70.net> [2016-03-06 02:09:07 +0100]:
> * John Found <johnfound@asm32.info> [2016-03-06 03:02:30 +0200]:
>
> > On Sat, 5 Mar 2016 19:36:09 -0500
> > Rich Felker <dalias@libc.org> wrote:
> >
> > > The musl-gcc script is limited in its usefulness, and was not really
> > > designed/tested for repurposing an existing x86_64 gcc as an i386-musl
> > > one. You should be able to make it work though by editing the musl-gcc
> > > script to remove the double quotes around "${REALGCC:-...}". If that
> > > works for you, this is possibly a change we should make upstream.
> > >
> > > Rich
> >
> > After the suggested change, I can start musl-gcc and it even accepts some commands as --help
> > But trying to use it with ./configure script again fails with:
> >
> > checking for gcc... musl-gcc
> > checking whether the C compiler works... no
> > configure: error: in `/work/cwork/SQLite/sqlite-autoconf-3110100':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> >
> > In the config.log I found the following:
> >
> > configure:3234: musl-gcc conftest.c >&5
> > /usr/bin/ld: skipping incompatible /usr/local/musl/lib/libc.so when searching for -lc
> > /usr/bin/ld: skipping incompatible /usr/local/musl/lib/libc.a when searching for -lc
> > /usr/bin/ld: cannot find -lc
> > collect2: error: ld returned 1 exit status
>
> your gcc toolchain does not support -m32
> because it's missing i386 gcc runtime libraries.
>
> install the appropriate i386 libgcc package or
> get a proper i386 toolchain.
>
on a second thought that would prevent the musl build too,
i think musl-gcc does not pass the -Wl,-melf_i386 to the linker
> > configure:3238: $? = 1
> > configure:3276: result: no
> > configure: failed program was:
> > | /* confdefs.h */
> > | #define PACKAGE_NAME "sqlite"
> > | #define PACKAGE_TARNAME "sqlite"
> > | #define PACKAGE_VERSION "3.11.1"
> > | #define PACKAGE_STRING "sqlite 3.11.1"
> > | #define PACKAGE_BUGREPORT "http://www.sqlite.org"
> > | #define PACKAGE_URL ""
> > | #define PACKAGE "sqlite"
> > | #define VERSION "3.11.1"
> > | /* end confdefs.h. */
> > |
> > | int
> > | main ()
> > | {
> > |
> > | ;
> > | return 0;
> > | }
> >
> >
> > Regards
> > --
> > http://fresh.flatassembler.net
> > http://asm32.info
> > John Found <johnfound@asm32.info>
next prev parent reply other threads:[~2016-03-06 1:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 22:28 John Found
2016-03-06 0:36 ` Rich Felker
2016-03-06 0:51 ` Szabolcs Nagy
2016-03-06 1:02 ` John Found
2016-03-06 1:09 ` Szabolcs Nagy
2016-03-06 1:14 ` Szabolcs Nagy [this message]
2016-03-06 1:15 ` John Found
2016-03-06 1:18 ` Szabolcs Nagy
2016-03-06 2:20 ` James B
2016-03-06 2:33 ` Rich Felker
2016-03-06 13:07 ` James B
2016-03-06 7:30 ` John Found
2016-03-06 13:07 ` James B
2016-03-06 13:26 ` John Found
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=20160306011400.GR29662@port70.net \
--to=nsz@port70.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).