From nobody Wed Jan 31 14:31:11 2024 X-Original-To: freebsd-questions@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 4TQ4HC6n2xz58dQJ; Wed, 31 Jan 2024 14:31:51 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TQ4HB5x6wz4t5j; Wed, 31 Jan 2024 14:31:50 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-55efbaca48bso5030626a12.2; Wed, 31 Jan 2024 06:31:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706711509; x=1707316309; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=eoJG7eRx8UCNhJks2Uuc52pkrPBfBeUlZnKeYHOjVcA=; b=cZnFfuMLnB5BCxOjCXhOiMhFSqy0RC+rRHOU8Xvi4az+yl1vnRus9k4UP+AGXTUcHi QrjK0DU8nCTEL2gaeUEDG34AVRgJuVOGirHCKtfQQ9j6XT/hwHi4cOcSyUdhN5T5rFY5 bg2J/GhHA1Mdy/zmc2TOZGvtQe9N06T5w/NMmnHDrDJmqXBEe9c+8OITjtVA67RanLfK qO+8asOaxTVQ74CYhUvGu3FdPZE5mzhMatPFHmu9W5fiIdzU7MQpbZskf/mFa8xvqeid q5XFV9LeZ+iNbsOYByDcySPn8Q4xMvIOJ7K7XHkghlvHaTxKZXixk90mlE83Mx1akk8X bUow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706711509; x=1707316309; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eoJG7eRx8UCNhJks2Uuc52pkrPBfBeUlZnKeYHOjVcA=; b=SnR8XyU+DPVQi2HAMlqUyFSixxiuzzQpgZFc9iDnPY+hE27smtbrCKtZn9nr99JiWg soO/mTTwr+A+j8KKjee2/5Sw3lymOM1W1kLAqiqJIqGXOJ5YHnE7DMUqyuq3/3bEHLtA bGZI6m6ZZ6l93SuKJCO5Owaojkpdgf8+LIdxh2O0curU6XHf03+SRd2WQE7dwhppu7nz Exeva9b9H7/N7NTCsxTMzI58WtOvSI6I/eniZ5/nxcRTzFMXM22JFW1L5pVE4/6D/PGx kMPVYNsPZoOl6CvgJ82plyR17D6zZ4u2OpnWuYi1oIfCL0h3z5iS76dZ2KHixANBPzAp tnKQ== X-Gm-Message-State: AOJu0Yyqk3ADgkqle88Wcs/gTHijzR6Pk7RAQu4dLl9cqKeHKLUOSasi uPpX4aWB4U8kSCH9LnXpQHIB3QtAbgUuh5Y8lz0foEkQ41KVy6gn1sxze4UOD0Y9P39s4txmYEi qhrIpoC/22FU0o8c/gwrQk9HcOAbbw6lk X-Google-Smtp-Source: AGHT+IG+ZRGnnZEtWCecd9klWcDLaN6sJw1IxQBzOogur4r/WvRDoR+jOQ47j/a8QS7IkfWGXlgXkJDXC9sVB5DDcqA= X-Received: by 2002:a17:906:3b19:b0:a35:7192:1f with SMTP id g25-20020a1709063b1900b00a357192001fmr1352702ejf.49.1706711509146; Wed, 31 Jan 2024 06:31:49 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <80d527f-df83-5657-6a2a-262156e08440@puchar.net> <202401311216.40VCGZSo001051@donotpassgo.dyslexicfish.net> In-Reply-To: <202401311216.40VCGZSo001051@donotpassgo.dyslexicfish.net> From: Mario Marietto Date: Wed, 31 Jan 2024 15:31:11 +0100 Message-ID: Subject: Re: set : illegal option -o pipefail error while trying to upgrade pkg. To: Jamie Landeg-Jones Cc: wojtek@puchar.net, freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="0000000000003ca13206103ebd00" X-Rspamd-Queue-Id: 4TQ4HB5x6wz4t5j X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --0000000000003ca13206103ebd00 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Jamie, I ran your script and it gave no error message,BUT I still got the error : root@marietto:/usr/ports/ports-mgmt/pkg # make set: illegal option -o pipefail.... ? On Wed, Jan 31, 2024 at 1:16=E2=80=AFPM Jamie Landeg-Jones wrote: > Mario Marietto wrote: > > > What I haven't understood is why you are talking about newer ports when > the > > only thing I do is to update ports using the same FreeBSD version,in th= is > > case 10.4. I mean,upgrading ports without upgrading the version of > > FreeBSD,can't mean to use newer ports,since I don't use a newer version > of > > the OS. > > The ports infrastucture (under /usr/ports/Mk) now contains scripts that s= et > the "pipefail" option - these scripts are updated when you update the por= ts > tree. > > I had an old out-of-date box for a while, and used this quick hack to get > it to work. > > You need to run this after you update the ports tree: > > sed -i.bak '/^[[:space:]]*set [+-]o pipefail/d' /usr/ports/Mk/Scripts/* > > It removes the references to pipefail. This can mean that some build erro= rs > are potentially not trapped, but if that's the case you're likely to noti= ce > the failure anyway. > > Still best to update your system or your /bin/sh though! > > Cheers, Jamie > --=20 Mario. --0000000000003ca13206103ebd00 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Jamie,

I ran your script and= it gave no error message,BUT I still got the error :=C2=A0

<= /div>
root@marietto:/usr/ports/ports-mgmt/pkg # make
set:= illegal option -o pipefail....

?
<= br>
On Wed,= Jan 31, 2024 at 1:16=E2=80=AFPM Jamie Landeg-Jones <jamie@catflap.org> wrote:
Mario Marietto <marietto2008@gmail.com> wrote= :

> What I haven't understood is why you are talking about newer ports= when the
> only thing I do is to update ports using the same FreeBSD version,in t= his
> case 10.4. I mean,upgrading ports without upgrading the version of
> FreeBSD,can't mean to use newer ports,since I don't use a newe= r version of
> the OS.

The ports infrastucture (under /usr/ports/Mk) now contains scripts that set=
the "pipefail" option - these scripts are updated when you update= the ports
tree.

I had an old out-of-date box for a while, and used this quick hack to get it to work.

You need to run this after you update the ports tree:

sed -i.bak '/^[[:space:]]*set [+-]o pipefail/d' /usr/ports/Mk/Scrip= ts/*

It removes the references to pipefail. This can mean that some build errors=
are potentially not trapped, but if that's the case you're likely t= o notice
the failure anyway.

Still best to update your system or your /bin/sh though!

Cheers, Jamie


--
Mario.
--0000000000003ca13206103ebd00--