From nobody Fri Sep 3 10:11:29 2021 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 57E4417A18F1 for ; Fri, 3 Sep 2021 10:11:42 +0000 (UTC) (envelope-from ps.ports@smyrak.com) Received: from ipv6.s149.cyber-folks.pl (ipv6.s149.cyber-folks.pl [IPv6:2a02:1778:113::68:149]) (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 4H1D993TLpz3Bmm for ; Fri, 3 Sep 2021 10:11:41 +0000 (UTC) (envelope-from ps.ports@smyrak.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyrak.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=mhfxcOksDJ5xSSE+B3XeIQkxN2TjyIIuuO6FsCj/Rok=; b=jnVpsnbzXnvHN1PI/zct8zgUNR 6fYhJ2zwANrJFU3leMEAmuFRRmR3ch9WUpga449zNIA2Xt/+vElnlbPW0ZK6+RdQkMs2VJV88m4HI I+PmlPtmpOW66Q6Z0KOQkGXnCKWCElGEe5Ob3fJvCkZwwZ3nqogRAEpTBEaZ5u7pmurl4O5nOCAyd J82aMg5dHwtAsfTtNmXNiAoRcS34CIO8OZMiDtR4BPBz5CLlAVPqeyNxWh3Umwaf0us1BqDOUPRYM IGgkS507HiozLkPvka3nx1HPwY/awt8rw8ApRcGcMrLkHKlJGbKUxXZEZ5Z/rjiUxzOGVQ1F2juWQ 7Y3Eq9GQ==; Received: from 93-181-165-201.internetia.net.pl ([93.181.165.201] helo=daleth.home) by s149.cyber-folks.pl with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1mM6Ae-00Avhq-FS for ports@freebsd.org; Fri, 03 Sep 2021 12:11:40 +0200 Date: Fri, 3 Sep 2021 12:11:29 +0200 From: Piotr Smyrak To: ports@freebsd.org Subject: Re: Odd whine from grep in www/chromium? Message-ID: <20210903121129.1fc20075@daleth.home> In-Reply-To: References: X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; amd64-portbld-freebsd12.2) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authenticated-Id: piero@smyrak.com X-Rspamd-Queue-Id: 4H1D993TLpz3Bmm X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=smyrak.com header.s=x header.b=jnVpsnbz; dmarc=pass (policy=none) header.from=smyrak.com; spf=pass (mx1.freebsd.org: domain of ps.ports@smyrak.com designates 2a02:1778:113::68:149 as permitted sender) smtp.mailfrom=ps.ports@smyrak.com X-Spamd-Result: default: False [-1.06 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:1778:113::/48]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(0.74)[0.737]; DKIM_TRACE(0.00)[smyrak.com:~]; DMARC_POLICY_ALLOW(-0.50)[smyrak.com,none]; R_DKIM_PERMFAIL(0.00)[smyrak.com:s=x]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:41079, ipnet:2a02:1778::/32, country:PL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 2 Sep 2021 16:16:44 -0600 Adam Weinberger wrote: > On Thu, Sep 2, 2021 at 12:29 PM David Wolfskill > wrote: > > > It doesn't seem to cause a real "problem," but... it doesn't look > > quite ideal, either: > > > > E.g.: > > g1-48(12.2-S)[1] cd /usr/ports/www/chromium/ > > g1-48(12.2-S)[2] make showconfig > > make: "/common/ports/www/chromium/Makefile" line 210: warning: > > "/usr/bin/grep mempcpy /usr/include/string.h" returned non-zero > > status ===> The following configuration options are available for > > chromium-92.0.4515.159_1: > > CODECS=on: Compile and enable patented codecs like H.264 > > CUPS=on: CUPS printing system support > > DEBUG=off: Build with debugging support > > DRIVER=on: Install chromedriver > > KERBEROS=on: Kerberos support > > LTO=off: Use Link-Time Optimization > > TEST=off: Build and/or run tests > > ====> Options available for the group AUDIO > > ALSA=on: ALSA audio architecture support > > PULSEAUDIO=off: PulseAudio sound server support > > SNDIO=off: Sndio audio support > > ====> Kerberos support: you can only select none or one of them > > HEIMDAL=off: Heimdal Kerberos (security/heimdal) > > HEIMDAL_BASE=off: Heimdal Kerberos (base) > > MIT=off: MIT Kerberos (security/krb5) > > ===> Use 'make config' to modify these settings > > g1-48(12.2-S)[3] > > > > (I see the message several times when working with ports -- e.g., > > during "portmaster -Fa" or "portmaster -da", as well as just after > > building the port successfully: > > > > ... > > For more information, and contact details about the security > > status of this software, see the following webpage: > > https://www.chromium.org/Home > > > > make: "/common/ports/www/chromium/Makefile" line 210: warning: > > "/usr/bin/grep mempcpy /usr/include/string.h" returned non-zero > > status make: "/common/ports/www/chromium/Makefile" line 210: > > warning: "/usr/bin/grep mempcpy /usr/include/string.h" returned > > non-zero status ===>>> Upgrade of chromium-92.0.4515.159 to > > chromium-92.0.4515.159_1 succeeded > > > > ===>>> Returning to update check of installed ports > > > > ===>>> Update check of installed ports complete > > > > ===>>> The following actions were performed: > > Upgrade of chromium-92.0.4515.159 to > > chromium-92.0.4515.159_1 > > > > ) > > > > Environment: > > g1-48(12.2-S)[3] uname -aUK > > FreeBSD g1-48.catwhisker.org 12.2-STABLE FreeBSD 12.2-STABLE #1108 > > stable/12-n233711-e99900847a5: Thu Sep 2 03:31:49 PDT 2021 > > root@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1202508 1202508 > > > > g1-48(12.2-S)[5] gen_fbsd_git_tag -fr /usr/ports . > > main-n556810-ea698cc7edbb > > Yeah, something like grep -c may be a better option, and then check > whether the output == 0. I'm afraid this would still cause a warning, since grep exits with non zero status when no strings were found. Appending " || :" to the line 210 would prevent the negative scenario from causing a warning. -- Piotr Smyrak