I'm trying to update some programs by downloading and installing from source, mainly PHP and GCC. They both fail. PHP returns make Error 1, and GCC 4.4.2 returns 4 errors (the site does not load for me, so I can't download the package & tell the errors exactly). From what I've read, it's a 32-bit - 64-bit problem, but I can't seem to find a fix, and it kills me. So is it an OS-specific problem (and if so, how can I fix that?), or am I missing something?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Compiling from Source in Snow Leopard
- Thread starter Not Available
- Start date
- Sort by reaction score
First off you do not want to build GCC from non-Apple sources, especially not if you are going to be compiling Obj-C code.
And have you gone through the ./configure routine on PHP already? Is there a specific reason that you are replacing the PHP that is already installed on your system? For most purposes it is better to just built the modules you need and add them in.
And have you gone through the ./configure routine on PHP already? Is there a specific reason that you are replacing the PHP that is already installed on your system? For most purposes it is better to just built the modules you need and add them in.
I tried updating the GCC installation, and it returned those errors. So I was curious about it. Then, I tried replacing the 5.3.0 PHP with 5.3.1, and that didn't work either. I was trying to learn how to do this thing, and now I'm wondering what I am doing wrong. Yes, I did run the ./configure part, it went through, but it failed at the make part. It's not really a necessity, everything works fine right now as it is, but I wanted to do it for education purposes.
The easiest way to install these kinds of tools is through fink or MacPorts. Fink tends to have more stuff and also tends to offer newer versions, but MacPorts gives you a LOT more configurability.
As larkost said, you really don't want to be replacing Xcode's GCC unless you have a really good reason--and are really brave. If you do, you'll be on your own with virtually no support.
As larkost said, you really don't want to be replacing Xcode's GCC unless you have a really good reason--and are really brave. If you do, you'll be on your own with virtually no support.
Again, I'm not going for the easiest way to do it. As I said, everything works fine right now, I only wanted to try my hand at installing from source. So would it be easier if I had 1 x VirtualBox, 1 x Arch Linux?
From my experience, the benefits of installing from source are limited. It's difficult to keep track of what has been installed, so you wind up struggling with dependencies which may be less than obvious. There's no practical benefit to trying to learn the intricacies of compiling GCC on the Mac.
Building and installing from source has the major downside that it can be really difficult to uninstall, as you may not know where everything went, and these things don't come with uninstallers.
That being said, playing with this stuff in a separate install of the OS, be it Linux in a VM, Linux as a separate install, or OS X as a separate install has the benefit that if you FUBAR the system, you can wipe it and start over again.
The only time I install from source is if I am building libraries I intend to ship with a product, as then I can take finer control over what features are included as well as control of optimization flags and system version compatibilities. Also, most configure scripts give you the option of a "prefix" which gives you complete control over where to install which can make it easier to uninstall.
Building and installing from source has the major downside that it can be really difficult to uninstall, as you may not know where everything went, and these things don't come with uninstallers.
That being said, playing with this stuff in a separate install of the OS, be it Linux in a VM, Linux as a separate install, or OS X as a separate install has the benefit that if you FUBAR the system, you can wipe it and start over again.
The only time I install from source is if I am building libraries I intend to ship with a product, as then I can take finer control over what features are included as well as control of optimization flags and system version compatibilities. Also, most configure scripts give you the option of a "prefix" which gives you complete control over where to install which can make it easier to uninstall.
Apple updates GCC via Xcode updates, leave that one alone. Apple is moving away from GCC anyway, you don't want to start messing with that component.
If you want to try to build from source get ImageMagic and try to build that. That should keep you busy for a week or so.
If you want to try to build from source get ImageMagic and try to build that. That should keep you busy for a week or so.
Problem is, some applications do not come with binaries. For example, two weeks ago I was looking for a partition recovery software, and someone recommended me a program whose web site only had a download link for an archive containing the folder to run the ./configure from. So after a few days, I started looking for this kind of installation methods, and I wanted to give it a run. I guess I'll be installing Arch in VB, then. Thanks a lot!
soooo... ./configure && make didn't work? What was the error? Did you check ./configure --help?
...and Data Rescue is the best for data recovery. It also doesn't require compiling from source code.
I did not know what to do with the folder in the archive at that time
Recuva did and awesome job for me...and Data Rescue is the best for data recovery. It also doesn't require compiling from source code.