From owner-freebsd-ports@FreeBSD.ORG Sun Apr 18 23:30:47 2010 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 152861065676; Sun, 18 Apr 2010 23:30:47 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id AD5C18FC14; Sun, 18 Apr 2010 23:30:46 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 5so1385258qwi.7 for ; Sun, 18 Apr 2010 16:30:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=DvL4qTBNvBpsH2nEq2MnFRDF9xJ/+x9bXE26E1ky82w=; b=KEVQZQbUOkfOy5uw1bgK9DpUjR+tJAuOg47fQv4d4Sh4hFqyPwZWEdjris7ru7PYMP cxdMKytlD/VBhEfw5OCbIDuI0QuTAyGn11FwvxbRc3LYB4/eRsHJ/owoblBY2gNwJwFM rTzumNjYy5BhR2aMJ6TcF+UZIA4Bu02m3asdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=E9cEOsfTDt63fOY9BkH4Uzae5AAeT1KkTRGJlPEVDkFFkFdx5ea2BGGagYVh1lVr9n g4cbIF0BeU77swcX91T+bA6r199eB+wVJEqWNHbQSLZJjBiAsFinehhOOvDGFj8GCST2 XOBL3MhPOU5/o+jOmALNlZfcrBdA9HovUu3TQ= MIME-Version: 1.0 Received: by 10.229.28.85 with HTTP; Sun, 18 Apr 2010 16:30:45 -0700 (PDT) In-Reply-To: <4BCB7DA9.40105@FreeBSD.org> References: <4BCAAB3F.5020407@FreeBSD.org> <4BCB7DA9.40105@FreeBSD.org> Date: Sun, 18 Apr 2010 16:30:45 -0700 Received: by 10.229.216.76 with SMTP id hh12mr1763916qcb.47.1271633445843; Sun, 18 Apr 2010 16:30:45 -0700 (PDT) Message-ID: From: Garrett Cooper To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: Xin LI , jsa@wickedmachine.net, freebsd-ports@freebsd.org Subject: Re: VLC does not support the audio or video format "XVID". 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: Sun, 18 Apr 2010 23:30:47 -0000 On Sun, Apr 18, 2010 at 2:46 PM, Doug Barton wrote: > On 04/17/10 23:48, Doug Barton wrote: >> I recently updated -current, and all of my ports, and am now getting the >> following message when I try to watch an avi file encoded with xvid: >> >> No suitable decoder module: >> VLC does not support the audio or video format "XVID". Unfortunately >> there is no way for you to fix this. >> >> Recompiling vlc, xvid, and numerous other things didn't help. Any >> suggestions? > > I have found the problem, it's zlib. In r206708-9 delphij updated zlib > to version 1.2.4.3 and did some magic with the symbols. I just regressed > my system to r206707 and now the same vlc does xvid just fine. > > When I booted the new -current yesterday (after the libz changes) I had > to rebuild and reinstall openbox and libxml2 because the latter had some > sort of unresolved symbol problem related to libz. When I regressed the > system today and had to do the same thing I got this error: > /usr/local/lib/libxml2.so: undefined reference to `gzopen@ZLIB_1.2.4.0' > > (Note, this libxml2 that generated this error was compiled against the > NEW libz, so it's not the error that I was seeing previously.) > > In looking over the things in /usr/lib that may be related I see that > gpac-libgpac-0.4.5_4,1 has the gzopen symbol, and I did not recompile > that when I was trying to get vlc to work last night so it may be the > magic bullet. > > My plan at this point is to re-upgrade to the latest -current, record > the error I get from libxml2 when recompiling openbox, and then try > recompiling stuff until I find the one that does the trick. Worst case > scenario I do 'portmaster -f vlc' but that constitutes 175 ports, which > would take a while. Yeah... that's what I thought it was. vlc does some interesting work initializing codecs I think where it disguises runtime linker issues, etc with pieces that tie into vlc. Not really happy about that, but after the issue with zlib was identified 2~3 weeks ago, it was easy to clean up... The other issues with zlib are pretty well known, and the overall upgrade as I and others mentioned a few weeks back is large as it's use is pervasive in 3rd party software. HTH, -Garrett