Duncan McGregor wrote:
On 28 Dec 2005, at 22:06, Martin Costabel wrote:
A shot in the dark: Is there something wrong with your "sed"
executable? What do you get from
type -a sed
If it is not /usr/bin/sed, what is it?
Thanks for taking the time, but
$ type -a sed
sed is /usr/bin/sed
$ which sed
/usr/bin/sed
Well, then here is the longer version of the reasons for my guess: In my
version of /usr/sbin/gcc_select, there are the two lines
actual_ver="`cc -v 2>&1 | grep -i 'gcc version'`"
current_cc="`echo \"$actual_ver\" | sed -e 's/.*gcc version \([^
]*\).*/\1/'`"
If you execute this (in /bin/sh) and then do
echo $current_cc
you should get "4.0.1" as a result. According to what you said before,
it looks like you are instead getting the result "gcc version 4.0.1
(Apple Computer, Inc. build 5247)". This is the value of $actual_ver.
That is, the "sed -e ..." command is not doing anything. I am trying to
understand how this is possible, but this is difficult from the
distance. Maybe you can find it out yourself.
--
Martin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
