[CFT] Update to clang 3.4

[Stefan Esser]

Am 12.01.2014 17:21, schrieb Dimitry Andric:
> On 12 Jan 2014, at 13:12, Yamaya Takashi <yamayan at kbh.biglobe.ne.jp> wrote:
>> buildworld is failed when WITH_LLDB=
> 
> Yes, this is a known issue. I discussed it with Ed Maste.  Clang 3.4
> will have to be imported first, afterwards we can fix lldb.  
> 
> 
>> some ports cannot build.
>>
>> reason1: clang cannot handle some options.
>> (libmad build)
>> cc: error: unknown argument: '-fforce-addr'
>> cc: error: unknown argument: '-fthread-jumps'
>> cc: error: unknown argument: '-fcse-follow-jumps'
>> cc: error: unknown argument: '-fcse-skip-blocks'
>> cc: error: unknown argument: '-fregmove'
>> cc: error: unknown argument: '-fschedule-insns2'
>> (libtheora build)
>> cc: error: unknown argument: '-fforce-addr'
>> (poppler build)
>> c++: error: unknown argument: '-fno-check-new'
>> (py27-sqlite build)
>> cc: error: unknown argument: '-R/usr/local/lib'
>> (tbb build)
>> c++: error: unknown argument: '-fno-schedule-insns2'
>> (gstreamer-ffmpeg build)
>> cc: error: unknown argument: '-fno-force-addr'

Wouldn't it be best to put automatic fixup makros into ports/Mk/ that
remove the unsupported options from all files named "Makefile.in",
"Makefile", "configure", "CMakeLists.txt" (and probably many more I
forgot), if compiled with CLANG?

I just fixed a few of the KDE ports and their dependencies that way,
but I think it is very annoying that our ports' Makefiles will need
such option fixup in literally hundreds to thousands of places.

This will put a penalty on all port build times, but this effect could
be minimized by making the fixup conditional not only on CLANG and the
CLANG version used, but also on the presence of *_CONFIGURE etc. in the
particular port's Makefile.

Regards, STefan