On May 2, 2012, at 10:31 AM, Alexander Hansen wrote:

> On 5/2/12 9:20 AM, Cameron Christensen wrote:
>> On May 2, 2012, at 10:14 AM, Alexander Hansen wrote:
>> 
>>> On 5/2/12 8:36 AM, Cameron Christensen wrote:
>>>> I had the following issue with the fink installation of ctags not
>>>> working correctly on my newly updated OSX machine (Lion w/ latest XCode):
>>>> 
>>>> https://sourceforge.net/tracker/?func=detail&atid=106556&aid=3482809&group_id=6556
>>>> <https://sourceforge.net/tracker/?func=detail&atid=106556&aid=3482809&group_id=6556>
>>>> 
>>>> After trying to build ctags manually it still didn't work. The solution
>>>> was to use "normal" gcc instead of the llvm version shipped with xcode.
>>>> 
>>>> I hope this helps anyone else who has been frustrated by this issue.
>>>> 
>>>> Cheers,
>>>> Cameron aka taranaki
>>>> 
>>>> 
>>> 
>>> You didn't define '"normal" gcc', so it's going to be hard for the
>>> maintainer or anyone else to figure out exactly what you did.
>>> 
>> 
>> True, and thank you for pointing that out. I'd hoped sufficient details 
>> could be found in the sourceforge bug report, but here are all the compiler 
>> versions that were used:
>> 
>> (WORKED)
>> $ /usr/local/bin/gcc --version
>> gcc (GCC) 4.6.0
>> Copyright (C) 2011 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>> 
>> (DID NOT WORK)
>> $ which gcc
>> /usr/bin/gcc
>> $ /usr/bin/gcc --version
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 
>> 5658) (LLVM build 2336.1.00)
>> Copyright (C) 2007 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>> 
>> Best,
>> Cameron
>> 
>> 
> 
> That's not actually what you used.  During the build process, the first
> "gcc" in the PATH is a wrapper script that we have set up.
> 
> On Lion, it's /sw/var/lib/fink/path-prefix-clang/gcc, which points to clang.
> 

This is entirely possible regarding the fink installation.

I did build ctags myself from source and the default compiler was used (i.e. 
/usr/bin/gcc). This is why I reported the bug to the developer first: the 
errors from my build matched those found in the fink installation.

I'm not deeply familiar with the differences between clang, llvm, gcc or how 
the fink packages are built. I just hoped to shed light on a particularly murky 
bug.

Good luck,
Cameron 



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to