From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] systemd: bumped to version 206
Date: Mon, 2 Sep 2013 17:04:05 +0200 [thread overview]
Message-ID: <20130902150405.GB6918@pc-eric> (raw)
In-Reply-To: <CALdGskLJPNgZ+iRokvubyE0FdG=miQHTHsdC56q84pQGcZE7Zw@mail.gmail.com>
On Sun, Sep 01, 2013 at 06:54:48PM +0200, Olivier Schonken wrote:
> I have started to test building the new version(Using Codesourcery for
> ARM). One thing I noticed is that with the SYSTEMD_AUTORECONF=YES,
> autotools complains about undefined macro AM_PATH_LIBGCRYPT if libgcrypt or
> libgcrypt-devel is not present on the build system. Not sure how to go
> about pleasing autotools without the additional system dependency. Maybe
> someone on the buildroot mailing list will know...?
I removed libgcrypt11-dev from my development machine and built an image for
QEMU arm-versatile using Code Sourcery 2013.05, but I have not seen this issue.
Can you send me a log file of the build with the error?
next prev parent reply other threads:[~2013-09-02 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 16:54 [Buildroot] [PATCH 1/1] systemd: bumped to version 206 Olivier Schonken
2013-09-02 15:04 ` Eric Le Bihan [this message]
2013-09-07 16:52 ` Olivier Schonken
2013-09-08 11:30 ` Eric Le Bihan
2013-09-15 18:15 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-08-30 14:32 eric.le.bihan.dev at free.fr
2013-08-30 14:36 ` Thomas Petazzoni
2013-08-30 16:38 ` eric.le.bihan.dev at free.fr
2013-08-31 11:46 ` Thomas Petazzoni
2013-08-31 20:06 ` Eric Le Bihan
2013-09-01 7:24 ` Thomas Petazzoni
2013-09-02 6:18 ` Arnout Vandecappelle
2013-09-02 9:18 ` Eric Le Bihan
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=20130902150405.GB6918@pc-eric \
--to=eric.le.bihan.dev@free.fr \
--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 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.