From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Subject: Pre-compiled versions of ELLCC are now available via FTP.
Date: Sat, 15 Feb 2014 17:02:15 -0600 [thread overview]
Message-ID: <52FFF1F7.9000900@pennware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
Hi,
I have made pre-compiled versions of the ELLCC cross compilation tool
chain available for various Linux targets.
They can be found at ftp://ellcc.org/pub
Targets supported:
ARM (little and big endian)
i386
Mips (little and big endian)
PowerPC
X86_64
From the README:
The files in this directory contain pre-compiled versions of the ELLCC
cross compiler tool chain. Each tarball is meant to run on a specific
target linux system as indicated by the name, e.g. ellcc-arm-... are
executables that are supposed to run on an little endian ARM Linux box.
All of the executables in these tarballs are statically linked, so they
should run on any reasonably recent Linux box.
Tarball contents:
C/C++ compiler (ecc, ecc++)
Assemblers for all targets
GNU binutils compiled to support all targets.
GDB compiled to support all the targets.
All of the tarballs contain header files and runtime libraries for all
the targets so you should be able to build for any one of the targets [1].
These tarballs have not been tested, except for the i386 and x86_64
versions,
because I don't have access to Linux boxes running on the other targets. I
would welcome feedback on how they work for you.
If you have any problems, please post on the ELLCC forum:
http://ellcc.org/blog/?forum=forum
Please visit http://ellcc.org for more information.
Have fun!
-Rich
[1]: The ARM versions of the executables currently can only target ARM
processors because the ecc compiler became too large to be statically
linked when all processors were supported.
[-- Attachment #2: Type: text/html, Size: 2495 bytes --]
next reply other threads:[~2014-02-15 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 23:02 Richard Pennington [this message]
2014-02-16 1:36 ` 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=52FFF1F7.9000900@pennware.com \
--to=rich@pennware.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).