Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 May 2023 15:00:52 +0200
From:      Yuri <yuri@aetern.org>
To:        questions@freebsd.org
Subject:   Re: The port build failed claiming a runtime dependency on libmuffin.
Message-ID:  <49ccaa55-7bee-8496-456b-be0b3948599a@aetern.org>
In-Reply-To: <2f04cc27-85ae-0f93-cd18-7ff93b0b0db0@Gmail.com>
References:  <b2f66c2c-f671-15fc-0b61-872abd0a75df@Gmail.com> <21b620c0-53db-c45f-3f18-9bbcbd547c45@aetern.org> <2f04cc27-85ae-0f93-cd18-7ff93b0b0db0@Gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Steven Friedrich wrote:
> On 5/8/23 5:02 AM, Yuri wrote:
>> Steven Friedrich wrote:
>>> I had installed cinnamon.  I went to the port to reinstall.  The port
>>> build failed claiming a runtime dependency on libmuffin.
>> You need to provide actual build output with exact errors to get any
>> helpful answers.
>>
>>> So why is cinnamon allowed to be installed as a package without
>>> libmuffin?  How is this port being built on FreeBSD's build clusters?
>> The dependency is called x11-wm/muffin and it's recorded in
>> x11/cinnamon/Makefile.
>>
> Respectfully, you're missing the point.  How can libmuffin be a
> dependency when it's not in our ports tree?  How does the freebsd team
> build cinnamon?  And why is a runtime dependency breaking a build?

Did you read my reply completely? Why - because it's not runtime-only
dependency; try looking in the port Makefile.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49ccaa55-7bee-8496-456b-be0b3948599a>