public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: unterminated call to function 'firstword' while downloading new sources
Date: Sun, 03 Apr 2022 16:36:47 +0000	[thread overview]
Message-ID: <16672e09-c2f5-2b9d-6378-b1bf0a74a96d@ipfire.org> (raw)
In-Reply-To: <7cfda233-7b95-5e7c-7ec2-0eb4a2a2740c@ipfire.org>

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

Hello Matthias,

yes, I just experienced the same thing with an updated version of smartmontools.

This looks like I broke something while switching the checksum algorithm. Not
being very familiar to Makefiles, I will try to figure it out and report back.

Sorry for the mess - feel free to compile things against the "master" branch,
using MD5 checksums. I will convert the patches for BLAKE2 if you submit them,
so you can continue working.

Thanks, and best regards,
Peter Müller


> Hi,
> 
> interesting error:
> 
> While running './make.sh downloadsrc' I'm getting these errors for files
> that didn't exist in the local cache of my 'Devel':
> 
> ***SNIP***
> Building monit Config:347: *** unterminated call to function
> 'firstword': missing ')'.  Stop.
> ...
> Apr  3 16:23:50: Building util-linux Config:347: *** unterminated call
> to function 'firstword': missing ')'.  Stop.
> ...
> Apr  3 16:27:44: Building zlib Config:347: *** unterminated call to
> function 'firstword': missing ')'.  Stop.
> ***SNAP***
> 
> After downloading these three files manually, all went through, "all
> files BLAKE2 checksum match".
> 
> Anyone else?
> 
> Best,
> Matthias

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 16:32 Matthias Fischer
2022-04-03 16:36 ` Peter Müller [this message]
2022-04-03 16:54   ` Matthias Fischer
2022-04-03 18:26     ` Matthias Fischer

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=16672e09-c2f5-2b9d-6378-b1bf0a74a96d@ipfire.org \
    --to=peter.mueller@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