Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I am however still missing my mpicc and automake, which were included in earlier version of XCode but were apparently dropped. I was hoping there might be a _second_ package much like the command line tools that I overlooked.

I don't have access to my Mac right now (nor did I upgrade to 4.3 yet), and can't find a list of the tools online. Either the package doesn't include them (Xcode after all doesn't use automake/autoconf and other such GNU tools, in favor of its xcodebuild system) or they aren't put in the PATH (could try updatedb/locate to find them).

Otherwise, the Command Line Tools package should be sufficient to install them from MacPorts.
 
I don't have access to my Mac right now (nor did I upgrade to 4.3 yet), and can't find a list of the tools online. Either the package doesn't include them (Xcode after all doesn't use automake/autoconf and other such GNU tools, in favor of its xcodebuild system) or they aren't put in the PATH (could try updatedb/locate to find them).

I can tell you already that they are not included, sadly. I tried locate already and manually (and with find) searched through the Xcode.app-folder. In case anyone reads this and is interested: Upgrading will work fine (or so it did on my old laptop), and the autotools will be kept.

I am actually more surprised that they got rid of the OpenMPI installation. I can see that most Mac developers probably won't need to program highly parallel applications, but some of us do. :(

Otherwise, the Command Line Tools package should be sufficient to install them from MacPorts.

Okay, I'm gonna go with MacPorts, thanks.
By the way: Macports claims on their website that it won't work with XCode 4.3, only with 4.2. I got it installed though after finding out about the command line tools. Let's hope that it works out.

Thanks again and greetings from Germany, (sorry for my English btw.)

Floh
 
I am actually more surprised that they got rid of the OpenMPI installation. I can see that most Mac developers probably won't need to program highly parallel applications, but some of us do. :(

Was OpenMPI ever included with the developer tools?
 
Okay, I'm gonna go with MacPorts, thanks.
By the way: Macports claims on their website that it won't work with XCode 4.3, only with 4.2. I got it installed though after finding out about the command line tools. Let's hope that it works out.

You'll need to perform some workarounds (search for xcode-select) and a few symlinks to get it working. There's also some hacking required of the Macports configuration file.
 
Was OpenMPI ever included with the developer tools?

It was. I can still find it in my "/Developer-old/usr/bin/"-Folder on my old harddrive. It was actually nice to have a ready-made MPI on every Mac system. Well, those days are over...

----------

You'll need to perform some workarounds (search for xcode-select) and a few symlinks to get it working. There's also some hacking required of the Macports configuration file.

Thanks you, that has already been very helpful. I'll report back when I get it running.
 
This is frustrating as hell.

I have installed Xcode 4.5 Preview 2 and Command Line Tools for Xcode 4.5 preview 2 for Lion.

If I do gcc -v I get:
Code:
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.11~30/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~30/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)

...and g++ -v gives:

Code:
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.11~30/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~30/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)

...and clang -v gives:

Code:
Apple clang version 4.0 (tags/Apple/clang-421.10.48) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.0
Thread model: posix

....but when I try to make, I'm still getting:

Code:
Checking for a C compiler... not found.
make: *** [compiler] Error 1


arrggghh, I think I'm outa my depth :(
 
Code:
Checking for a C compiler... not found.
make: *** [compiler] Error 1

I am not an expert by any chance, but I know the following: This looks like a configure script that is called by make. This configure script will not only take a huge amount of options but is also highly dependent on what build system you use.

To me, the error message looks like an autotools one. Do you have a script "configure" in the directory? Have you tried giving that script the gcc location manually, like:
Code:
./configure CC=/usr/bin/gcc

I think to get help here, you need to post some more details on what you are trying to compile and with what build system.
 
Guys, new issue. I've got gcc and got gnuplot downloaded and running...kind of. But now every time I try to use gnuplot through Terminal, I tell it to plot a basic function and get the following error:

gnuplot> plot sin(x)
gnuplot(21992) malloc: *** error for object 0x7000000074697865: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6

What does all this mean and what can I do to fix it?

It means there is a bug in gnuplot. You'd have to run it under Xcode, set a breakpoint in malloc_error_break as it tells you, and the program will stop exactly at the point where the bug breaks the program. And then you figure out what's wrong and fix it.
 
I'm trying to compile flashrom.
It doesn't have a configure file.

I just downloaded flashrom to see what it's about.

First things first: You do know what you're doing, right? It says explicitely to not use flashrom on any laptop since you might permanently brick it. It also says (in the included README file) that you have to install DirectHW from coresystems first. If you want to compile such a delicate tool, I highly suggest you know your way around computers very well.

That being said: flashrom comes with its own very long Makefile. This Makefile seems to check for various compilers and go with the wrong one. It can not be fixed by MacOS experts, but by the guys from flashrom. They seem to have an IRC channel you can check out. Good luck.

----------

It means there is a bug in gnuplot. You'd have to run it under Xcode, set a breakpoint in malloc_error_break as it tells you, and the program will stop exactly at the point where the bug breaks the program. And then you figure out what's wrong and fix it.

For some reason, this seems to have landed in the wrong thread. The quote isn't from within the thread and it's about something completely different. Could the poster please check what went wrong?
 
I'm trying to use the program GNUplot to fit data, but I just updated to Lion and naturally had to update GNUplot. However, when I try to configure in Terminal it states that I do not have a C compiler, but I already installed Xcode 4 so I know that the GCC and GNU compilers were downloaded. I'm completely lost so any help would be great!

Have you installed the additional tools? If not then you've no GCC yet. I had this problem too only a few days ago :D
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.