From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: 'next' with new kernel 4.14.39 took a long time - (was: Re: A few updates - built under Core 120)
Date: Sat, 05 May 2018 19:50:03 +0200 [thread overview]
Message-ID: <dacf9195-9291-21db-d092-1d5f48a30dba@ipfire.org> (raw)
In-Reply-To: <47b733b4-c1cf-5a68-6fcc-f7b365388800@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On 04.05.2018 22:19, Matthias Fischer wrote:
> Hi,
>
> On 03.05.2018 21:34, Michael Tremer wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Ah, sorry I forget to check this out.
>>
>> I just started my build and it will need a while now to go to the point where it
>> crashes. Probably has something to do with the core update folder. Just delete
>> that and the build should complete without creating any core updates.
>
> Just saw this.
>
> Core 120:
> root(a)Devel: /home/matz/ipfire-2.x/config/rootfiles/core/120/filelists
>
> next:
> root(a)Devel: /home/matz/ipfire-2.x/config/rootfiles/core/121/fileslists
> ^^^^^^^^^^
> Typo?
Rhetorical question. Yes, it was.
Anyway, Arne now saw this too.
But: building the new 'next' with kernel 4.14.39 set a new record here:
"*** Build finished in 9:24:12"
Wow.
Any chance of getting ~4:30 again, as with Core 120? ;-)
Best,
Matthias
next prev parent reply other threads:[~2018-05-05 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 17:01 A few updates - built under Core 120 Matthias Fischer
2018-05-03 17:08 ` Michael Tremer
2018-05-03 18:19 ` Peter Müller
2018-05-03 19:34 ` Michael Tremer
2018-05-04 20:13 ` Matthias Fischer
2018-05-04 20:19 ` Matthias Fischer
2018-05-05 17:50 ` Matthias Fischer [this message]
2018-05-06 22:55 ` 'next' with new kernel 4.14.39 took a long time - 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=dacf9195-9291-21db-d092-1d5f48a30dba@ipfire.org \
--to=matthias.fischer@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