Date: Sun, 20 Dec 2009 18:34:44 +1300 (NZDT) From: Atom Smasher <atom@smasher.org> To: Pav Lucistnik <pav@FreeBSD.org> Cc: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/141450: audio/lmms port - does not build Message-ID: <20091220053406.13466.qmail@smasher.org> In-Reply-To: <1261264093.47091.16.camel@hood.oook.cz> References: <200912182001.nBIK1cCY088312@freefall.freebsd.org> <20091219020747.16133.qmail@smasher.org> <1261225000.31548.37.camel@hood.oook.cz> <20091219212033.91144.qmail@smasher.org> <1261264093.47091.16.camel@hood.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Dec 2009, Pav Lucistnik wrote:
> What is conflicting with what?
>
> Atom Smasher p??e v ne 20. 12. 2009 v 10:21 +1300:
>> build conflicts:
>> x11/kdelibs3-nocups (as noted)
>> x11/kdelibs3 (presumably)
>> x11-toolkits/fltk (breaks later in the build)
======================
i dunno... i ~think~ there's a naming collision of header files between
/usr/ports/audio/lmms/work/ and /usr/local/include/.
i just followed my nose, got some good hunches, and made some good
guesses. that lead to de-installing x11/kdelibs3-nocups which got me past
the first fatal error and x11-toolkits/fltk which got me past the next
fatal error. if my suspicion is correct, then 1) there may be other ports
which cause a conflict and 2) the path used to find header files in the
build environment is hosed.
can anyone confirm that on a fresh install those ports will cause lmms
build to fail?
--
...atom
________________________
http://atom.smasher.org/
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
"In fact a vegan driving a hummer would be contributing
less greenhouse gas carbon emissions than a meat eater
riding a bicycle."
-- Capt Paul Watson, A Very Inconvenient Truth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091220053406.13466.qmail>