Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 247879 - media-video/gnome-subtitles fails to build with parallel make
Summary: media-video/gnome-subtitles fails to build with parallel make
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-21 04:34 UTC by Diego Elio Pettenò (RETIRED)
Modified: 2012-06-24 06:56 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Build log (media-video:gnome-subtitles-0.8:20081121-042900.log,17.07 KB, text/plain)
2008-11-21 04:35 UTC, Diego Elio Pettenò (RETIRED) 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Elio Pettenò (RETIRED) gentoo-dev 2008-11-21 04:34:34 UTC 
See attached build log.
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2008-11-21 04:35:21 UTC 
Created attachment 172621 [details]
Build log
Comment 2 Pedro Castro 2008-11-21 12:41:15 UTC 
This should have been fixed in the SVN trunk. Can you disable parallel compilation for this specific version?
Comment 3 Peter Alfredsen (RETIRED) gentoo-dev 2008-11-26 22:51:51 UTC 
Added -j1 in 0.8-r1 and a note to remove in next bump.

+*gnome-subtitles-0.8-r1 (26 Nov 2008)
+
+  26 Nov 2008; Peter Alfredsen <loki_val@gentoo.org> metadata.xml,
+  -gnome-subtitles-0.7.2.ebuild, -gnome-subtitles-0.7.2-r1.ebuild,
+  -gnome-subtitles-0.8.ebuild, +gnome-subtitles-0.8-r1.ebuild:
+  Fix bug 224547, depend on gtk-sharp with fixed api (b.gnome.o 558312
+  b.novell.c 445370) and update deps for mono-2.
+
Comment 4 Diego Elio Pettenò (RETIRED) gentoo-dev 2008-11-27 00:17:38 UTC 
-j1 is a workaround, this bug has to stay open.
Comment 5 Peter Alfredsen (RETIRED) gentoo-dev 2008-12-25 23:28:49 UTC 
That may be, but it's fixed for us, since the next version won't have this problem.