Unfortunately the new [sloted] ebuild fails to build on my system! Out of curiosity I tried to re-compile app-backup/dar-2.2.6 & app-backup/kdar-2.0.7 ... which both build flawless & are running as desired! I'm attaching the crash-log & my `emerge-info' in a moment...
Created attachment 93677 [details] crash-log for the current build attempt
Created attachment 93678 [details] my `emerge --info'
Please report to upstream. Perhaps its amd64 gcc4* issue. I had tried unsuccessfully to fix it.
I'm experiencing this too, and can't find a report on the upstream m/l or sourceforge tracker. Was it reported upstream or should I do so?
Damn ... on 12.08.2006 @ 03.48 I scribbled the following note, which got lost on his way to bugzilla: Please excuse my being late ... the following is not to be meant sarcastic, I am only taking the chance to share my humble situation ... yes, I am trying to hold this box up-to-the-minute because I use it for my professional tasks mainly as a playwright & also to demonstrate my students how a perfect os should/could work ... but real life has it's own credentials, such being present for my beloved children & despite the fact that working with/on computers makes your private living become a wreckage ... whatever, if I find any spare moment, I promise to follow your advice & will contact the dar support group on `gmane' ... please notice also, that meanwhile I have masked the current build to avoid being pestered by an update reminder ;) Anyway ... thank you for trying to provide a fix! --- The approaching new curricula, my private struggles & never-ending projects ... until the end of this month, I'll have to quit! Either wait for my intervention ... or follow `The Call of Cthulhu' ;)
Builds for me if USE=-examples.
So I won't report this upstream, no time :-(
Removed examples USE flag from dar-2.3.1.
