From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: autogen.sh warnings
Date: Mon, 07 Dec 2009 20:50:33 +0100 [thread overview]
Message-ID: <4B1D5C89.8080104@gmail.com> (raw)
In-Reply-To: <4B1D3D7E.5000909@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
Bruce Dubbs wrote:
> I did a fresh checkout of revision 1917 and autogen.sh produces
> several warnings, although the configure and make stages are OK. I am
> using relatively new versions of autoconf and automake:
>
> automake (GNU automake) 1.11
> autoconf (GNU Autoconf) 2.64
>
> When building, a lot of warnings is a red flag to me. I've studied
> the code and am attaching the fixes. autogen.sh now runs cleanly for
> me with a few informational messages.
>
> Below are explanations of what was going on and attached are patches
> to remove all the warnings.
>
Thanks. I'll let someone more familiar with automake to review automake
parts. Just a comment to import_gcry
>
> These are generated by util/import_gcry.py by copying (and in some
> cases modifying) the files in lib/libgcrypt to lib/libgcrypt-grub. It
> also creates cipher.h, memory.h, and types.h.
>
> The warnings above appear to be spurious for autogen.sh
crypto and experimental branches have newer import_gcry.py which has
less warning by skipping copying files unnecessary for grub2. If you
want to fix remaining warnings (on rsa, dsa, elgamal, primegen and ecc)
implement assymetric cryptography support (it's planned but may need
changes to core to be useful, there are lower hanging fruits for crypto).
>
> I added code to util/import_gcry.py supress the warnings if a third
> parameter is passed. I then changed autogen.sh to use:
>
> python util/import_gcry.py lib/libgcrypt/ . NoWarn
This NoWarn is just suppressing legitimate warnings
>
> In a release, the lib/libgcrypt-grub/ directory should be released and
> the lib/libgcrypt/ should probably be suppressed to avoid dependence
> on ruby for non-developers.
import_gcry.py is python, not ruby. Generally ./autogen.sh is ran before
releasing tarball
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2009-12-07 19:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:38 autogen.sh warnings Bruce Dubbs
2009-12-07 19:21 ` Colin Watson
2009-12-07 20:28 ` Bruce Dubbs
2009-12-07 22:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:07 ` Bruce Dubbs
2009-12-07 22:40 ` Colin Watson
2009-12-07 23:26 ` Bruce Dubbs
2009-12-09 21:52 ` Robert Millan
2009-12-09 22:19 ` Bruce Dubbs
2009-12-09 22:34 ` Felix Zielcke
2009-12-09 23:28 ` Bruce Dubbs
2009-12-10 0:25 ` Felix Zielcke
2009-12-10 6:05 ` Bruce Dubbs
2009-12-10 10:15 ` Felix Zielcke
2009-12-10 16:20 ` Bruce Dubbs
2009-12-24 21:13 ` Robert Millan
2009-12-29 3:50 ` Bruce Dubbs
2010-01-01 11:33 ` Robert Millan
2010-01-01 16:57 ` Bruce Dubbs
2010-01-03 16:25 ` Robert Millan
2009-12-10 0:49 ` Robert Millan
2009-12-09 22:56 ` Robert Millan
2009-12-07 19:50 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-12-07 20:51 ` Bruce Dubbs
2009-12-07 22:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 22:49 ` Bruce Dubbs
2009-12-07 23:54 ` Colin Watson
2009-12-08 0:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08 0:13 ` Bruce Dubbs
2010-01-07 19:14 ` Robert Millan
2009-12-08 0:16 ` Colin Watson
2009-12-08 0:34 ` Building system (Re: autogen.sh warnings) Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08 3:40 ` Bruce Dubbs
2009-12-08 10:20 ` autogen.sh warnings Felix Zielcke
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=4B1D5C89.8080104@gmail.com \
--to=phcoder@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 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.