On Fri, Mar 14, 2014 at 1:02 PM, Tim Walker <[email protected]> wrote: > On 14 Mar 2014, at 12:46, Vittorio Giovara <[email protected]> wrote: > >> On Friday, March 14, 2014, Tim Walker <[email protected]> wrote: >> >>> On 14 Mar 2014, at 01:51, Vittorio Giovara >>> <[email protected]<javascript:;>> >>> wrote: >>> >>>> --- >>>> cc seems to work on osx and linux, it would allow skipping "--cc=clang" >>>> at configure on modern osx, but I'm not sure of the overall impact. >>>> Ideas? >>>> Vittorio >>> >>> Latest Xcode has gcc in /Applications/Xcode.app/Contents/Developer/usr/bin >>> (if I am not mistaken, even when you don't install command-line tools), so >>> I don't see that setting --cc is needed there either. >>> >>> >> That gcc is *very* old, like 4.2.1 iirc. Moreover osx doesn't ship gdb any >> more, lldb only. So you cannot usually debug a gcc-produced executable, >> unless you reconfigure with --cc and re-compile which may be mildly >> annoying. > > No, it's just an alias for (or a rather a copy of, it looks like) clang.
Yeah but it gets configured with older includes (--prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1) Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
