gnu-crypto-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Crypto] Suggestions for README build instructions


From: Raif S. Naffah
Subject: Re: [GNU Crypto] Suggestions for README build instructions
Date: Sun, 20 Oct 2002 09:44:51 +1000
User-agent: KMail/1.4.3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hello Mark,

On Thursday 10 October 2002 22:07, Mark Wielaard wrote:
> Hi,
>
> Maybe this is already documented somewhere but I could not find it in
> the README. I would suggest to add the following:
>
>     Building
>     --------
>
>     When building from source you need a compiler and runtime for
> java. When using gcj you will need gcj 3.2 or higher. (But note that
> all tests currently fail.) gcj (GNU Compiler for Java) is part of GCC
> (GNU Compiler Collection) and can be found at <http://gcc.gnu.org/>.
> When using gcj you must follow the instructions in gcj/INSTALL.
>
>     [...add some requirements for other java environments and ant
> plus ant build targets...]
>
> Then I would add the following to the gcj/INSTALL file (where it
> already says [   TODO   ]:
>
>     To regenerate the different GNU autotools files (aclocal.m4,
>     configure, Makefile.in, etc) you need the following versions of
> the GNU autotools:
>
>     - aclocal 1.6, to create the aclocal.m4 file.
>     - automake 1.6, to create the various Makefile.in files.
>     - autoconf 2.50, to create the configure file.
>
> The top level directory contains Makefile.in configure and
> configure.in files. I could not make these work at all but it seems
> they are not supported. So it seems a good idea to remove them from
> the tree...

i've checked in new files in the top level directory that should help 
building with GNU tools; ie. aclocal + automake + autoconf, and updated 
the README file accordingly.

comments and suggestions --and of course, testing in one's own 
environment-- are welcome.

using the gcj/INSTALL instructions for building the shared library has 
not changed, and remains the only way to effectively use GCJ.


cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE9se50+e1AKnsTRiERAzXHAKDzrV2sIkHLqo7OciHBLwiRO6JpDQCgg3O0
BKGthz6oPkYCHCv5Pt/5ZNk=
=GHWT
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]