aboutsummaryrefslogtreecommitdiff
path: root/configure.in
Commit message (Collapse)AuthorAge
...
| * | Fix libevent autoconf bug #2698Jacob Appelbaum2011-03-27
| | |
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2011-03-18
|\| | | | | | | | | | | | | | Trivial Conflicts: configure.in
| * | Remove superfluous -g -O2 compiler argumentSebastian Hahn2011-03-18
| | | | | | | | | | | | | | | | | | Autoconf adds -g -O2 by default, so adding it ourselves is not required. It also caused a warning with clang for every source file, so remove it here. Fixes last issue of ticket 2696.
| * | Fix compilation under LLVM/clang with --enable-gcc-warningsSteven Murdoch2011-03-10
| | | | | | | | | | | | | | | | | | | | | - When compiling using clang (2.9 or lower) do not enable -Wnormalized=id or -Woverride-init when --enable-gcc-warnings or --enable-gcc-warnings-advisory is set as these options are unsupported.
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2011-02-22
|\| | | | | | | | | | | | | | Conflicts: configure.in
| * | Merge remote branch 'origin/maint-0.2.1' into maint-0.2.2Nick Mathewson2011-02-22
| |\| | | | | | | | | | | | | Conflicts: configure.in
| | * Remove doc/spec/Makefile.in from list of generated filesNick Mathewson2011-02-22
| | |
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2011-02-03
|\| |
| * | Enable ASLR and permanent DEP for Windows executablesJohn Brooks2011-02-03
| | | | | | | | | | | | Fix for #2358
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2011-01-12
|\| |
| * | Merge remote branch 'sebastian/bug2337' into maint-0.2.2Nick Mathewson2011-01-12
| |\ \
| | * | Fix a autoconf warningSebastian Hahn2011-01-12
| | | |
| | * | Detect signed size_t and report an error at configure time.Nick Mathewson2011-01-03
| | |/
| * | bump to 0.2.2.19-alphaRoger Dingledine2010-11-21
| | |
| * | new development versionRoger Dingledine2010-11-16
| | |
| * | bump to 0.2.2.18-alphaRoger Dingledine2010-11-16
| | |
* | | Use autoconf's FLEXIBLE_ARRAY_MEMBER for unspecified-length arraysNick Mathewson2011-01-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | C99 allows a syntax for structures whose last element is of unspecified length: struct s { int elt1; ... char last_element[]; }; Recent (last-5-years) autoconf versions provide an AC_C_FLEXIBLE_ARRAY_MEMBER test that defines FLEXIBLE_ARRAY_MEMBER to either no tokens (if you have c99 flexible array support) or to 1 (if you don't). At that point you just use offsetof [STRUCT_OFFSET() for us] to see where last_element begins, and allocate your structures like: struct s { int elt1; ... char last_element[FLEXIBLE_ARRAY_MEMBER]; }; tor_malloc(STRUCT_OFFSET(struct s, last_element) + n_elements*sizeof(char)); The advantages are: 1) It's easier to see which structures and elements are of unspecified length. 2) The compiler and related checking tools can also see which structures and elements are of unspecified length, in case they wants to try weird bounds-checking tricks or something. 3) The compiler can warn us if we do something dumb, like try to stack-allocate a flexible-length structure.
* | | Initial work to set CLOEXEC on all possible fdsNick Mathewson2010-11-20
| | | | | | | | | | | | Still to go: some pipes, all stdio files.
* | | Split long lines in configure.in and Makefile.am filesNick Mathewson2010-11-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Having very long single lines with lots and lots of things in them tends to make files hard to diff and hard to merge. Since our tools are one-line-at-a-time, we should try to construct lists that way too, within reason. This incidentally turned up a few headers in configure.in that we were for some reason searching for twice.
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2010-11-11
|\| | | | | | | | | | | | | | Conflicts: configure.in
| * | Remove everything related to os x expert packageSebastian Hahn2010-11-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We decided to no longer ship expert packages for OS X because they're a lot of trouble to keep maintained and confuse users. For those who want a tor on OS X without Vidalia, macports is a fine option. Alternatively, building from source is easy, too. The polipo stuff that is still required for the Vidalia bundle build can now be found in the torbrowser repository, git://git.torproject.org/torbrowser.git.
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2010-10-20
|\| |
| * | Remove redundant -Wpointer-sign CFLAGSebastian Hahn2010-10-20
| | | | | | | | | | | | | | | -Wpointer-sign is implied with -Wall, which we use when building with --enable-gcc-warnings.
| * | Remove redundant -Wformat -Wformat-security CFLAGSSebastian Hahn2010-10-20
| | | | | | | | | | | | | | | | | | When configuring with --enable-gcc-warnings, we use -Wformat=2 which automatically enables the available -Wformat switches, so adding them again in the --enable-gcc-hardening case doesn't make sense..
| * | Use ssp-buffer-size param when hardeningSebastian Hahn2010-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We used to enable ssp-buffer-size=1 only when building with --enable-gcc-warnings. That would result in warnings (and no protection for small arrays) when building with --enable-gcc-hardening without enabling warnings, too. Fixes bug 2031. Also remove an XXX: We now allow to build with -fstack-protector by using --enable-gcc-hardening.
* | | Raise libevent version needed for buffereventsSebastian Hahn2010-10-15
| | |
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2010-10-12
|\| |
| * | Fix MIPSpro and time_t signedness detectionSebastian Hahn2010-10-11
| | | | | | | | | | | | | | | 3d6e2830876 silenced the autogen.sh warnings as it was supposed to, but introduced two bugs. Fix them.
* | | Fix running unit tests from outside of the build directory (fixes bug #2051)Steven Murdoch2010-10-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the unit tests test_util_spawn_background_* assume that they are run from the Tor build directory. This is not the case when running make distcheck, so the test will fail. This problem is fixed by autoconf setting BUILDDIR to be the root of the Tor build directory, and this preprocessor variable being used to specify the absolute path to test-child. Also, in test-child, do not print out argv[0] because this will no longer be predictable. Found by Sebastian Hahn.
* | | Fix the new warnings during autogen.shSebastian Hahn2010-10-11
| | | | | | | | | | | | | | | Follow-up fix to 3d6e2830876c for configure.in additions in master that weren't in maint-0.2.2
* | | Merge remote branch 'origin/maint-0.2.2'Nick Mathewson2010-10-11
|\| |
| * | Fix warnings with new versions of autoconfSebastian Hahn2010-10-11
| | | | | | | | | | | | | | | | | | It looks like autoconf 2.68 introduced a bunch of new warnings when it didn't like the syntax you used or forgot to use AC_LANG_(SOURCE|PROGRAM).
| * | bump to 0.2.2.17-alpha-devRoger Dingledine2010-10-01
| | |
| * | bump to 0.2.2.17-alphaRoger Dingledine2010-09-30
| | |
* | | Changes to tor-fw-helper, some based on Nick's reviewJacob Appelbaum2010-09-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * MINIUPNPC rather than the generic UPNP * Nick suggested a better abstraction model for tor-fw-helper * Fix autoconf to build with either natpmp or miniupnpc * Add AM_PROG_CC_C_O to fix automake complaint * update spec to address nickm's concern * refactor nat-pmp to match upnp state * we prefer tor_snprintf to snprintf * link properlty for tor_snprintf * rename test_commandline_options to log_commandline_options * cast this uint as an int * detect possible FD_SETSIZE errors * make note about future enhancements for natpmp * add upnp enhancement note * ChangeLog entry * doxygen and check-spaces cleanup * create tor-fw-helper.1.txt
* | | First implementation of tor-fw-helper.Jacob Appelbaum2010-09-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tor-fw-helper is a command-line tool to wrap and abstract various firewall port-forwarding tools. This commit matches the state of Jacob's tor-fw-helper branch as of 23 September 2010. (commit msg by Nick)
* | | Autodetect the number of CPUs when possible if NumCPUs==0Nick Mathewson2010-09-28
| | | | | | | | | | | | | | | | | | | | | This is needed for IOCP, since telling the IOCP backend about all your CPUs is a good idea. It'll also come in handy with asn's multithreaded crypto stuff, and for people who run servers without reading the manual.
* | | Detect Libevent version at configure time when using buffereventsNick Mathewson2010-09-27
| | |
* | | Teach read_event/write_event manipulators about bufferevents.Nick Mathewson2010-09-27
| | | | | | | | | | | | Add an --enable-bufferevents config switch.
* | | Remove never-actually-finished code to use readv and writev for IO.Nick Mathewson2010-09-27
| | | | | | | | | | | | | | | We'll get this feature for free with bufferevents, so there's no good reason to clone it in Tor.
* | | Bump the Tor version in master to 0.2.3.0-alpha-devNick Mathewson2010-09-24
|/ / | | | | | | | | | | | | | | 0.2.2.x development will continue in branch maint-0.2.2. master is now out of feature freeze. Let's not go crazy right away. :)
* | bump to 0.2.2.16-alpha-devRoger Dingledine2010-09-17
| |
* | best tor ever!Roger Dingledine2010-09-17
| |
* | Merge remote branch 'origin/maint-0.2.1'Nick Mathewson2010-08-26
|\|
| * Use -Wno-system-headers on openbsd to resolve 2nd case of bug1848Nick Mathewson2010-08-26
| |
| * bump to 0.2.1.25Roger Dingledine2010-03-15
| | | | | | | | it's perfect, let's ship it
| * clean up the 0.2.1.25 changelogRoger Dingledine2010-03-06
| |
| * bump to 0.2.1.24Roger Dingledine2010-02-21
| |
| * Bump version to 0.2.1.23-devNick Mathewson2010-02-18
| |
| * prepare for 0.2.1.23Roger Dingledine2010-02-12
| |
generated by cgit v1.2.3 (git 2.45.0) at 2024-11-26 00:22:33 +0000