Summary: | dev-python/pycdio-0.20-r1 : swig/pycdio_wrap.c:8020:66: error: DRIVER_BSDI undeclared (first use in this function); did you mean DRIVER_OSX ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | covici, slawomir.nizio |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=651292 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
dev-python:pycdio-0.20-r1:20171123-171643.log emerge-history.txt environment etc.portage.tbz2 temp.tbz2 patch for new cdio Fixes BSDI issue |
Description
Toralf Förster
2017-11-23 19:06:03 UTC
Created attachment 506130 [details]
emerge-info.txt
Created attachment 506132 [details]
dev-python:pycdio-0.20-r1:20171123-171643.log
Created attachment 506134 [details]
emerge-history.txt
Created attachment 506136 [details]
environment
Created attachment 506138 [details]
etc.portage.tbz2
Created attachment 506140 [details]
temp.tbz2
I am also seeing this Created attachment 508616 [details, diff]
patch for new cdio
If you patch their cdio to not match that deprecated constant, it compiles. Given that BSDI hasn't existed in years, I don't think doing this is any detriment, even with older libcdio.
(In reply to Adam Stylinski from comment #8) > Created attachment 508616 [details, diff] [details, diff] > patch for new cdio > > If you patch their cdio to not match that deprecated constant, it compiles. > Given that BSDI hasn't existed in years, I don't think doing this is any > detriment, even with older libcdio. You attached a patch that adds epatch_user to the ebuild but not the change that actually makes it build. What's the actual one? Created attachment 525846 [details, diff] Fixes BSDI issue (In reply to Sławomir Nizio from comment #9) > (In reply to Adam Stylinski from comment #8) > > Created attachment 508616 [details, diff] [details, diff] [details, diff] > > patch for new cdio > > > > If you patch their cdio to not match that deprecated constant, it compiles. > > Given that BSDI hasn't existed in years, I don't think doing this is any > > detriment, even with older libcdio. > > You attached a patch that adds epatch_user to the ebuild but not the change > that actually makes it build. What's the actual one? My apologies. Here's the actual patch, though it fails now that libcdio's API underwent another change. |