From: Artem Bityutskiy <dedekind@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: akpm <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: next 20080530: ubifs build errors
Date: Mon, 02 Jun 2008 08:42:49 +0300 [thread overview]
Message-ID: <1212385369.31023.147.camel@sauron> (raw)
In-Reply-To: <20080530093147.cc1d389f.randy.dunlap@oracle.com>
On Fri, 2008-05-30 at 09:31 -0700, Randy Dunlap wrote:
> with:
> CONFIG_UBIFS_FS=y
> # CONFIG_UBIFS_FS_XATTR is not set
> CONFIG_UBIFS_FS_ADVANCED_COMPR=y
> # CONFIG_UBIFS_FS_LZO is not set
> # CONFIG_UBIFS_FS_ZLIB is not set
> # CONFIG_UBIFS_FS_DEBUG is not set
>
> build gets:
> fs/built-in.o: In function `compr_exit':
> compress.c:(.text+0x4a3fc): undefined reference to `crypto_free_tfm'
> fs/built-in.o: In function `compr_init':
> compress.c:(.init.text+0x11d4): undefined reference to `crypto_alloc_base'
> make[1]: *** [.tmp_vmlinux1] Error 1
>
>
> because CRYPTO is not enabled.
Fixed, pushed to the git tree, thank you!
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-06-02 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 16:31 next 20080530: ubifs build errors Randy Dunlap
2008-06-02 5:42 ` Artem Bityutskiy [this message]
2008-06-02 5:46 ` Stephen Rothwell
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=1212385369.31023.147.camel@sauron \
--to=dedekind@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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