public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hartmut Figge <h.figge@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: xcdroast 0.98alpha16: Empty CD
Date: Thu, 14 Dec 2017 14:23:13 +0100	[thread overview]
Message-ID: <afb4aa11-3732-00e8-74ea-8c3bdb26ceab@hfigge.myfqdn.de> (raw)
In-Reply-To: <5a325151.mM4+/XfKyt3UsX3W%Joerg.Schilling@fokus.fraunhofer.de>

Joerg Schilling:
>Hartmut Figge <h.figge@gmx.de> wrote:

>> Starting xcdroast with -d 10 shows the problem:
>>
>> DGB1: spawning: /usr/lib/xcdroast-0.98/bin/xcdrwrap CDDA2WAV -D "2,1,0"
>> -J -g -Q -H -v toc,summary,sectors,titles
>> DGB10: readtoc: cdda2wav: Invalid argument. Cannot open output fd 0.
>
>This is a bug in cdda2wav that only hits when compiled in 64 bit mode. For this 
>reason, it has not been detected for a long time as Solaris by default uses 32 
>Bit applications as 64 bit application on an orthogonal CPU are usually 
>slower...

Ah, therefore it doesn't occur in a chroot to an old Gentoo.

>The bug has been fixed on March 28, 2017 and published in schilytools.
>
>Today, I published a separate source ball cdrtools-3.02a09.

Thanks, Joerg. In the meantime I had played a little, for the first
time, with an overlay to get the exact versions of the relevant programs
and was a little baffled that it didn't help.

I can imagine that finding the issue was tricky.

Hartmut



  reply	other threads:[~2017-12-14 13:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 18:36 [gentoo-user] xcdroast 0.98alpha16: Empty CD Hartmut Figge
2017-12-13 20:53 ` Helmut Jarausch
2017-12-13 21:24   ` [gentoo-user] " Hartmut Figge
2017-12-14 10:26     ` Joerg Schilling
2017-12-14 10:30     ` Helmut Jarausch
2017-12-14 11:55       ` Joerg Schilling
2017-12-14 10:24 ` [gentoo-user] " Joerg Schilling
2017-12-14 13:23   ` Hartmut Figge [this message]
2017-12-14 15:06     ` [gentoo-user] " Joerg Schilling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=afb4aa11-3732-00e8-74ea-8c3bdb26ceab@hfigge.myfqdn.de \
    --to=h.figge@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox