public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with trying to do downloadsrc and build
Date: Mon, 04 Apr 2022 17:07:49 +0100	[thread overview]
Message-ID: <7C265DAC-7B3B-49BD-BC23-7756E98BA11C@ipfire.org> (raw)
In-Reply-To: <b78664a0-4c7c-cc55-945e-6c95d3f04957@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2419 bytes --]

Hello Adolf,

Yes, deleting the toolchains are re-downloading is probably the easiest fix.

I just pushed another patch to make the package download work smoothly again.

-Michael

> On 4 Apr 2022, at 13:51, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I am trying to run a build. First time for a week or so but had some problems. Build is now running but I thought I would flag up what happened so far.
> 
> I ran git pull origin next to get my repository updated.
> 
> Then I ran ./make.sh gettoolchain which came back with
> Toolchain is already downloaded. Exiting...
> Then I ran ./make.sh downloadsrc and for several packages that were not in my cache it then downloaded the missing package into my computers /tmp/ directory and then looked for the file in my build cache/ directory and said it was not available.
> I copied the missing file from my /tmp/ directory to my build cache/ directory and reran downloadsrc and repeated the copying for each file that it downloaded into /tmp/ 11 in total.
> I had a look in the downloadsrc section of make.sh but could not figure out why it was placing the files in /tmp/
> 
> After all files were in my cache then downloadsrc successfully went through the whole sequence including all the BLAKE sums matching.
> Then I ran ./make.sh clean and then ./make.sh build which then gave me the following failure.
> 
> Packaged toolchain compilation
> cat: /home/ahb/sandbox/ipfire-2.x/cache/toolchains/ipfire-2.27-toolchain-20220203-x86_64.b2: No such file or directory
> ./make.sh: line 1847: [: 2c8f3ff0e2bdc638c1470e27dc1ed51a2681ed56480f1b62d8fc7e8c16e5da745333972e9fcda997d62f2927626e3e6ae7510697d0064d178fc3e96d0a3696ba: unary operator expected
> 
> ERROR: /home/ahb/sandbox/ipfire-2.x/cache/toolchains/ipfire-2.27-toolchain-20220203-x86_64 BLAKE2 checksum did not match, check downloaded package                                   [ FAIL ]
>     Check /home/ahb/sandbox/ipfire-2.x/log/_build.preparation.log for errors if applic[ FAIL ]
> 
> This looks like it was trying to find the .b2 file for the toolchain and what was in my cache was the .md5 version. I then deleted all my old toolchains and reran gettoolchain which then downloaded the same version of toolchain but with the .b2 blakesum file.
> 
> Build is now running, hopefully through to the end without any hiccups.
> 
> Regards,
> Adolf.
> 
> 


      reply	other threads:[~2022-04-04 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 12:51 Adolf Belka
2022-04-04 16:07 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7C265DAC-7B3B-49BD-BC23-7756E98BA11C@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox