Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 81828 - cdrdao-1.1.9 builds and runs on os x panther
Summary: cdrdao-1.1.9 builds and runs on os x panther
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Mac OSX (show other bugs)
Hardware: PPC All
: High normal (vote)
Assignee: Gentoo for Mac OS X
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-12 23:49 UTC by Karl Svec
Modified: 2006-04-12 10:52 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Svec 2005-02-12 23:49:09 UTC
Cdrdao and its dependencies ( cdrtools, pccts ) build successfully with the ppc-macos keyword. Cdrdao also runs ( using the generic-mmc driver on my system ), but not in the same capacity as on a Linux system. Cdrdao has to fight with the OS X volume manager for control of the burner, so there's a couple things that need to be done:

- use 'hdiutil unmount /Volumes/name_of_cd' before creating a cd image file
- have OS X ignore inserted blank cds
 
Problems:

I haven't been able to get 'cdrdao copy' to work on my slot-load G3 iMac. When cdrdao is done creating a temporary image file, it doesn't automatically eject the disc. Since the disc had to be manually unmounted earlier so cdrdao could read it, OS X doesn't "know" the disc is in the drive, so hitting the eject key on the keyboard won't eject it. At this point, the disc can only be ejected by sticking a paper clip into the drive and hitting the manual eject button. After this, inserting a blank cd into the drive alerts the OS X volume manager, which then "steals" control of the burner from cdrdao, which then quits with an error.

So the bottom line is that 'cdrdao copy' won't work on a slot-load G3 iMac ( the only machine I've tested it on ).

The workaround for this is to use 'cdrdao read-cd' to create an image file, then burn the image with 'cdrdao write'.

Because of this one problem, I think the ~ppc-macos keyword would be appropriate for this package.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Portage 2.0.51-r15 (default-darwin/macos/10.3, gcc-3.3, libsystem-7.1-r0, 7.8.0 Power Macintosh)
===============================================================
==
System uname: 7.8.0 Power Macintosh powerpc
macos-20041118
Python:               [2.3 (#1, Sep 13 2003, 00:49:11)]
distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled]
dev-lang/python:     [Not Present]
sys-devel/autoconf:  [Not Present]
sys-devel/automake:  [Not Present]
sys-devel/binutils:  [Not Present]
sys-devel/libtool:   [Not Present]
virtual/os-headers:  7.1
ACCEPT_KEYWORDS="ppc-macos"
AUTOCLEAN="yes"
CFLAGS="-mcpu=750 -Os -mpowerpc-gfxopt -pipe"
CHOST="powerpc-apple-darwin"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/
qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=750 -Os -mpowerpc-gfxopt -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks userpriv"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/
gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="ppc cdr ncurses nls oggvorbis ppc-macos readline"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 1 Fabian Groffen gentoo-dev 2005-08-27 04:27:08 UTC
app-cdr/cdrtools-2.01-r1 is ~ppc-macos
dev-util/pccts-1.33.33 is ~ppc-macos

I don't really dare to keyword ~ppc-macos if it is so conflicting with the OS...
Comment 2 Lina Pezzella (RETIRED) gentoo-dev 2005-08-29 13:03:28 UTC
I would agree that this (cdrdao) is not working sufficiently to keyword, unless the copy option requires two 
drives or something (I don't use this).
Comment 3 Fabian Groffen gentoo-dev 2005-08-29 13:16:32 UTC
ok, closing.  Please reopen if the hardware support has improved and doesn't
require you to use a paperclip ;)