From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] keyutils: Bump version to 1.5.9, fix patches and static build
Date: Wed, 24 Sep 2014 09:45:37 +0100 [thread overview]
Message-ID: <542284B1.6000105@imgtec.com> (raw)
In-Reply-To: <20140923215259.3644f7ab@free-electrons.com>
On 09/23/2014 08:52 PM, Thomas Petazzoni wrote:
> This fails to build with:
>
> /home/thomas/projets/buildroot/output/host/usr/bin/arm-linux-gcc -L. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -o keyctl keyctl.o -lkeyutils
> /home/thomas/projets/buildroot/output/host/usr/bin/arm-linux-gcc -L. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -o request-key request-key.o -lkeyutils
> key.dns_resolver.c:55:22: fatal error: keyutils.h: No such file or directory
> #include <keyutils.h>
Thanks Thomas,
patch v2 sent with this problem fixed and also including a hash file.
Regards,
--
Vincent
prev parent reply other threads:[~2014-09-24 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 15:59 [Buildroot] [PATCH] keyutils: Bump version to 1.5.9, fix patches and static build Vicente Olivert Riera
2014-09-23 19:52 ` Thomas Petazzoni
2014-09-24 8:45 ` Vicente Olivert Riera [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=542284B1.6000105@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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