From owner-freebsd-ports@FreeBSD.ORG Mon Oct 17 20:19:16 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75DDE106566B for ; Mon, 17 Oct 2011 20:19:16 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 3862A8FC15 for ; Mon, 17 Oct 2011 20:19:15 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p9HKJFCP052325; Mon, 17 Oct 2011 14:19:15 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p9HKJE9Z052324; Mon, 17 Oct 2011 14:19:14 -0600 (MDT) (envelope-from ken) Date: Mon, 17 Oct 2011 14:19:14 -0600 From: "Kenneth D. Merry" To: Kevin Oberman Message-ID: <20111017201914.GA52299@nargothrond.kdm.org> References: <20111012033304.GA48367@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: ports@freebsd.org Subject: Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2011 20:19:16 -0000 On Sun, Oct 16, 2011 at 15:20:22 -0700, Kevin Oberman wrote: > On Tue, Oct 11, 2011 at 9:00 PM, Kevin Oberman wrote: > > On Tue, Oct 11, 2011 at 8:33 PM, Kenneth D. Merry wrote: > >> On Tue, Oct 11, 2011 at 15:52:35 -0700, Kevin Oberman wrote: > >>> > On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote: > >>> > > Just a note to say that recent changes on -CURRENT (r225950, meaning > >>> > > that it is probably broken on 9.0 after r226067) have broken > >>> > > audio/cdparanoia, and it should be fixed or marked as BROKEN there. ?I > >>> > > haven't filed a PR, or attempted to patch it yet -- I think that it > >>> > > would be worthwhile to look into moving to 10.2, which has a large > >>> > > number of improvements, although suffering from some Linuxisms. > >>> > > >>> > This will be easy to patch, using one of two methods: > >>> > > >>> > ?- change struct scsi_sense_data to struct scsi_sense_data_fixed > >>> > or, better yet: > >>> > ?- use scsi_extract_sense_len(), which will work for fixed or descriptor sense. > >>> > >>> Ken, > >>> > >>> OK. I have grepped through all of the cdparanoia sources and fine no > >>> instances of scsi_sense_data. Where in the heck do I find it so I can > >>> get this port built? 10.2 would be lovely, but I just need cdparanoia > >>> on 9-stable quickly and I fear that hte package will no longer work > >>> after r226067. > >> > >> There is no FreeBSD support in cdparanoia by default. ?It is patched in by > >> the ports system. > >> > >> Go into the directory for the port, do a 'make fetch' and then 'make patch'. > >> > >> Then go into cdparanoia-III-alpha9.8/interface and copy the attached file > >> on top of scsi_interface.c. > >> > >> I've checked that it compiles on a system running code before the change, > >> but I think that change should work for systems before or after the change. > >> > >> Let me know whether it works for you. > > > > Thanks so much! > > > > Yes, the new scsi_interface.c compiled cleanly and cdparanoia built > > and installed. > > > > I am in the process of re-building all ports after I upgraded my > > system to 9-stable, so I really can't plug in my CD and try ripping > > aomething right now, but I'll try soonand let you know how it worked. > > Finally got all of my ports installed and re-booted with the DVD > installed. Sorry to have taken so long, but rebuilding over 1600 ports > on an old, slow laptop takes a lot of time and I had to tweak several > port to get them to build. > > With the modified scsi_interface.c file you sent, cdparanoia seems to > be working just fine. > > Thanks! Great, glad to hear it! > Should I submit a PR with the new file? Yes. I'm not a ports committer, it would be better for one of them (ideally the mantainer, if any) to go in and fix it. Ken -- Kenneth Merry ken@FreeBSD.ORG