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: [PATCH] ccache: update to 3.7.12
Date: Tue, 22 Dec 2020 12:12:40 +0100	[thread overview]
Message-ID: <7B28533A-D2FA-4A0D-BD6A-D432DFDAD8DE@ipfire.org> (raw)
In-Reply-To: <d35df4f7-b5eb-d492-2fce-0be5992b6aca@ipfire.org>

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

Hi,

I merged this patch, but I do think that we should upgrade to 4.x.

There are various features in it to improve performance and that is what we want.

Unfortunately this is another project who switched to another shitty build system, so we will need to depend on cmake to build the toolchain. I guess that is a price we have to pay.

-Michael

> On 21 Dec 2020, at 23:12, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Michael,
> 
> yes, the 3.x series is still supported and the current 4.x release required more
> changes to the LFS file (cmake as a dependency - causing a bootstrap problem here?).
> 
> Thereof, I thought it might be a good compromise to update to the latest 3.x release.
> 
> Thanks, and best regards,
> Peter Müller
> 
> 
>> Hi,
>> 
>> Is there any reason you didn’t go for 4.1?
>> 
>> -Michael
>> 
>>> On 21 Dec 2020, at 20:02, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>> 
>>> Please refer to https://ccache.dev/news.html#2020-10-01 for a list of
>>> all release notes since version 3.4.1, it is unfortunately way too long
>>> to be added here. :-]
>>> 
>>> Since ccache is not part of the distribution itself, no rootfile updates
>>> were necessary.
>>> 
>>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>>> ---
>>> lfs/ccache | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>> 
>>> diff --git a/lfs/ccache b/lfs/ccache
>>> index 1361f3ed0..e930f20d1 100644
>>> --- a/lfs/ccache
>>> +++ b/lfs/ccache
>>> @@ -24,7 +24,7 @@
>>> 
>>> include Config
>>> 
>>> -VER        = 3.4.1
>>> +VER        = 3.7.12
>>> 
>>> THISAPP    = ccache-$(VER)
>>> DL_FILE    = $(THISAPP).tar.xz
>>> @@ -51,7 +51,7 @@ objects = $(DL_FILE)
>>> 
>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>> 
>>> -$(DL_FILE)_MD5 = 39492aea565c3e6d5affa633672a93bd
>>> +$(DL_FILE)_MD5 = 4c9a09ae499d1d82bb83e67f1068f9bb
>>> 
>>> install : $(TARGET)
>>> 
>>> -- 
>>> 2.26.2
>> 


      reply	other threads:[~2020-12-22 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 19:02 Peter Müller
2020-12-21 21:28 ` Michael Tremer
2020-12-21 22:12   ` Peter Müller
2020-12-22 11:12     ` 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=7B28533A-D2FA-4A0D-BD6A-D432DFDAD8DE@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