Re: set : illegal option -o pipefail error while trying to upgrade pkg.
- In reply to: Jamie Landeg-Jones : "Re: set : illegal option -o pipefail error while trying to upgrade pkg."
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 01 Feb 2024 12:07:49 UTC
Hello Jamie, thanks. I don't know if you read my last email,but I have cut the problem at the root,by using the old version of the Mk Scripts,to be sure that it didn't have the pipefail parameter. I did like this because your script probably didn't remove some of those references and I got the same error. Unfortunately,when I tried to upgrade the port "pkg" to 1.20.9 I got a compilation error. I'm not able to upgrade the whole system until I'm not able to upgrade it. The error that I need to fix is : Invoked as: ./configure --prefix=/usr/local Tclsh: /usr/ports/ports-mgmt/pkg/work/pkg-1.20.9/jimsh0 Failed: cc -O2 -pipe -Wno-error -fstack-protector-strong -fno-strict-aliasing -c conftest__.c -o conftest__.o cc: error: unknown argument: '-fstack-protector-strong' ============ The failed code was: #include <stdlib.h> int main(void) { return 0; } ============ On Thu, Feb 1, 2024 at 12:42 PM Jamie Landeg-Jones <jamie@catflap.org> wrote: > Mario Marietto <marietto2008@gmail.com> wrote: > > > Can you tell me where should be stored the references to pipefail ? > Maybe I > > will try to remove them manually. Maybe your command does not work out of > > the box. > > I juat tested it on an old 11.1 box and it worked. The various files are > the > ones listed in the command, under /usr/ports/Mk/Scripts - there are about > 22 > that contain mentions of pipefail, though not all will be relevent to your > particilar cases. > > Yes, you can manually just delete the "set +o pipefail" and "set -o > pipefail" > commands as you find them, not forgetting the caveat mentioned in the > previous mail that you may miss some errors that may occur during building. > -- Mario.