From: Rob Landley <rlandley@se-instruments.com>
To: musl <musl@lists.openwall.com>, Szabolcs Nagy <nsz@port70.net>
Subject: Re: musl-cross-make build script.
Date: Sat, 18 Feb 2017 02:45:38 -0600 [thread overview]
Message-ID: <3fa40871-36f0-9d82-6602-f929ece76de6@se-instruments.com> (raw)
In-Reply-To: <20170217115321.GH12395@port70.net>
Oh right, this list has the broken reply-to header that makes "reply
all" not reply to all. I need to come up with a thunderbird plugin to
disable that...
On 02/17/2017 05:53 AM, Szabolcs Nagy wrote:
> * Rob Landley <rlandley@se-instruments.com> [2017-02-16 16:57:54 -0600]:
>>
>> git clone https://github.com/richfelker/musl-cross-make
>> cd musl-cross-make
>> ~/mcm-buildall.sh
>>
>> And then wait a long time and the result should wind up in "output".
>
> nice
>
>> #!/bin/bash
>
> isn't it posix sh compatible?
>
>> PATH="$LP" make OUTPUT="$OUTPUT" TARGET="$TARGET" \
>> GCC_CONFIG="--disable-nls --disable-libquadmath --disable-decimal-float $GCC_CONFIG" COMMON_CONFIG="$COMMON_CONFIG" \
>> install -j$(nproc)
>
> i didnt know about -j$(nproc), what does it do?
You answered your own question, but I note you can go "taskset 1
./thingy.sh" to do a single processor build with this. :)
>> for i in i686:: \
>> armv5l:eabihf:--with-arch=armv5t armv7l:eabihf:--with-arch=armv7-a \
>> "armv7m:eabi:--with-arch=armv7-m --with-mode=thumb --disable-libatomic --enable-default-pie" \
>> armv7r:eabihf:--with-arch=armv7-r \
>> armv8l:eabihf:--with-arch=armv8-a i486:: sh2eb:fdpic:--with-cpu=mj2 \
>> mipsel:: mips:: powerpc:: sh4:: microblaze:: mips64:: powerpc64:: \
>> s390x:: x86_64::
>
> aarch64 is missing
In theory armv8l is what they used to call aaaarrcchh64 before they
decided to stutter and pretend it wasn't arm or whatever that nonsense
is. (I've done my best to ignore it.)
https://www.arm.com/products/processors/armv8-architecture.php
In practice I haven't tested that one yet and it looks like it's broken,
have to figure out how to hit it with a rock...
(The armv7r target is also broken because it's nommu but not pie, need
to tweak that...)
> (and i don't think it's useful to
> build both armv7l and armv8l toolchains: the former
> can produce binaries for armv8-a targets just fine
These are not multilib toolchains. If armv7l is 32 bit, armv8l is 64
bit, they have different libgcc.a and so on...
> and i don't know about any code in the toolchain target
> libs that would be different on armv8-a,
One is 32 bit, one is 64 bit?
> well may be
> the new float to int rounding and acquire/release
> atomics insns could be used but that's about it)
Rob
next prev parent reply other threads:[~2017-02-18 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 22:57 Rob Landley
2017-02-17 11:53 ` Szabolcs Nagy
2017-02-17 11:56 ` Szabolcs Nagy
2017-02-18 8:45 ` Rob Landley [this message]
2017-02-18 12:53 ` Szabolcs Nagy
2017-02-18 13:39 ` 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=3fa40871-36f0-9d82-6602-f929ece76de6@se-instruments.com \
--to=rlandley@se-instruments.com \
--cc=musl@lists.openwall.com \
--cc=nsz@port70.net \
/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).