From nobody Mon Jul 27 02:43:57 2026 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4h7jbW3y18z6mNQ4 for ; Mon, 27 Jul 2026 02:44:07 +0000 (UTC) (envelope-from kargls@comcast.net) Received: from resqmta-a2p-658916.sys.comcast.net (resqmta-a2p-658916.sys.comcast.net [IPv6:2001:558:fd01:2bb4::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4h7jbV3hYtz3ZZj for ; Mon, 27 Jul 2026 02:44:06 +0000 (UTC) (envelope-from kargls@comcast.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=comcast.net header.s=20190202a header.b=Ns4CaRRT; spf=pass (mx1.freebsd.org: domain of kargls@comcast.net designates 2001:558:fd01:2bb4::2 as permitted sender) smtp.mailfrom=kargls@comcast.net; dmarc=pass (policy=reject) header.from=comcast.net Received: from resomta-a2p-647653.sys.comcast.net ([96.103.145.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-a2p-658916.sys.comcast.net with ESMTPS id oBEYwbQSEDUk7oBJvwzkG3; Mon, 27 Jul 2026 02:43:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1785120239; bh=4JNSjezvXVPn4kPVWvtDhGKices7McQDJ7sBmgDwH+0=; h=Received:Received:Message-ID:Date:MIME-Version:Subject:To:From: Content-Type:Xfinity-Spam-Result; b=Ns4CaRRT/SnqmKZ6M/xNaIdtsrZul0RbHaRCWd+4yttKoO4/MDrjHZI6oPCntZHEN AcBI8A9xdkkUSVRXEKt8s0KCddssnY0r98D7WmALV3Lx+MYzFDqopcLFQ4cHgbo3aG cARbrZQO/a1FkPC5x0PS2jVXg1kwSdkGWnsynwzeJuzMdqSxPthlO+bKzPQ3Bz0T2F iTAq0+KzgZkgxmRxnZgo3+bqCXMpD0GchjXRW0dTItuX5nm6WPfMYK+PjFb9qFCWJO FOQ6Z0+LYAEb2p6s/WxHnr+lZsuzY5Jf7bJQKq77W5LX7jaGxvGV41wG8N9q5n9LxQ 59D1DsQHmWuGg== Received: from [10.0.0.31] ([73.97.237.216]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resomta-a2p-647653.sys.comcast.net with ESMTPSA id oBJuwsfuqfL7yoBJuw2OWz; Mon, 27 Jul 2026 02:43:59 +0000 Xfinity-QID: oBJuwsfuqfL7yoBJuw2OWz Xfinity-Graffiti: 67602080926 Message-ID: Date: Sun, 26 Jul 2026 19:43:57 -0700 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: What is a FLAVOR and how to unbreak ports? To: ports@freebsd.org References: <6ce75735-75f7-4852-814c-91b8105692e6@comcast.net> Content-Language: en-US From: Steve Kargl In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfETRCSI/pCgHpFxykiidCTUoerEYNQKg1Z6UZznahmp4CNk0x11DoUzUa0DCfA1WzjUyuQPb0zfKj4pUW/oXaZS+DE/3LsjdG+rfO/EP+QCtRYptsLJW T0mnOYaqnZ82U/dsnXn4a6dkWyJgvjnlVVs3kWgwVSzQ6u5JvdImzsD9kjlw28+fxrshq78XKkv0JQ== X-Spamd-Result: default: False [0.00 / 15.00]; HFILTER_HELO_5(3.00)[resqmta-a2p-658916.sys.comcast.net]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[comcast.net,reject]; R_DKIM_ALLOW(-0.20)[comcast.net:s=20190202a]; R_SPF_ALLOW(-0.20)[+ip6:2001:558:fd01:2bb4::/64]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_NONE(0.00)[comcast.net:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[comcast.net]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[comcast.net]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[comcast.net:+]; MLMMJ_DEST(0.00)[ports@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:7922, ipnet:2001:558::/29, country:US]; RCVD_IN_DNSWL_NONE(0.00)[96.103.145.229:received] X-Rspamd-Queue-Id: 4h7jbV3hYtz3ZZj X-Spamd-Bar: / On 7/26/26 18:41, Edward Sanford Sutton, III wrote: >   Flavors are a way to have separate packages created for different > configurations of a port. That way users of pkg do not need to go > manually build software for relatively common software variation > possibilities that they may want or need in place of a single default > set of options. Yeah, I read the porter's documentation. I could not find where it mentions a comprehensive list of the FLAVORs. There is no discussion of how one can query for the list of FLAVORs. > On 7/26/26 13:18, Steve Kargl wrote: >> On 7/26/26 12:51, Gleb Popov wrote: >>> On Sun, Jul 26, 2026 at 10:43 PM Steve Kargl wrote: >>>> >>>> Hi, >>>> >>>> Updating a laptop that had a year old FreeBSD on it >>>> to top-of-tree. >>>> >>>> % portmaster -Byd --force-config sqlite3 |& tee sgk.log >>> >>> Try updating libclc first using portmaster or plain make. >> >> I did try plain make in libclc.  See the end of original email. >> make dies with an error about llvm15 no longer being supported. >> If llvm15 is no longer supported on fbsd 16, then the libclc >> Makefile should simply skip trying to build for llvm15. >> >>> Figure out what flavor you need by looking at the installed package's >>> name >> >> That's the question.  What is a FLAVOR and how do I determine what >> FLAVOR is the right flavor? >> >>> pkg info -x libclc >>> >>> If going the plain make route, append FLAVOR=llvmXY to make invocation. >> >> Is there a comprehensive list of FLAVORs?  'man make.conf' does not >> mention FLAVOR.  Is it possible to set FLAVORS there? > >   Flavors are a property of each port individually and not an > externally defined property; some different ports use common flavors > like 'nox11' but there is no hard rule to it. In the ports tree you can > list flavors with `make -C /usr/ports/devel/libclc -VFLAVORS` and drop - > C if you run it in the port's folder. Well, that's inconvenient, but that make command should be provided in the porter's documentation. At the moment, portmaster dies with some mystery error. Going to /usr/ports/devel/libclc and type 'make' leads to all sorts of fun. libclc dies because llvm15 is no longer supported; so, well, the port shouldn't even try to build that flavor. >   For manually running make, `make -C /usr/ports/devel/libclc > FLAVOR=llvm17` would be an example of overriding it. Not sure if there > are other ways to express it. That's the problem. There are apparently 8 flavors. How do I determine I need llvm17 instead of llvm20? >   Some changes I assume should happen: >   1. The default of libclc should be reconsidered if it is broken on a > platform unless it is being actively worked on. Why are we defaulting to > the oldest compiler, a compiler not included as a base compiler on any > supported FreeBSD version, and not even having a comment as to why? Good question. >> In the old days, one could cd into any directory under /usr/port >> and simply type 'make'. > >   Unless things are broken. Having been building things since 2004, you > can usually find broken things when you look. I've been building ports since its inception. In fact, I was the maintainer for lang/f2c and few others prior to the creation of portmgr. portmgr broke lang/f2c, I received daily complaints it was broken, and it only wasted a few weeks of my time trying to figure out what portmgr did. I dropped maintainership decades ago due to that experience. at over 30,000 port > folders, its hard to have the tree in a state where 'nothing' fails. Sure, I find a number of issues every time I need to rebuild ports. I fix/workaround the issue and move on with life. The math/arpack-ng port now has a mpich and openmpi flavor, because I got tired of editing out the hardcoded use of mpich and asked for either 'none' or 'openmpi' build option. Unfortunately, math/octave has a hardcoded dependency on arpack-ng@mpich. Fun times. >> My actual problem is building devel/node24, which dies with an >> error: >> ld.lld: error: undefined symbol: sqlite3session_patchset. > >   I'd have to see a more complete error log to guess properly. I've found a fix. It seems that node24 requires sqlite3 built with the sessions compile option set. For some reason, it was unset when I last built it on my system. I suppose default options change over time. -- steve