Mailinglist Archive: opensuse-factory (761 mails)
|< Previous||Next >|
[opensuse-factory] GCC 4.7 status
- From: "Dominique Leuenberger a.k.a DimStar" <DimStar@xxxxxxxxxxxx>
- Date: Tue, 10 Apr 2012 04:58:27 -0400
- Message-id: <20120410045827.Horde.NS-yD0Q7_k5Pg-YzvfyWzfA@webmail.new.leuenberger.net>
as it has become custom to send out regular updates (be it only to keep people aware of the topic), here another round for the "GCC 4.7 as default in Factory" - Update:
Not much has happened in the last week. A critical component failing to build with Gcc 4.7 is currently libzypp, which, understandably, blocks the switch (well, I think it could always be decided to switch to 4.7, but keep zypp build with 4.6?)
Anyway, let's not paint it too dark: libzypp folks are helpful and looked into the matter. The first result was a regression in gcc which had been identified for libzypp.
There are currently 22 packages failing in my branch (home:dimstar:gcc47):
libzypp, which causes at least PackageKit to fail as a result.
blender (this might be to do with the openCOLLADA changes... could be trickier to find the cause)
ekiga/opal: nice bundle.. 'stable' series has been stale for a while. unstable series has it fixed, but backporting 'just that' is close to, well, a lot of work :)
gsd: not looked at that one yet
jack: likely not gcc 4.7 related, as it fails the same way in Factory.. it hangs the build bot.
kdebase3/kdepim3: presumably not too hard to patch... maybe I'll find time.
kvm: error: call to '__warn_memset_zero_len' declared with attribute warning: memset used with constant zero length (sounds like just a nice bug :) )
libQtWebKit4: I know AJ looked at that one already, but more work is needed.
limal*: not really sure: looks like it just does not like the new boost libs.
llvm: honestly, I have no clue, especially as it fails in stage 2... so the integration to the new headers seems to cause griev.
mariadb: conversion errors...
openvas-administrator: not really gcc4.7 related.. it's actually a glib 2.32 fallout..
rubygem-passenger: likely it does not like new boost libs
seamonkey: big beast... anybody?
sleuthkit: just a buffer overflow in ext2fs... it actually builds; just brp check raises it. Wondering why it's not triggered with gcc 4.6 though.
virtualbox: nasty... an update to the latest version should fix the gcc 4.7 issues (tried in my branch... raises a can of new worms)
If you feel like working on any of those, don't hesitate! The more people looking at them, the higher chance we get them fixed... and the more likely we can actually switch to Gcc 4.7 in time for 12.2 (mind it: we're passing M3... so there is not much time left if we want to do that switch for 12.2).
Looking forward for all your help!
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
|< Previous||Next >|