There is a m68k-elf-gcc toolchain available from DarwinPortsbased on gcc3.4.3 but unfortunately, it doesn't contain the Coldfirepatches and other goodies that are needed to work well with uClinux and surprisingly, all the available toolchains for OS X seem to be somewhat unavailable for download!
The GNU Compiler Collection (m68k-elf) I'm sure the puzzle I am doing with the bootstrap package can be improved. PowerPC running Darwin (Mac OS X kernel). Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at This version of GCC requires at least cctools-590.36. M68k-elf-gcc -O2 -c -o hello.o hello.c. M68k-elf-objdump -S hello.o That should compile your program and then give you an assembly dump. You may need to to enter 'm68k-elf-gcc -target-help' to find out how to specify the right machine type.
Myvarious attempts to build this cross compiler ended up saving the dayat a recent Internet Exchange Research workshop. We didn't have acompiler for our Sparc servers, they didn't have any CD-ROM drives, andthe Internet connection was too slow. Fortunately, I had everythingneeded on my PowerBook (I'm a packrat like few others) and I was ableto build a Sparc cross-compiler hosted on Darwin PPC.
Thatbit of success gave me a much needed shot in the arm to finish up thebuild of the Coldfire cross-compiler. It took almost 24 hours to buildit (including the various stops and rebuilds needed to make it compilecleanly), clearly not a job for the faint hearted, or those who give upeasily.
DOWNLOADS
You can get binaries of the toolchain for Mac OS X 10.4.4(PowerPC) from (the links below don't work since I haven't uploaded thefiles. I'm looking for a place to host them since I have a bandwidthlimit)
I'm looking for a better place to host these files. Ideas?
GETTING SOURCES
You'll need Bernardo Innocenti's sources.
It'sprobably wise to choose the most recent version of his sources, andhope for the best. Stick to the exact version of each source required(e.g. gcc 3.4.0 != gcc 3.4.3). I tried 3.4.3 but it crashed inside xgccdue to my incompetence at patching the sources.
BUILDING YOUR OWN
Yourexperience may differ from mine. What I do know is that building thistakes quite some time and you won't enjoy doing it again and again tofix problems (unless that's your sort of fun!)
Before building, install DarwinPorts and
Startthe build process by editing the build-uclinux-tools.sh script as peryour needs. I used Apple gcc 3.3 with the following settings inbuild-uclinux-tools.sh …
After setting up the build-uclinux-tools.sh script and downloading the necessary additional files and patches, you can do
and each time you encounter an error (and hopefully fix what's causing it) you can do
BUILD ERRORS (AND SOLUTIONS)
You'regoing to run into various errors during the build. These steps documenthow I managed to get past them. There are probably mistakes in them, orat least better ways to do them. Suggestions and improvements are mostwelcome. It should be easy to make this into a patch. Maybe I'll dothat the next time around, but it took so long to build that I wouldn'thold my breath for it.
Configuring the uClinux kernel
You'll receive a message saying
You should edit linux-2.4.x/Makefile and change all occurrences of expr to gexpr …
Building elf2flt-20040326
You'll get an error saying 「elf.h not found」 (it's not present on Darwin systems)
Edit elf2flt-20040326/elf.h and uncomment the #include
During linking, you'll get an error saying crt0.a not found. Edit Makefile.in, change
toAnd that should take care of it for you. Continue building via
Building m68k-bdm-1.3.0
This will fail because BDMhardware access hasn't been written for Darwin yet. The ioperm systemcall is missing, and there's no native driver, so editbuild-uclinux.tools.sh and in the stageA function, replace thefollowing lines
with the lines below
i.e. add—disable-ioperm and—disable-driver to the configure stanza.Building m68k-bdm-1.3.0
Thiswill fail again since its trying to build a static executable.Apparently, that's a no-no on Darwin. Edit Makefile.in and Makefile.amin the utils directory and remove the static lurking as below:
should be changed to
You should be still able to connect to a remote server that's running BDM.Since I'm running on a Powerbook, which doesn't even have a parallelport, it's not a big deal to not build the hardware interface bits of BDM. Your mileage may vary. You should be able to continue your build now.
Building gdb-6.1
You will receive an error due to an incorrect gdb.texinfo file. Editgdb-6.1/gdb/doc/gdb.texinfo and around line 6961 (or whatever makeinfo complained about) and change
to become
Afterthis, you should have a successful build. All the tools will beinstalled on your system by Bernardo's excellent build script.
Package Details: m68k-elf-gcc 10.2.0-2
Package Actions
- View PKGBUILD / View Changes
| Git Clone URL: | https://aur.archlinux.org/m68k-elf-gcc.git (read-only, click to copy) |
|---|---|
| Package Base: | m68k-elf-gcc |
| Description: | The GNU Compiler Collection (m68k-elf) |
| Upstream URL: | http://gcc.gnu.org |
| Licenses: | GPL, custom, LGPL, FDL |
| Conflicts: | m68k-elf-gcc-bootstrap |
| Replaces: | m68k-elf-gcc-bootstrap |
| Submitter: | doragasu |
| Maintainer: | doragasu |
| Last Packager: | doragasu |
| Votes: | 3 |
| Popularity: | 1.39 |
| First Submitted: | 2017-10-27 17:31 |
| Last Updated: | 2021-01-11 14:52 |
Dependencies (4)
- zlib(zlib-static, zlib-git, zlib-asm, minizip-asm, zlib-ng-git)
- m68k-elf-binutils>=2.29-1
- m68k-elf-newlib(make)
- m68k-elf-newlib(optional)
Sources (8)
doragasu commented on 2021-01-09 22:14
@Un1Gfn: Thanks for the feedback. I think I should be able to remove the m68k-elf-gcc-bootstrap if I move the m68k-elf-gcc-bootstrap in newlib to the build dependencies. Otherwise, if I do not touch the newlib PKGBUILD but remove the bootstrap provide from m68k-elf-gcc, you will be able to build it, but installation will fail (because newlib depends on m68k-elf-gcc-bootstrap and m68k-elf-gcc replaces it (and wants to uninstall it).
Un1Gfn commented on 2021-01-09 02:42
@doragasu Oops I didn't know it was for baremetal. I've switched to buildroot(uClibc) now. Thanks.
BTW: m68k-elf-gcc-bootstrap provides m68k-elf-gcc. But maybe m68k-elf-gcc should not provide m68k-elf-gcc-bootstrap the other way around.
doragasu commented on 2021-01-08 16:20
@Un1Gfn: This compiler is for bare metal targets, and it uses newlib instead of glibc. Most of the C standard library functions are usable without any additional requirements. But some of them like e.g. malloc() or printf() require you to implement some syscalls like the ones you are seeing in your error tailored for your specific target. For example where do you intend printf() to output the characters? On a bare metal target it could be an UART, an embedded screen with a framebuffer device, a memory region...
For more information read newlib documentation, specifically syscalls are documented here: https://sourceware.org/newlib/libc.html#Stubs
Un1Gfn commented on 2021-01-08 09:19
test.c
build w/ m68k-elf-gcc -std=c99 -o test.out test.c
fail
M68k-elf-gcc Mac Download Software
doragasu commented on 2020-05-24 18:57
Makes sense, added to both makedepends and optdepends. Thanks for the suggestion!
BTW I have never user freestanding mode. I have built things without using standard libraries, linking with -nostdlib. But never used -ffreestanding before.
rouhannb commented on 2020-05-24 15:41
Then perhaps you should add newlib as both a makedepend and an optdepend?
(Also, I’m not sure if you know this or not, but you can build executables without a library by using freestanding mode.)
doragasu commented on 2020-05-23 19:13
M68k-elf-gcc Mac Download Windows 10
I'm sure the puzzle I am doing with the bootstrap package can be improved. But I don't think putting newlib in the makedepends is a good idea, since if you remove the library after building the compiler, resulting compiler will fail to build executables.
rouhannb commented on 2020-05-18 17:23