From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Building GRUB fails with `In function `do_setkey' undefined reference to `fips_mode'`
Date: Mon, 29 Dec 2014 16:36:20 +0300 [thread overview]
Message-ID: <CAA91j0XQmcgpEG8_ULQ3b8FtzHi1OEpb5shuRvpzUr-DKpwzKw@mail.gmail.com> (raw)
In-Reply-To: <1419849384.3406.80.camel@users.sourceforge.net>
On Mon, Dec 29, 2014 at 1:36 PM, Paul Menzel
<paulepanter@users.sourceforge.net> wrote:
> Am Freitag, den 26.12.2014, 20:59 +0300 schrieb Andrei Borzenkov:
>> В Fri, 26 Dec 2014 11:23:24 +0100 Paul Menzel пишет:
>
>> > with latest master
>> >
>> > $ git describe
>> > grub-2.02-beta2-137-gbac5d1a
>> >
>> > building GRUB as a coreboot payload fails on Debian Sid/unstable.
>> >
>> > $ make clean
>> > $ ./configure --with-platform=coreboot
>> > $ make
>> > […]
>> > mv -f .deps-util/grub_fstest-grub_fstest_init.Tpo .deps-util/grub_fstest-grub_fstest_init.Po
>> > gcc -Wall -W -Wshadow -Wpointer-arith -Wundef -Wchar-subscripts -Wcomment -Wdeprecated-declarations -Wdisabled-optimization -Wdiv-by-zero -W
>> > float-equal -Wformat-extra-args -Wformat-security -Wformat-y2k -Wimplicit -Wimplicit-function-declaration -Wimplicit-int -Wmain -Wmissing-br
>> > aces -Wmissing-format-attribute -Wmultichar -Wparentheses -Wreturn-type -Wsequence-point -Wshadow -Wsign-compare -Wswitch -Wtrigraphs -Wunkn
>> > own-pragmas -Wunused -Wunused-function -Wunused-label -Wunused-parameter -Wunused-value -Wunused-variable -Wwrite-strings -Wnested-externs
>> > -Wstrict-prototypes -Wcast-align -Wextra -Wattributes -Wendif-labels -Winit-self -Wint-to-pointer-cast -Winvalid-pch -Wmissing-field-initia
>> > lizers -Wnonnull -Woverflow -Wvla -Wpointer-to-int-cast -Wstrict-aliasing -Wvariadic-macros -Wvolatile-register-var -Wpointer-sign -Wmissing
>> > -include-dirs -Wmissing-prototypes -Wmissing-declarations -Wformat=2 -Werror -Wno-undef -Wno-sign-compare -Wno-unused -Wno-unused-parameter
>> > -Wno-redundant-decls -Wno-unreachable-code -Wno-conversion -o grub-fstest util/grub_fstest-grub-fstest.o grub-core/kern/emu/grub_fstes
>> > t-hostfs.o grub-core/disk/grub_fstest-host.o grub-core/osdep/grub_fstest-init.o grub_fstest-grub_fstest_init.o libgrubmods.a libgrubgcry.a l
>> > ibgrubkern.a grub-core/gnulib/libgnu.a
>> > libgrubgcry.a(libgrubgcry_a-rijndael.o): In function `do_setkey':
>> > rijndael.c:(.text+0x51): undefined reference to `fips_mode'
>>
>> Works here. Looks like fips_mode is (re-)defined in some header on
>> your system. Could you find out where?
>
> Sorry, I was not able to find that out. Cloning the repository on the
> same system again and running
>
> $ ./autogen.sh
> $ ./configure --with-platform=coreboot
> $ make
>
> it worked fine too. So, maybe I’m missing when I need to run
> `./autogen.sh` and not only `make clean`. Are there some guidelines?
>
Normally autogen.sh is needed just once after git checkout (or I think
to rebuild message catalogs if you add some). All other times I just
use "make distclean" which worked so far.
prev parent reply other threads:[~2014-12-29 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 10:23 Building GRUB fails with `In function `do_setkey' undefined reference to `fips_mode'` Paul Menzel
2014-12-26 17:59 ` Andrei Borzenkov
2014-12-29 10:36 ` Paul Menzel
2014-12-29 13:36 ` Andrei Borzenkov [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=CAA91j0XQmcgpEG8_ULQ3b8FtzHi1OEpb5shuRvpzUr-DKpwzKw@mail.gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).