Clang, GCC and the kdegames4 port

[Brandon Allbery]

On Sat, Dec 31, 2011 at 23:13, Ian Wadham <iandw.au at gmail.com> wrote:

>  - Both errors will get fixed, but not until KDE SC 4.8.1 at least.  The
> release
>   of KDE SC 4.8.0 is in its last stages ATM.
>
>  - There will be no further releases of KDE SC 4.7.  Release 4.7.4 is the
> last.
>   The KDE release guys have decided that.
>
>  - So, if the port of kdegames4 @4.7.4 or @4.8.0 is to compile with Clang
> within
>   the next six months or so, it will be necessary to patch it at the
> Macports end.
>   I can provide the patch, if required.
>
> I thought I should tell the list the above for general info re the
> transition from GCC
> to Clang.  It looks as though Clang does a more thorough job in some ways.
>
> Should I submit a ticket and include the patch?
>

I *think* the prevailing notion is that, if upstream plans to address it,
we just switch to llvm-gcc-4.2 (that's how I've been making KDE stuff build
in general here) in the Portfile and wait for upstream to catch up, rather
than patch locally and have to remove the patches later (which is more
intrusive and labor-intensive).

And yes, clang is much more strict about errors, and also has better error
messages.  This is a good thing.  It's just that MacPorts is about making
stuff work on OS X with the minimum reasonable effort, not so much about
maintaining its own "forks" of stuff (regardless of how temporary).

-- 
brandon s allbery                                      allbery.b at gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20111231/95c06b48/attachment.html>