Bug 179202 - x11/kde4-workspace (and elsewhere): automoc4 SEGVs on certain files
Summary: x11/kde4-workspace (and elsewhere): automoc4 SEGVs on certain files
Status: Closed DUPLICATE of bug 185164
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-kde (group)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-02 15:10 UTC by Matthias Apitz
Modified: 2014-10-12 20:51 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Apitz 2013-06-02 15:10:00 UTC
While building x11/kde4-workspace, 'automoc4' crashes again and again on
different files, here one example:

# make install BATCH=yes USE_GCC=any
..
Scanning dependencies of target
plasma_containmentactions_applauncher_automoc
Generating switch.moc
Generating launch.moc
gmake[2]: ***
[plasma/generic/containmentactions/applauncher/CMakeFiles/plasma_containmentactions_applauncher_automoc] Segmentation fault (core dumped)
gmake[1]: ***
[plasma/generic/containmentactions/applauncher/CMakeFiles/plasma_containmentactions_applauncher_automoc.dir/all] Error 2
gmake[1]: *** Waiting for unfinished jobs....
[  5%] Built target plasma_containmentactions_switchwindow_automoc
gmake: *** [all] Error 2
*** [do-build] Error code 1

After identifying that the crash is in 'automoc4', I have rebuild the
port devel/automoc4 with

# make reinstall USE_GCC=any WITH_DEBUG=yes

to avoid regresion of 'clang' in 'automoc4', but this did not help;
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-06-02 15:10:08 UTC
Responsible Changed
From-To: freebsd-ports-bugs->kde

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Matthias Apitz 2013-06-02 16:01:05 UTC
the described situation reads like this bug report in KDE bug tracking
system:

https://bugs.kde.org/show_bug.cgi?id=296433

especially the moving/random source file of the crash;
Comment 3 Carlo Strub freebsd_committer freebsd_triage 2014-09-14 10:30:20 UTC
Is this PR still relevant?
Comment 4 Max Brazhnikov freebsd_committer freebsd_triage 2014-10-12 20:51:59 UTC

*** This bug has been marked as a duplicate of bug 185164 ***