| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on Solaris 10 with GCC 3.4.3.
First, remove the definition of _XOPEN_SOURCE_EXTENDED=1 in mmap_mem.cpp
and unix_cmd.cpp, because apparently on Solaris defining this macro breaks
C++ compilation entirely with GCC:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6395191
In es_egd.cpp and es_dev.cpp, include <fcntl.h> to get the declaration of
open(), which is apparently where open(2) lives on Solaris - this matches
the include the *BSD man pages for open(2) show, though AFAIK the BSDs
all compiled fine without it (probably due to greater efforts to be
source-compatible with Linux systems by *BSD developers).
I have not been able to test these changes personally on Solaris but
Rickard reports that with these changes everything compiles OK.
Update lib version to 1.8.0-pre. ZOMG. Finally.
|
| | |
|
| |
|
|
|
| |
decide later on if changes warrant another release candiate or not. If
not, 1.7.24 will be remarked as 1.8.0 prior to release.
|
| |
|
|
|
|
|
|
| |
the user that it can override via --cpu, however if it was guessed using
Config{'archname'} the user was not so reminded. This is actually the worst
possible case since Perl's Config setting is probably the least reliable
method (which is why it is only used if /proc/cpuinfo and uname are not
around).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
GNU MP, zlib, and bzip2.
--with-{openssl,gnump,bzip2,zlib}
--without-{openssl,gnump,bzip2,zlib}
They have the exact same effect as --enable-modules=x or --disable-modules=x
This turned out to be a much easier way of specifying options for the
Gentoo ebuild. It is likely that other distro builds architectures will
also prefer this option style as being somewhat more autoconf-like and
fitting in with existing command templates.
|
| |
|
|
|
|
| |
--disable-modules. While updating the Gentoo ebuild I found it was
much easier to autogen the configure line if both of these options
are no-ops if used with no value.
|
| |
|
|
|
|
| |
Print the version number at the start of the build.
Fix compiler name in TR1 message
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
both support TR1 fine AFAICT.
Add ability to explicitly disable using TR1 with --with-tr1=none
Add a marker in the cc info files specifiying if TR1 should be chosen
by default. Yes, autoconf would be better for this than a static
per-compiler setting. Yes, I totally hate autoconf. Yes, I would still
consider autoconf patches. No, I'm not going to do it myself. :)
I am looking forward to being able to safely adopt C++0x and TR2
throughout the library and make the need for a lot of this special-casing
stuff go away.
Until then, it seems better to defaulting to using tr1 (and thus, ECC) than
not.
|
| | |
|
| |
|
|
| |
this if desired)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
was not the right place to keep track of this information. Also modify
all Algorithm_Factory constructor functions to take instead of a SCAN_Name
a pair of std::strings - the SCAN name and an optional provider name. If
a provider is specified, either that provider will be used or the request
will fail. Otherwise, the library will attempt best effort, based on
user-set algorithm implementation settings (combine with benchmark.h for
choosing the fastest implementation at runtime) or if not set, a static
ordering (preset in static_provider_weight in prov_weight.cpp, though it
would be nice to make this easier to toggle).
|
| | |
|
| |
|
|
|
| |
botan-17, which was potentially confusing (and apparently contradictory to
normal pkg-config naming conventions).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
instead of in the toplevel directory.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
out of tree builds.
Also rename the generated botan-config script so that it is, like the
pkg-config settings, namespaced by the major and minor version numbers
(eg, botan-17-config). This is useful in particular for distros like
Debian which ship both stable and unstable versions. Currently Debian
is actually the only distro I know of shipping 1.7 as well as 1.6, but
I would certainly like to encourage more in the future by making it
easy to do.
|
| | |
|
| |
|
|
|
|
|
| |
$ pkg-config botan-17 --libs
-L/usr/local/lib -lbotan -lm -lpthread -lrt
to make it easier to have multiple versions of Botan installed and in
use at the same time.
|
| | |
|
| |
|
|
|
| |
the submodel it is referencing - this is usually more recognizable.
Suggested by Markus Wanner.
|
| |
|
|
|
|
| |
of /proc/cpuinfo in configure.pl
This is probably only useful for testing.
|
| | |
|
| |
|
|
| |
rather than silently ignoring it.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
accepts options 'boost' and 'system'. Now GF(p) math (and indirectly,
ECDSA) will be enabled if --with-tr1=boost or --with-tr1=system
is passed at build time to enable a shared_ptr implementation.
Modules can now specify that they require TR1, in which case
they will only be autoloaded if a TR1 implementation was set
(they can choose which one to use by checking the feature macros
from build.h)
The gfpmath module was set to load only on request. That has
changed to load automatically (but will only do so if a TR1
impl is set as described above). CVC has also been marked
as requiring TR1. (ECDSA/ECDH are not, since they do not
use tr1 shared_ptr directly)
Update and cleanup help output. Do not print the list of modules in
--help anymore (too long); you can still get the list (in an easier to
parse format) --module-info. Reorganize the help text so the more
useful options are described closer to the top.
Fix the --with-endian and --with-unaligned-mem options: they were being
accepted but ignored.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'/bin/uname', '/usr/bin/uname', or '/bin/sh' - the existence of
these files gives us some hope that exec'ing uname will work,
and avoids an error on Windows builds.
Only run uname once (uname -a), collecting it into $$config{'uname'}
(previously configure.pl might run it as many as three times,
uname -s, uname -p, and uname -m).
Only submodels were being searched longest to shortest. Modify
guess_cpu_from_this to also search arch names and aliases in this
manner. This allows Config{'archname'} of 'x86_64-linux' to be
correctly detected as x86-64 (was being detected as x86, since
before the search was ordered by the Perl hash order).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
longest match first instead of random Perl hash order. Seems to work
very well in practice.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Markus Wanner noted on the mailing list that build.h was not being
installed. That is because it was not included in the HEADERS variable
in the Makefile, and build.h did not yet exist when configure.pl scanned
the source and include directories.
Rearrange the order of operations in configure.pl a bit so first build.h
is generated and then the makefile is.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
--enable-modules for it to be recognized
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
(--bindir, --libdir, --docdir already supported, add --includdir=,
--localstatedir=, etc)
|
| | |
|
| |
|
|
|
|
|
| |
Suggestions from Zack Weinberg on the monotone-devel list.
Rename --endian to --with-endian
Rename --unaligned-mem to --with-unaligned-mem
|
| | |
|
