Date: Sun, 28 Jan 2024 23:04:26 +0100 From: Mario Marietto <marietto2008@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Craig Leres <leres@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org>, freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: set : illegal option -o pipefail error while trying to upgrade pkg. Message-ID: <CA%2B1FSijC-Z-1EuBp7_YVyroWAar_hDvsDLYWasV0v_t9OufCkg@mail.gmail.com> In-Reply-To: <CANCZdfopZ9zXV_ab0EWKigHoQRogHbR2nuGiT_MQRD3SmSU-9Q@mail.gmail.com> References: <CA%2B1FSijXJUDtkmf0KKEtCJ_cFhg4Htc_a=q1BWt9mtGV1T7oLw@mail.gmail.com> <CANCZdfqTdrPqswGPiku5f4ror2pxUr8MwpQPDqC15uYY8MkfkQ@mail.gmail.com> <CANCZdfp8skF24LVKcp1ygZL_zrrSAZ%2B=%2BvorhvXcE2BQCBOQFA@mail.gmail.com> <CA%2B1FSigBeH1Wm7C02OJvJ8YT6uMMOkZUEinOuaNyhKVBULfGcw@mail.gmail.com> <CA%2B1FSihbBxOmKa4gvNErrrfi4Se9yP7YB3C-=W4VTqLAYaoAqQ@mail.gmail.com> <CA%2B1FSii3zCfP=3L5BypzCPPTwsVJ2QFyXB%2Bb3VeFDBJm3eeuFQ@mail.gmail.com> <CA%2B1FSijnTFspSkdp5YA7fnaQvgUjhc=P9NEPTw4NRGOQSDCnag@mail.gmail.com> <CANCZdfrBnC-G0kG0%2BuwQKZWz2Va--Db-z3TS2td2yWisMGOx8Q@mail.gmail.com> <CANCZdfqu8dZXaRjdsn-hS2238yNZ1d36ZG8hJRx285=xBjNdHg@mail.gmail.com> <2840a1c8-839c-480f-a0db-42235bf7581e@freebsd.org> <CANCZdfopZ9zXV_ab0EWKigHoQRogHbR2nuGiT_MQRD3SmSU-9Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000009b9191061008b8d1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks. You gave me the instructions about how to upgrade pkg on FreeBSD 10 for armV6 ? This will be useful when I will install FreeBSD 10.04 (but I see that I can even install 12.04) on my Chromebook. But at the moment I'm trying to compile the only revision which allows to install FreeBSD on the Chromebook : # svnlite co http://svn.freebsd.org/base/head@269385 /usr/src directly on my old Intel I5 CPU PC,where I have installed FreeBSD 10.4 x64 = bit. So,I would need to understand how to fix the pipefail error necessary to upgrade pkg and to install xfce4 as well as some other useful ports. The idea of using the sh statically linked didn't work. I get a lot of errors and I doubt that I can fix them. Thanks. On Sun, Jan 28, 2024 at 7:18=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote: > > > On Sun, Jan 28, 2024 at 11:08=E2=80=AFAM Craig Leres <leres@freebsd.org> = wrote: > >> On 1/28/24 09:55, Warner Losh wrote: >> > On Sun, Jan 28, 2024 at 10:53=E2=80=AFAM Warner Losh <imp@bsdimp.com >> > <mailto:imp@bsdimp.com>> wrote: >> > >> > OK. On your 10.x arm system, you need to build /bin/sh using sourc= es >> > from FreeBSD 13. >> > Binaries from 12 or 13 won't work on your 10.x system: libc doesn'= t >> > have the right symbols. >> > But source build against a 10.x system should work. That was my >> > suggestion. Too bad >> > pipefail didn't arrive until 14. So you'll need to build that on >> > your 14 system. >> > >> > ... need to build stable/14 on your 10.x system this should say. Rathe= r >> > an important >> > detail I didn't catch on first proofreading. >> What about just copying /rescue/sh from a new enough system? >> >> My build server is 13.2 but it has a 14.0-RELEASE-p4 poudriere jail and >> the sh from that runs on 13.2 at least (and has pipefail). I tried to >> test with an older version of FreeBSD but it looks like my spare machine >> is too new for its usb keyboard to work with FreeBSD 10 or 11... >> > > /rescue/sh will have system calls embedded in it that the old FreeBSD 10 > kernel will not understand. Between FreeBSD 11 and 12 we moved to > 64bit inode sizes, adding a bunch of system calls that we don't fall back > to the old versions of. Plus we've added a bunch of *at system calls that > we now use always (they are more general than the old system calls, so > those have changed into library routines that call the *at function in th= e > right way). > > Warner > --=20 Mario. --0000000000009b9191061008b8d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Thanks.</div><div><br></div><div>You gave me the inst= ructions about how to upgrade pkg on FreeBSD 10 for armV6 ? This will be us= eful when I will install FreeBSD 10.04 (but I see that I can even install 1= 2.04) on my Chromebook. But at the moment I'm trying to compile the onl= y revision which allows to install FreeBSD on the Chromebook :<br></div><di= v><pre><br># svnlite co <a href=3D"http://svn.freebsd.org/base/head@269385"= >http://svn.freebsd.org/base/head@269385</a>; /usr/src<br><br></pre><pre>dir= ectly on my old Intel I5 CPU PC,where I have installed FreeBSD 10.4 x64 bit= . <br><br></pre><pre>So,I would need to understand how to fix the pipefail = error necessary to upgrade pkg<br></pre><pre>and to install xfce4 as well a= s some other useful ports.<br><br></pre><pre>The idea of using the sh stati= cally linked didn't work. I get a lot of errors and<br></pre><pre>I dou= bt that I can fix them. <br></pre><pre><br></pre><pre>Thanks.<br></pre></di= v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr= ">On Sun, Jan 28, 2024 at 7:18=E2=80=AFPM Warner Losh <<a href=3D"mailto= :imp@bsdimp.com">imp@bsdimp.com</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></di= v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On S= un, Jan 28, 2024 at 11:08=E2=80=AFAM Craig Leres <<a href=3D"mailto:lere= s@freebsd.org" target=3D"_blank">leres@freebsd.org</a>> wrote:<br></div>= <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-= left:1px solid rgb(204,204,204);padding-left:1ex">On 1/28/24 09:55, Warner = Losh wrote:<br> > On Sun, Jan 28, 2024 at 10:53=E2=80=AFAM Warner Losh <<a href=3D"ma= ilto:imp@bsdimp.com" target=3D"_blank">imp@bsdimp.com</a> <br> > <mailto:<a href=3D"mailto:imp@bsdimp.com" target=3D"_blank">imp@bsd= imp.com</a>>> wrote:<br> > <br> >=C2=A0 =C2=A0 =C2=A0OK. On your 10.x arm system, you need to build /bin= /sh using sources<br> >=C2=A0 =C2=A0 =C2=A0from FreeBSD 13.<br> >=C2=A0 =C2=A0 =C2=A0Binaries from 12 or 13 won't work on your 10.x = system: libc doesn't<br> >=C2=A0 =C2=A0 =C2=A0have the right symbols.<br> >=C2=A0 =C2=A0 =C2=A0But source build against a 10.x system should work.= That was my<br> >=C2=A0 =C2=A0 =C2=A0suggestion. Too bad<br> >=C2=A0 =C2=A0 =C2=A0pipefail didn't arrive until 14. So you'll = need to build that on<br> >=C2=A0 =C2=A0 =C2=A0your 14 system.<br> > <br> > ... need to build stable/14 on your 10.x system this should say. Rathe= r <br> > an important<br> > detail I didn't catch on first proofreading.<br> What about just copying /rescue/sh from a new enough system?<br> <br> My build server is 13.2 but it has a 14.0-RELEASE-p4 poudriere jail and <br= > the sh from that runs on 13.2 at least (and has pipefail). I tried to <br> test with an older version of FreeBSD but it looks like my spare machine <b= r> is too new for its usb keyboard to work with FreeBSD 10 or 11...<br></block= quote><div><br></div><div>/rescue/sh will have system calls embedded in it = that the old FreeBSD 10</div><div>kernel will not understand. Between FreeB= SD 11 and 12 we moved to</div><div>64bit inode sizes, adding a bunch of sys= tem calls that we don't fall back</div><div>to the old versions of. Plu= s we've added a bunch of *at system calls that</div><div>we now use alw= ays (they are more general than the old system calls, so</div><div>those ha= ve changed into library routines that call the *at function in the</div><di= v>right way).<br></div><div><br></div><div>Warner <br></div></div></div> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Mario.<br></d= iv> --0000000000009b9191061008b8d1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSijC-Z-1EuBp7_YVyroWAar_hDvsDLYWasV0v_t9OufCkg>