From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] gnu: linux-libre: Update to 4.16
Date: Sat, 07 Apr 2018 21:10:12 -0400 [thread overview]
Message-ID: <87k1ticxl7.fsf@netris.org> (raw)
In-Reply-To: <20180407210616.GA4069@jasmine.lan> (Leo Famulari's message of "Sat, 7 Apr 2018 17:06:16 -0400")
Leo Famulari <leo@famulari.name> writes:
> On Sat, Apr 07, 2018 at 02:36:04PM -0400, Mark H Weaver wrote:
>> One more thing: I had to add 'flex' and 'bison' as native-inputs because
>> the build system in 4.16 now concludes that they need to be re-run for
>> some reason. This could perhaps be avoided by adding a phase to touch
>> the generated files, but I didn't try it.
>
> I noticed this too while building 4.16 with Debian's tooling (`make
> bindeb-pkg`).
That's interesting. I guess the timestamps in your unpacked source
directory were probably not zeroed, so I guess that timestamps are not
the issue here.
>> Anyway, here are the patches. Test reports encouraged.
>
> Thanks, I'm testing this on x86_64 (it's what I have access to).
>
> I noticed this warning at the beginning of the build phase:
>
> ------
> starting phase `build'
> scripts/kconfig/conf --silentoldconfig Kconfig
> Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
> ------
>
> The warning goes away when elfutils is available in the build
> environment.
Ah, good catch! I've now added to my queue another patch which adds
elfutils to native-inputs in 'make-linux-libre'. I'll push it to master
along with the 4.16 update after a bit more testing.
Thanks,
Mark
next prev parent reply other threads:[~2018-04-08 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 18:36 [PATCHES] gnu: linux-libre: Update to 4.16 Mark H Weaver
2018-04-07 21:06 ` Leo Famulari
2018-04-08 1:10 ` Mark H Weaver [this message]
2018-04-08 8:28 ` Vincent Legoll
2018-04-08 15:16 ` Mark H Weaver
2018-04-09 0:35 ` Chris Marusich
2018-04-09 15:38 ` Ludovic Courtès
2018-05-09 6:44 ` Chris Marusich
2018-05-09 8:56 ` Ricardo Wurmus
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=87k1ticxl7.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.