Bug 638624 – 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 ?

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Toralf Förster 2017-11-23 19:06:03 UTC]

x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -Wall -fno-strict-aliasing -fPIC -I/usr/include/python2.7 -c swig/pycdio_wrap.c -o /var/tmp/portage/dev-python/pycdio-0.20-r1/work/pycdio-0.20-python2_7/temp.linux-x86_64-2.7/swig/pycdio_wrap.o
swig/pycdio_wrap.c: In function ‘init_pycdio’:
swig/pycdio_wrap.c:8020:66: error: ‘DRIVER_BSDI’ undeclared (first use in this function); did you mean ‘DRIVER_OSX’?
   SWIG_Python_SetConstant(d, "DRIVER_BSDI",SWIG_From_long((long)(DRIVER_BSDI)));
                                                                  ^~~~~~~~~~~
                                                                  DRIVER_OSX

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-desktop_20171121-221602

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-7.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby22 (with Rubygems) *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.6.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

emerge -qpv dev-python/pycdio
[ebuild   R   ] dev-python/pycdio-0.20-r1  USE="-examples" PYTHON_TARGETS="python2_7"

[Comment 1 Toralf Förster 2017-11-23 19:06:06 UTC]

Created attachment 506130 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-11-23 19:06:09 UTC]

Created attachment 506132 [details]
dev-python:pycdio-0.20-r1:20171123-171643.log

[Comment 3 Toralf Förster 2017-11-23 19:06:12 UTC]

Created attachment 506134 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-11-23 19:06:15 UTC]

Created attachment 506136 [details]
environment

[Comment 5 Toralf Förster 2017-11-23 19:06:18 UTC]

Created attachment 506138 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2017-11-23 19:06:21 UTC]

Created attachment 506140 [details]
temp.tbz2

[Comment 7 Adam Stylinski 2017-12-07 01:31:51 UTC]

I am also seeing this

[Comment 8 Adam Stylinski 2017-12-07 01:40:44 UTC]

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.

[Comment 9 Sławomir Nizio 2017-12-08 23:57:50 UTC]

(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?

[Comment 10 Adam Stylinski 2018-03-28 15:07:37 UTC]

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.