From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: The unshared changes give a problem with build after doing git pull on next Date: Fri, 26 Jul 2024 10:35:40 +0200 Message-ID: In-Reply-To: <4B595FF5-9FD8-4000-B5AF-DD40D0607F47@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9090554027380857550==" List-Id: --===============9090554027380857550== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 26/07/2024 10:17, Michael Tremer wrote: > Hello, >=20 > Hmm, this might be a slight transitioning problem=E2=80=A6 Yes, of course. >=20 > If you are now in next and build the distribution, it will likely build in = build_x86_64/ and logs will be stored in logs_x86_64/. If you run ./make.sh c= lean, those directories will be removed. I had forgotten that the new build system created the build and log dirs with= the architecture included in the name now. My next still had all the build and logs from the last build run and I did no= t do a ./make.sh clean before I did the pit pull. So the new clean was trying= to remove the build_x86_64 but I still had the build dire. >=20 > If you however change back to master, it will assume that your build is in = build/ and your logs are in logs/. If you then run clean, it will try to remo= ve those directories and since they don=E2=80=99t exist, ./make.sh clean will= return really quickly.>=20 > Is this maybe what happens? Yes. That makes sense. >=20 > You can fix this by either removing the directories by hand or changing to = next, run ./make.sh clean, then change to master and run it again. That shoul= d give you a clean tree. I will run the clean in master which will get rid of all the old named dirs a= nd then move to next with a clean structure for doing the build with the new = system. Thanks. Adolf. >=20 > Best, > -Michael >=20 >> On 26 Jul 2024, at 08:57, Adolf Belka wrote: >> >> Hi Michael, >> >> I ran git pull origin next on my local repo and then went to try a package= update build. >> >> The gettoolchain and downloadsrc worked fine. However the ./make.sh clean = just came straight back to the cursor without removing any of the directories= in my repo. >> >> I am now using my master repo version for doing the package update but som= ething has gone wrong with the unshared migration because the clean command w= orked fine when it was in your own repo. >> >> Regards, >> >> Adolf. >> >=20 --===============9090554027380857550==--