From: James B <jamesbond3142@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Problem with musl-gcc script. Is it bad installation?
Date: Sun, 6 Mar 2016 13:20:53 +1100 [thread overview]
Message-ID: <20160306132053.5c6a26f39db6a963ff1a1c11@gmail.com> (raw)
In-Reply-To: <20160306011825.GS29662@port70.net>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
On Sun, 6 Mar 2016 02:18:25 +0100
Szabolcs Nagy <nsz@port70.net> wrote:
>
> gcc -m32 is a hack.. you will find more brokenness
> if you keep using it instead of using an i386
> cross toolchain.
>
I use this spec file running 32-bit musl on 64-bit env ... it seems to work for making simple binaries.
(PS: there are hardcoded paths there, I installed 32-bit musl to /usr/musl32).
cheers!
--
James B <jamesbond3142@gmail.com>
[-- Attachment #2: musl-gcc.specs --]
[-- Type: application/octet-stream, Size: 693 bytes --]
*asm:
--32
%rename cpp_options old_cpp_options
*cpp_options:
-nostdinc -isystem /usr/musl32/include -isystem include%s %(old_cpp_options)
*cc1:
%(cc1_cpu) -m32 -nostdinc -isystem /usr/musl32/include -isystem include%s
*link_libgcc:
-L/usr/musl32/lib -L .%s
*libgcc:
32/libgcc.a%s %:if-exists(32/libgcc_eh.a%s)
*startfile:
%{!shared: /usr/musl32/lib/%{pie:S}crt1.o} /usr/musl32/lib/crti.o %{shared|pie:crtbeginS.o%s;:32/crtbegin.o%s}
*endfile:
%{shared|pie:crtendS.o%s;:32/crtend.o%s} /usr/musl32/lib/crtn.o
*link:
-m elf_i386 -dynamic-linker /ld-musl-i386.so.1 -nostdlib %{shared:-shared} %{static:-static} %{rdynamic:-export-dynamic}
*esp_link:
*esp_options:
*esp_cpp_options:
next prev parent reply other threads:[~2016-03-06 2:20 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
2016-03-06 1:15 ` John Found
2016-03-06 1:18 ` Szabolcs Nagy
2016-03-06 2:20 ` James B [this message]
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=20160306132053.5c6a26f39db6a963ff1a1c11@gmail.com \
--to=jamesbond3142@gmail.com \
--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).