Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 60423 - app-cdr/dvdrtools-0.1.6 fails on ~x86 (automake=1.6)
Summary: app-cdr/dvdrtools-0.1.6 fails on ~x86 (automake=1.6)
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Lars Weiler (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-15 09:59 UTC by Florian E.J. Fruth
Modified: 2004-10-30 19:41 UTC (History)
0 users

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


Attachments
patch to use automake-1.6 (dvdrtools-0.1.6.ebuild-automake1.6.patch,261 bytes, patch)
2004-08-15 10:02 UTC, Florian E.J. Fruth
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Florian E.J. Fruth 2004-08-15 09:59:31 UTC
dvdrtools-0.1.6 filed to build with the following error:

-----------------------------------------------------------
config.status: creating librscg/Makefile
config.status: executing default-1 commands
make[2]: Leaving directory `/var/tmp/portage/dvdrtools-0.1.6/work/dvdrtools-0.1.6/librscg'
make[2]: Entering directory `/var/tmp/portage/dvdrtools-0.1.6/work/dvdrtools-0.1.6/librscg'
Makefile:91: scsi-remote.Po: No such file or directory
Makefile:94: *** missing separator.  Stop.
make[2]: Leaving directory `/var/tmp/portage/dvdrtools-0.1.6/work/dvdrtools-0.1.6/librscg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/dvdrtools-0.1.6/work/dvdrtools-0.1.6'
make: *** [all] Error 2
-----------------------------------------------------------

i changed the .ebuild to use automake-1.6 and it worked for me...
Comment 1 Florian E.J. Fruth 2004-08-15 10:02:11 UTC
Created attachment 37484 [details, diff]
patch to use automake-1.6
Comment 2 Lars Weiler (RETIRED) gentoo-dev 2004-10-30 19:41:44 UTC
As this was the only bug with automake-problems on dvdrtools, I guess this was caused by an unproper update or by environment variables.

I'll close this bug WONTFIX, but if the problem should still exist, just reopen it.