gcc6 binary for mac os x tiger powerpc (ibook g3 800 MHz)

[trevor12]

pls would be anybody so kind and upload somewhere binery gcc6 (maybe also libs ?). I tried to compile it via macports but without success after 24 hours of compiling. Thank you very much. Martin

 

[mmphosis]

I usually build gcc from source, as needed, using Xcode. I think the builds take longer than 24 hours! (2 days? I can't remember.) Removing building ALL of the languages and building just the ones you need should help.

Although both macports and brew are excellent tools, I haven't used macports in many years, and I usually stay away from brew/homebrew.

Simply handing over a binary might not work because as you mention "libs" which in my experience all the paths need to be absolutely correct. I do local builds and installs not as root and not in /usr/local which the notes for gcc recommend against doing. I was using Mac OS X 10.5.8 (Leopard) with Xcode 3.1.4 Developer Tools. The version I built was 6.4.0. The current version of gcc6 appears to be gcc-6.5.0 2018-10-30

 

[mmphosis]

I appreciate you asking for this. I can't make any promises.

This has got me to dig out my old iBook G3 (500Mhz, 384MB RAM with a dead battery, and a flaky power adapter -- the iBook instantly powers off if I do so much as breathe on the power cord.) It's running Mac OS X 10.4.11 (Tiger) and appears to have Xcode 2.4.1 already installed, and it looks like I had built or attempted to build (what are now older versions of) postgresql, php, sqlite, and mariadb. Anyways, onto building gcc-6.x ...

I tried a very simple build of gcc-6.5.0 from source but it didn't work. I am currently doing a build of gcc-6.4.0 using my makefile and scripts that I used on Mac OS X 10.5.8 and Xcode 3.1.4. If all goes well, it'll finish tomorrow sometime.

partial log from an older build:
*** STARTED ***
Sat Jan 27 21:45:59 PST 2018
.
.
.
*** DONE ***
Sun Jan 28 14:39:10 PST 2018

 

[trevor12]

I appreciate you asking for this. I can't make any promises.

This has got me to dig out my old iBook G3 (500Mhz, 384MB RAM with a dead battery, and a flaky power adapter -- the iBook instantly powers off if I do so much as breathe on the power cord.) It's running Mac OS X 10.4.11 (Tiger) and appears to have Xcode 2.4.1 already installed, and it looks like I had built or attempted to build (what are now older versions of) postgresql, php, sqlite, and mariadb. Anyways, onto building gcc-6.x ...

I tried a very simple build of gcc-6.5.0 from source but it didn't work. I am currently doing a build of gcc-6.4.0 using my makefile and scripts that I used on Mac OS X 10.5.8 and Xcode 3.1.4. If all goes well, it'll finish tomorrow sometime.

partial log from an older build:
*** STARTED ***
Sat Jan 27 21:45:59 PST 2018
.
.
.
*** DONE ***
Sun Jan 28 14:39:10 PST 2018

Good afternoon, If it will be succesful, I would appreciate sharing of binary and libs because I know where I must place these as it would compile via macports (or is it possible to build it as static binary ?).

 

[mmphosis]

is it possible to build it as static binary ?

Unfortunately, no -- although I believe anything is possible. Question: How can I compile GCC as a static binary? Short Answer: "Don't try to build it as a static binary. That's hopeless."

Good afternoon, If it will be succesful, I would appreciate sharing of binary and libs because I know where I must place these as it would compile via macports

It could take a while, and I don't know if it will be successful. I think the build stopped last night. I am running it again.

 

[mmphosis]

I suspect this could take a week or more to complete! At the moment, the Power Macs are all down here due to a power outage. Maybe sometime in Janurary at this rate. I'll try to start the build on the iBook G3 once the power is back on.

I am doing some testing of my build on a Linux PC for now, there are some things I've discovered that I was doing wrong. The big problem was I was running the build inside the source directory which seemed to work in the past, but this is not the way to run it. I am also looking into cctools. I am also reviewing the configure options. For testing, I am only building the C compiler.

I intend to build c,objc,c++,obj-c++. If any of these can be excluded, let me know.

 

[trevor12]

I suspect this could take a week or more to complete! At the moment, the Power Macs are all down here due to a power outage. Maybe sometime in Janurary at this rate. I'll try to start the build on the iBook G3 once the power is back on.

I am doing some testing of my build on a Linux PC for now, there are some things I've discovered that I was doing wrong. The big problem was I was running the build inside the source directory which seemed to work in the past, but this is not the way to run it. I am also looking into cctools. I am also reviewing the configure options. For testing, I am only building the C compiler.

I intend to build c,objc,c++,obj-c++. If any of these can be excluded, let me know.

thank you for trying, (I am not professional programmer, only ocassionally I want to try build some tools where only source code often on github is available, .configure, make, make install)

I tried to find on internet some website where author would compile time consuming packages for g3 processors and offers binaries, but without success.

If it is bother to you, it is ok that I will only have applegcc-42 (is it too old to build new binary from new source files ?)
Also I do not know how to compile via X-Code, maybe if I know it, I did not need gcc6 ?


martin

 

[mmphosis]

Older versions of gcc should work for most things. I use the Apple versions of gcc that come with Xcode. On Mac OS X 10.4.11 (Tiger) with Xcode 2.4.1, I am using Apple gcc 4.0.x to attempt the builds of gcc 6.4.0. I've built newer versions of bash, dash, make and other software using the version of Apple gcc (4.2?) that comes with Xcode 3.1.4 on Mac OS X 10.5.8 (Leopard.) If Xcode is installed okay, you should be able to use: configure, make, make install. I would check the Xcode Installer, I can't remember if you need to check an extra box in the installer to build using command line tools. It is also possible to use new versions of Xcode, on Intel Macs , to build for older versions of Mac OS X -- again check the boxes to do this when installing Xcode.

The power is still out, so probably in 2019, I am going to continue trying to build gcc (and document how to build gcc) for Tiger, using Tiger on a PowerPC G3. I am also thinking that there are options in Xcode to build command line tools, and there may be ways to build binaries that will work for both Tiger and Leopard. Apple gcc-4.2 should work -- good luck!

 

[nglevin]

Works fine for me with Tigerbrew's version of gcc6, it builds without plugins and adds patches necessary for Tiger and Leopard.

Just set it up like on a modern Mac as indicated in Tigerbrew's README.md, and `brew install gcc6`.

`brew install gcc` will get you a version of GCC 7, similarly patched for Altivec and other PPC Mac considerations.