Date: Fri, 14 Apr 2023 07:09:43 +0200 From: Milan Obuch <freebsd-multimedia@dino.sk> To: Robert Huff <roberthuff@rcn.com> Cc: freebsd-multimedia@freebsd.org Subject: Re: problem building gstreamer1-plugins-bad Message-ID: <20230414070943.47558c69@zeta.dino.sk> In-Reply-To: <25656.53471.337608.569473@jerusalem.litteratus.org> References: <25656.42433.922749.696527@jerusalem.litteratus.org> <20230414044244.37340cb3@zeta.dino.sk> <25656.53471.337608.569473@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Apr 2023 00:04:47 -0400 Robert Huff <roberthuff@rcn.com> wrote: > Milan Obuch <freebsd-multimedia@dino.sk>: > > > This is described in 20221015 entry in UPDATING > > (/usr/ports/UPDATING) - in a nutshell, there is probably change in > > some header file making some collision using already installed > > header file instead of the one comming from sources being compiled. > > I just encountered it as well, it is possible to overcome it by > > removing the old one using > > pkg delete -f gstreamer1-plugins-bad-1.20.6 > > > > and then doing the build, in my case with > > > > portmaster multimedia/gstreamer1-plugins-bad > > > > but use what are used to use here instead :) > > That did it! <sound of multiple blocked ports building ....> > I looked in UPDATING, but not that far back. Silly me. > Thanks. > Glad it helps. Probably at the time this was added to UPDATING, there was another version update, but the root cause and solution were the same, so I pointed at it as another bit of info. Regards, Milan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230414070943.47558c69>