Search found 22 matches
- Mon Mar 07, 2011 6:30 am
- Forum: Tools
- Topic: Update your Genesis/32X Toolchain!
- Replies: 110
- Views: 151501
But if you're building a clean toolchain for cross-compiling, you almost certainly don't have the needed newlib. That's the point - you probably only have the "native" newlib for your system, which will NOT make a proper build. Of course. But after you've done it once, there's usually no need to sp...
- Mon Mar 07, 2011 4:51 am
- Forum: Tools
- Topic: Update your Genesis/32X Toolchain!
- Replies: 110
- Views: 151501
The two-stage build is so that newlib is used when building the standard c/c++ libs. You build binutils first, build the plain C compiler with no libs, use that to build the newlibs, then use BOTH of those to build the FULL gcc suite of compilers. GCC only really needs the headers from newlib when ...
- Mon Mar 07, 2011 1:23 am
- Forum: Tools
- Topic: Update your Genesis/32X Toolchain!
- Replies: 110
- Views: 151501
Maybe it's the difference between using gcc-core + g++ instead of gcc + g++; gcc-core has problems even building with the ARM processor, so maybe it also has problems with the 68000 as well. Nah, I've been using the gcc-core and gcc-g++ packages for quite some time now. Just to test, I built 4.5.2 ...
- Sat Feb 26, 2011 7:48 pm
- Forum: Tools
- Topic: Update your Genesis/32X Toolchain!
- Replies: 110
- Views: 151501
I've built GCC 4.5.1 for m68k, and I don't recall having to do anything special to get C++ support working. I had to apply a patch so MPFR 3.0.0 would build, but that has apparently been fixed in 4.5.2. The configure command I used was just $ ../../gcc-4.5.1/configure --prefix=/Users/anders/local --...
- Wed Feb 09, 2011 7:03 pm
- Forum: Hardware
- Topic: New devcart
- Replies: 34
- Views: 31612
- Tue Feb 08, 2011 12:37 pm
- Forum: Hardware
- Topic: New devcart
- Replies: 34
- Views: 31612
- Sun Feb 06, 2011 9:35 pm
- Forum: Hardware
- Topic: New devcart
- Replies: 34
- Views: 31612
I plan to make cards without the ROM. Concept: RAM, CPLD and supervisor with a memory card or PC link. The procedure is the following: when powerup the supervisor fills the primary firmware into RAM and makes nMRES. At rest of time, it handles requests from M68K (memory card or PC link access). Thu...