On 16-Aug-07, at 10:28 PM, Christian Biere wrote: > That's odd. Could you show me the output of the following? I suspect > that your GCC might not like the combination of -E with some other > compiler flags. Otherwise I don't see why it does not detect GCC 4.x.
The output is: > [22:30:23|~>~/Desktop/cbstest.sh > gcc_version_major 4 > gcc_version_minor 4 > gcc_version_patchlevel 1 Which seems more up to date. I think that the program calling itself gcc actually does 'stuff' and then calls the real gcc. I've a hazy thin whisp of something like a memory that something or other like this might possibly be happening. Apple's dev docs would explain it. But here's the files involved: > [22:32:44|~>ll -l /usr/bin/gcc* > lrwxr-xr-x 1 root wheel 7 Jun 6 09:51 /usr/bin/gcc@ -> > gcc-4.0 > -r-xr-xr-x 1 root wheel 260616 Sep 11 2006 /usr/bin/gcc-3.3* > -rwxr-xr-x 1 root wheel 80168 Sep 27 2006 /usr/bin/gcc-4.0* So unless they really cut a lot of bloat out of the old cc compiler, which somehow I doubt, I don't think it's really gcc. > Do you really have to pass --make=/usr/bin/make? Yes, I really do. Really a very odd thing. Um... my sh might really be bash, not the original sh. That's all I can think of. But that's less than rare, right? > Locating common programs... > I don't know where 'make' is, and my life depends on it. > Go find a free implementation or fix your PATH setting! - matt ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
