Date: Sun, 08 Oct 2006 20:19:13 +1000 From: Sam Lawrance <boris@brooknet.com.au> To: Roland Smith <rsmith@xs4all.nl> Cc: freebsd-ports-bugs@FreeBSD.org, redchrom@gmail.com Subject: Re: ports/104101: multimedia/audacious 1.1.2 doesn't compile. Message-ID: <4528D0A1.9070700@brooknet.com.au> In-Reply-To: <20061008100442.GA14054@slackbox.xs4all.nl> References: <200610080627.k986RphQ079192@freefall.freebsd.org> <20061008075326.GA499@slackbox.xs4all.nl> <4528B5E7.1090003@brooknet.com.au> <20061008100442.GA14054@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Roland Smith wrote: > On Sun, Oct 08, 2006 at 06:25:11PM +1000, Sam Lawrance wrote: > > >> Thanks for that feedback. Do you have an older version of audacious >> already installed? >> > > Yes. Version 1.0.0 is installed. > > >> Looking at some of the #includes in the source, it >> might be possible that an old header is being included instead of a new >> one. If so, deinstall the old version (back it up with pkg_create -b if >> you like), and try again. >> > > That did the trick! It now compiles, installs and runs cleanly. > > Thanks very much for the help! > > What is the correct way of preventing this in the future? With most > ports, you can do a 'make' without problems, even if an older version is > already installed. My SOP is to build the port first, then 'make > deinstall' the old version, followed by a 'make install clean'. > Excellent :-) Ordinarily this problem shouldn't happen, so there's not a lot you can do to prevent it. It could be fixed in the port. The ideal fix would be from the vendor, to ensure that the build uses its own headers instead of picking up those from outside. Cheers Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4528D0A1.9070700>