| 1 |
Duncan's suggestion worked... |
| 2 |
Thanks. |
| 3 |
Gavin. |
| 4 |
|
| 5 |
On Thu, 2005-12-01 at 15:36 -0700, Duncan wrote: |
| 6 |
> Gavin Seddon posted <1133447986.25299.1.camel@linuxstation>, excerpted |
| 7 |
> below, on Thu, 01 Dec 2005 14:39:45 +0000: |
| 8 |
> |
| 9 |
> > |
| 10 |
> > |
| 11 |
> > hI, |
| 12 |
> > wITH 'CDRDAO' i RECEIVED |
| 13 |
> > 'OSoundIF-ao.o(.text+0x117): In function `SoundIF::~SoundIF()': |
| 14 |
> > : undefined reference to `ao_shutdown' |
| 15 |
> > SoundIF-ao.o(.text+0x155): In function `SoundIF::~SoundIF()': |
| 16 |
> > : undefined reference to `ao_shutdown' |
| 17 |
> > SoundIF-ao.o(.text+0x19a): In function `SoundIF::start()': |
| 18 |
> > : undefined reference to `ao_open_live' |
| 19 |
> > SoundIF-ao.o(.text+0x21e): In function `SoundIF::play(Sample*, long)': |
| 20 |
> > : undefined reference to `ao_play' |
| 21 |
> > SoundIF-ao.o(.text+0x268): In function `SoundIF::end()': |
| 22 |
> > : undefined reference to `ao_close' |
| 23 |
> > collect2: ld returned 1 exit status |
| 24 |
> > make[3]: *** [gcdmaster] Error 1 |
| 25 |
> > make[3]: Leaving directory |
| 26 |
> > `/var/tmp/portage/cdrdao-1.2.0-r1/work/cdrdao-1.2.0/xdao' |
| 27 |
> > make[2]: *** [all-recursive] Error 1 |
| 28 |
> > make[2]: Leaving directory |
| 29 |
> > `/var/tmp/portage/cdrdao-1.2.0-r1/work/cdrdao-1.2.0/xdao' |
| 30 |
> > make[1]: *** [all-recursive] Error 1 |
| 31 |
> > make[1]: Leaving directory |
| 32 |
> > `/var/tmp/portage/cdrdao-1.2.0-r1/work/cdrdao-1.2.0' |
| 33 |
> > make: *** [all] Error 2 |
| 34 |
> > |
| 35 |
> > !!! ERROR: app-cdr/cdrdao-1.2.0-r1 failed. |
| 36 |
> > !!! Function src_compile, Line 63, Exitcode 2 |
| 37 |
> > !!! could not compile' |
| 38 |
> |
| 39 |
> Hmm... That's in the xdao subdir. Checking my portage logs, I see my |
| 40 |
> cdrdao is merged with --without-xdao in the config. Checking the ebuild |
| 41 |
> itself, that's controlled by the gnome USE flag. I don't have gnome |
| 42 |
> installed here, and have that flag off, so it doesn't compile with gnome |
| 43 |
> support, including (apparently) xdao. |
| 44 |
> |
| 45 |
> You said this was a dependency of k3b, which is a KDE app, so it's |
| 46 |
> possible you don't use GNOME anyway, and could turn off that USE flag. |
| 47 |
> |
| 48 |
> Even if you do use GNOME, you obviously aren't currently using it with |
| 49 |
> cdrdao, or it would already be merged and the k3b merge wouldn't have to |
| 50 |
> pull it in. Therefore, you should be able to turn off the gnome USE flag |
| 51 |
> specifically for cdrdao without issue (unless you are just building your |
| 52 |
> system and know you will want to use that support). |
| 53 |
> |
| 54 |
> Changing a use flag from the system defaults for a specific package is as |
| 55 |
> simple as entering that package, along with the use flag (or in this case |
| 56 |
> -flag, -gnome), in /etc/portage/package.use: |
| 57 |
> |
| 58 |
> echo app-cdr/cdrdao -gnome >> /etc/portage/package.use |
| 59 |
> |
| 60 |
> Of course, that's working around the problem rather than fixing it, but if |
| 61 |
> you don't need gnome support in the package anyway, and that's what's |
| 62 |
> causing the problem, as seems to be the case... |
| 63 |
> |
| 64 |
> If you /do need/want gnome support, perhaps someone who's running GNOME |
| 65 |
> can help. |
| 66 |
> |
| 67 |
> -- |
| 68 |
> Duncan - List replies preferred. No HTML msgs. |
| 69 |
> "Every nonfree program has a lord, a master -- |
| 70 |
> and if you use the program, he is your master." Richard Stallman in |
| 71 |
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 72 |
> |
| 73 |
> |
| 74 |
-- |
| 75 |
Dr Gavin Seddon |
| 76 |
School of Pharmacy and Pharmaceutical Sciences |
| 77 |
University of Manchester |
| 78 |
Oxford Road, Manchester |
| 79 |
M13 9PL, U.K. |
| 80 |
|
| 81 |
-- |
| 82 |
gentoo-amd64@g.o mailing list |
Archives