From owner-freebsd-ports@FreeBSD.ORG Sat Feb 14 17:25:24 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43C13106564A for ; Sat, 14 Feb 2009 17:25:24 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id 1FEDF8FC21 for ; Sat, 14 Feb 2009 17:25:23 +0000 (UTC) (envelope-from lars@larseighner.com) Received: by mail.team1internet.com (Postfix, from userid 12346) id 9D72716B87E; Sat, 14 Feb 2009 11:25:22 -0600 (CST) Received: from larseighner.com (unknown [216.110.13.78]) by mail.team1internet.com (Postfix) with SMTP id 6C23016B876; Sat, 14 Feb 2009 11:25:20 -0600 (CST) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Sat, 14 Feb 2009 11:24:07 -0600 (CST) Date: Sat, 14 Feb 2009 11:24:00 -0600 (CST) From: Lars Eighner X-X-Sender: lars@debranded.6dollardialup.com To: Christian Weisgerber In-Reply-To: Message-ID: <20090214112354.S87224@qroenaqrq.6qbyyneqvnyhc.pbz> References: <20090213172925.R97999@qroenaqrq.6qbyyneqvnyhc.pbz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sanitizer: Anomy and SpamAssassin mail filter - see http://www.6dollardialup.com/support/spaminfo.html Cc: freebsd-ports@freebsd.org Subject: Re: Sox in 7.1 broken or corrupt? 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: Sat, 14 Feb 2009 17:25:24 -0000 On Sat, 14 Feb 2009, Christian Weisgerber wrote: > Lars Eighner wrote: > >> It appears to me the audio/sox port is broken. During configure the >> screen breaks up with a bunch of ANSI garbage. This happens again with >> the compile which seems to halt in sox.c with the message EOF in backtick >> operator. > > Giving this a quick try on -CURRENT and with all dependencies > disabled, I don't see it. sox configures and builds fine. > > If you build sox in a script(1) session and inspect the typescript > with less(1) afterwards, you should be able to see where configure > starts going wrong. Oh, I see. The config script looks for something it calls "distro name" in /etc/issue . I don't think this is the right way to get this information; my understanding was that /etc/issue could be used for any pre-login message (as motd is the post-login message). Surely uname is the right way to get what the configure script wants. At any rate, /etc/issue contained, amoung other things an ANSI portrait of Beastie, which does have a few odd backticks in it. I just did not recognise it as the script rendered it all squashed. Well, I can fix this up to build sox (the fix is as simple as renaming the existing /etc/issue -- sox will build if the file does not exist), but I think the config script is sloppy and I haven't seen this on any other ports. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266