summaryrefslogtreecommitdiff
path: root/autogen.sh
AgeCommit message (Collapse)AuthorFilesLines
2019-03-26autogen.sh: add --help description about the --with-distro switchGabor Kelemen1-0/+2
Change-Id: I8d9732251b05ec4ec93ce0fc0ba24f2f27d54b18 Reviewed-on: https://gerrit.libreoffice.org/69712 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
2019-01-30don't require /autoconf/ to be 2.68 (also allow e.g. autoconf268)Christian Lohmaier1-2/+6
partially reverts 182f5a0f34fa45d2f74ba22eda41d4e39dca93e5 in the sense that configure still insists on autoconf 2.68, but in a way that allows to specify an already installed copy (that the libnumbertext build already picked up successfully) While there is autoconf268 package, it gets installed as autoconf268, but aclocal doesn't provide a way to use something else than "autoconf" In the spirit of "keeping it simple", no conditional check is done whether libnumbertext is actually enabled or not. Change-Id: Ice05a70ef56a4ed3428c74d15d6aeeaa54f71c0b Reviewed-on: https://gerrit.libreoffice.org/67159 Reviewed-by: Michael Stahl <Michael.Stahl@cib.de> Tested-by: Jenkins
2018-11-25Better way of enabling Developer Toolset 7 for Jenkins' linux_gcc_release_64Stephan Bergmann1-7/+0
Enabling it in the relevant distro-configs/Jenkins/* file is more intuitive than enabling it in autogen.sh (and avoids issues like d057e61cb5aae15ea37ce9ac824647cd2060e331 "Restrict Developer Toolset to Config=linux_gcc_release_64"), and will also be used for other Jenkins jobs like <https://gerrit.libreoffice.org/#/c/63982/> "Enabling Developer Toolset 7 for Jenkins' lo_tb_master_linux_dbg". Change-Id: If633044a90c35a12a73d60335839af0a106aa20f Reviewed-on: https://gerrit.libreoffice.org/63989 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2018-11-25Restrict Developer Toolset to Config=linux_gcc_release_64Stephan Bergmann1-1/+1
The Jenkins "Gerrit Linux clang/dbgutil" builds started to fail in odd ways, presumably because of having the Developer Toolset in the PATH now when building compilerplugins. So change compilerplugins/clang/pluginhandler.hxx slightly to force rebuild. Change-Id: I97b8f89dc2e20c85f130284ca5326a5c96c2a1ba Reviewed-on: https://gerrit.libreoffice.org/63962 Tested-by: Stephan Bergmann <sbergman@redhat.com> Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2018-11-24Make Jenkins linux_gcc_release_64 pick up Developer Toolset 7Stephan Bergmann1-0/+7
...as discussed at <https://lists.freedesktop.org/archives/libreoffice/2018-November/081423.html> "Re: Compiler baselines". It doesn't look exactly right to enable the Developer Toolset from autogen.sh. But the alternative would be to "hide" that in <https://ci.libreoffice.org/job/gerrit_linux_gcc_release/configure>, which would probably not be helpful when developers try to track down why a certain Jenkins build behaves the way it does. So pragmatically stick it in autogen.sh. (Also, it puts Developer Toolset on the PATH whenever it is found on a system using LODE_HOME, not just for the specific Config=linux_gcc_release_64 case. Lets see how that works out in practice.) However, it turns out that the Developer Toolset 7's GCC 7.3.1 with --enable-werror (that is implicitly enabled for LODE-driven builds in configure.ac) and (implicit) --enable-optimized produces many false warnings (i.e., errors), see below for a sample. (Actually, my experience is that contemporary GCC hardly ever work with -Werror in optimized builds, due to analysis being done on already optimized code; it surprised me to find out that the Jnekins linux_gcc_release_64 builds were apparently successfully done with --enable-werror with GCC 4.8.5.) So explicitly --disable-werror for these builds. (Which means that <https://gerrit.libreoffice.org/plugins/gitiles/lode/ +/b82e0a9d26ef4c81046c053ff831dccfc84c56be%5E!> "For linux_gcc_release_64, don't let ccache strip comments" could probably be reverted again if it has negative impact on Jenkins' performance.) Some of the false warnings encountered: > [CXX] jvmfwk/plugins/sunmajor/pluginlib/sunjavaplugin.cxx > In file included from /opt/rh/devtoolset-7/root/usr/include/c++/7/vector:69:0, > from /home/tdf/sberg/core/jvmfwk/plugins/sunmajor/pluginlib/sunjavaplugin.cxx:39: > /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/vector.tcc: In function ‘javaPluginError jfw_plugin_startJavaVirtualMachine(const JavaInfo*, const JavaVMOption*, sal_Int32, JavaVM**, JNIEnv**)’: > /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/vector.tcc:407:15: error: variable ‘__new_finish’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered] > pointer __new_finish(__new_start); > ^~~~~~~~~~~~ > cc1plus: all warnings being treated as errors > [CXX] libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx: In function ‘gboolean gtv_calc_header_bar_draw(GtkWidget*, cairo_t*)’: > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:89:117: error: ‘aRectangle._cairo_rectangle_int::height’ may be used uninitialized in this function [-Werror=maybe-uninitialized] > cairo_move_to(pCairo, rRectangle.x + rRectangle.width / 2 - extents.width / 2, rRectangle.y + rRectangle.height / 2 + extents.height / 2); > ~~~~~~~~~~~~~~~~~~^~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:102:22: note: ‘aRectangle._cairo_rectangle_int::height’ was declared here > GdkRectangle aRectangle; > ^~~~~~~~~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:89:59: error: ‘aRectangle._cairo_rectangle_int::width’ may be used uninitialized in this function [-Werror=maybe-uninitialized] > cairo_move_to(pCairo, rRectangle.x + rRectangle.width / 2 - extents.width / 2, rRectangle.y + rRectangle.height / 2 + extents.height / 2); > ~~~~~~~~~~~~~~~~~^~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:102:22: note: ‘aRectangle._cairo_rectangle_int::width’ was declared here > GdkRectangle aRectangle; > ^~~~~~~~~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:89:97: error: ‘aRectangle._cairo_rectangle_int::y’ may be used uninitialized in this function [-Werror=maybe-uninitialized] > cairo_move_to(pCairo, rRectangle.x + rRectangle.width / 2 - extents.width / 2, rRectangle.y + rRectangle.height / 2 + extents.height / 2); > ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:102:22: note: ‘aRectangle._cairo_rectangle_int::y’ was declared here > GdkRectangle aRectangle; > ^~~~~~~~~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:89:40: error: ‘aRectangle._cairo_rectangle_int::x’ may be used uninitialized in this function [-Werror=maybe-uninitialized] > cairo_move_to(pCairo, rRectangle.x + rRectangle.width / 2 - extents.width / 2, rRectangle.y + rRectangle.height / 2 + extents.height / 2); > ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~ > /home/tdf/sberg/core/libreofficekit/qa/gtktiledviewer/gtv-calc-header-bar.cxx:102:22: note: ‘aRectangle._cairo_rectangle_int::x’ was declared here > GdkRectangle aRectangle; > ^~~~~~~~~~ > cc1plus: all warnings being treated as errors > [CXX] svl/source/misc/lockfilecommon.cxx > /home/tdf/sberg/core/svl/source/misc/lockfilecommon.cxx: In static member function ‘static rtl::OUString svt::LockFileCommon::GetCurrentLocalTime()’: > /home/tdf/sberg/core/svl/source/misc/lockfilecommon.cxx:190:10: error: ‘%02d’ directive writing between 2 and 5 bytes into a region of size between 1 and 9 [-Werror=format-overflow=] > OUString LockFileCommon::GetCurrentLocalTime() > ^~~~~~~~~~~~~~ > /home/tdf/sberg/core/svl/source/misc/lockfilecommon.cxx:190:10: note: directive argument in the range [0, 65535] > /home/tdf/sberg/core/svl/source/misc/lockfilecommon.cxx:190:10: note: directive argument in the range [0, 65535] > /home/tdf/sberg/core/svl/source/misc/lockfilecommon.cxx:204:24: note: ‘sprintf’ output between 17 and 31 bytes into a destination of size 20 > sprintf( pDateTime, "%02d.%02d.%4d %02d:%02d", aDateTime.Day, aDateTime.Month, aDateTime.Year, aDateTime.Hours, aDateTime.Minutes ); > ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > cc1plus: all warnings being treated as errors Change-Id: I3a851b7591274a8cf8b4729ae036afeb8e82eedc Reviewed-on: https://gerrit.libreoffice.org/63884 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2018-08-27avoid error message about removing non-existent fileLuboš Luňák1-2/+2
If it's a first build, there are no Makefiles in the build dir. Change-Id: Idec99145a5fb273921f58d92013a1c882cb8b026
2018-06-30autogen.sh: fix out-of-tree module Makefiles for Win32 makeMichael Stahl1-2/+9
These were created as symlinks, which doesn't work with Win32 make as it doesn't understand Cygwin symlinks. Instead, create them as actual files. Note: the reason why they work as symlinks at all is that the Makefile uses $(realpath) and partial_build.mk does not, so they can resolve relative paths from 2 different directories... Change-Id: I4a9abffae82561111a9525fb35ed4b174cc8d96a Reviewed-on: https://gerrit.libreoffice.org/56691 Tested-by: Jenkins Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
2018-01-19Don't set autogen.sh KEY=VALUE arguments as environment variablesStephan Bergmann1-5/+0
> Jan 18 15:18:25 <sberg> tml__, do you remember anything about > e3a07b8a6cc03b6d5063e4da5a474d8c91a84b0a ? looks odd to add configure > KEY=VALUE args to the environment > Jan 18 15:18:27 <IZBot> core - Include environment variables already in > autogen.sh's environment - > http://cgit.freedesktop.org/libreoffice/core/commit/?id=e3a07b8a6cc03b6d5063e4da5a474d8c91a84b0a > Jan 18 15:22:54 <tml__> sberg: not really any recollection, sorry > Jan 18 15:23:09 <tml__> sberg: are you sure this isn't what makes it possible > to have CC=clang etc in autogen.input? > Jan 18 15:24:07 <tml__> or maybe this is related to propagating stuff when > make re-runs autogen.sh? > Jan 18 15:24:28 <sberg> tml__, configure already takes care itself of its > KEY=VALUE command line arguments > Jan 18 15:24:36 <tml__> sad that I didn't write a better commit message > Jan 18 15:24:55 <tml__> feel free to revert it, and see if anybody notices;) > Jan 18 15:25:04 * cloph_away used it for CC/CXX and devtools repo > Jan 18 15:26:11 <tml__> cloph_away: yes, but I think sberg says that should > work anyway, even without that commit The only reading from ENV after that code in autogen.sh (both today and at the time of e3a07b8a6cc03b6d5063e4da5a474d8c91a84b0a) is the if (defined $ENV{NOCONFIGURE}) { print "Skipping configure process."; check, which would now no longer work if you pass NOCONFIGURE= as an argument to autogen.sh (in autogen.input or on the command line) instead of as an environment variable. Change-Id: If50639978190d219b063ff39f81e29d2054c0443 Reviewed-on: https://gerrit.libreoffice.org/48133 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2018-01-19Also strip leading whitespace from autogen.input linesStephan Bergmann1-0/+1
...which allows to align --enable/--disable switches on the part being en-/dis- abled, as in > --disable-assert-always-abort > --enable-avahi > --enable-breakpad > --enable-build-unowinreg > --disable-ccache for better readability Change-Id: I490402c74ea1ee535deee6ef79274b588b614820 Reviewed-on: https://gerrit.libreoffice.org/48130 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2017-09-22Revert "Goodbye autogen.lastrun"Tor Lillqvist1-2/+45
Welcome back autogen.lastrun. I just don't have the energy to convince tinderbox maintainers to fix their scripts. Oh well. This reverts commit 7496c83374f68148c62ac23a6e4c4c314d67273d.
2017-09-22Goodbye autogen.lastrunTor Lillqvist1-45/+2
Change-Id: I46b92baf88661d49da2905699b9639522c0940d8 Reviewed-on: https://gerrit.libreoffice.org/42418 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2017-08-17Fix typosAndrea Gelmini1-1/+1
Change-Id: Iaa9c0aea3ea1a239e378bd714ba335f91bb1faf3 Reviewed-on: https://gerrit.libreoffice.org/41194 Reviewed-by: Michael Stahl <mstahl@redhat.com> Tested-by: Michael Stahl <mstahl@redhat.com>
2017-05-17Revert "Don't worry if there is no distro-configs/Foo.conf"Stephan Bergmann1-3/+3
This reverts commit 47bca2f06434346b556d4aa14b16770e0ae990ab. I worry very much when some --with-distro=foo due to a typo doesn't do what I'd expect, and the non-fatal error message scrolled by so quickly nobody would notice. Conflicts: autogen.sh Change-Id: I8e0938e28e5aa23b59c82bbd10db0018e32a44dd Reviewed-on: https://gerrit.libreoffice.org/37701 Reviewed-by: Tor Lillqvist <tml@collabora.com> Tested-by: Jenkins <ci@libreoffice.org>
2017-05-17Show all available distro configsStephan Bergmann1-6/+18
Change-Id: Ibecd89bb12b3e488a4cf25766bd6ffe5a097f135
2016-12-14autogen.sh: Use STDOUT for --help output (as configure does)Mike Kaganski1-4/+4
Without this, first lines (up to "Other arguments passed directly to configure:" inclusive) go to STDERR, while the rest to STDOUT Change-Id: I95327d1ebe7941e5eb89f941ff1f9dc59297946b Reviewed-on: https://gerrit.libreoffice.org/31999 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2015-12-31lode: make sure LODE_HOME/opt/bin is in the PATH for aclocalNorbert Thiebaud1-0/+12
When using a LODE setup, LODE_HOME must be defined in the environment but setting LODE_HOME/opt/bin in the PATH is optional and really only necessary as a convinience to get the right 'make' in the PATH. configure.ac has code do deal with the absence of LODE_HOME/opt/bin in the PATH but autogen.sh did not hence was failing in this case, not finding aclocal. Change-Id: I7a4449504dc539bb055798a6e1aea5268c5fb046 Reviewed-on: https://gerrit.libreoffice.org/21003 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
2015-09-22autogen.sh: Display arguments for configure without apostrophesSamuel Mehrbrodt1-1/+1
So one can easily c&p the list of arguments Change-Id: I0555c58aa6aadc410a26309d6e51382eed390b2b
2015-03-08autogen.sh: better error message when src_path contains spacesMiklos Vajna1-0/+3
Change-Id: I921ffaf2ee4be73ecfffca8bc36cfae484b70a32
2014-11-13autogen: add --best-effort to help automation bridge option changes.Michael Meeks1-1/+9
When we add or deprecate configure --with / --enable options lots of scripts can break. Instead just add --best-effort to your autogen.sh command line to get warnings but not a failure in this case. Change-Id: I73d6ba53ee179384c2e34bf6780d074b04f70c06
2014-05-30strip trailing spaces when reading autogen.input/lastrunChristian Lohmaier1-0/+1
Change-Id: I9d47d2d4c6d2eb14968bfd79ef2a406c57afa21d
2014-04-23make it possible to do 'make -C sw/' even with builddir!=srcdirLuboš Luňák1-0/+16
The change in partial_build.mk assumes all the Makefile's using it are in builddir/<module>/ or builddir/external/<module> , these are differentiated by checking for ../External_module.mk . Change-Id: Iddc8fa2ec0842f181780f7491cf5a2244efd014a
2014-04-11Revert "make it possible to do 'make -C sw/' even with builddir!=srcdir"Stephan Bergmann1-7/+0
This reverts commit 11e881a63821ea209bda509d1e502d9ba270782d, which assumed that "all the Makefile's using it are in builddir/<module>/", which is not the case for the external/ sub-modules.
2014-03-23make it possible to do 'make -C sw/' even with builddir!=srcdirLuboš Luňák1-0/+7
The change in partial_build.mk assumes all the Makefile's using it are in builddir/<module>/ , but that seems to be the case. Change-Id: Iddc8fa2ec0842f181780f7491cf5a2244efd014a
2014-03-04Clarify autogen.sh messagesJan-Marek Glogowski1-3/+35
Actually warn the user, if we ignore provided configuration files. Also add an extended header to explain the expected behaviour. Change-Id: I630d858c2d24aa0341d04359b45029c7faa54675 Reviewed-on: https://gerrit.libreoffice.org/8446 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2013-11-13Generate configure before calling ./configure --helpArnaud Versini1-26/+26
Change-Id: I21a88802b6ca617a44def3bc96789eb97969c918 Reviewed-on: https://gerrit.libreoffice.org/6291 Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com> Tested-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
2013-07-26Ignore empty line in autogen.inputIsamu Mogi1-0/+2
Change-Id: I5a640c996779ba548c1b4772820eaa799537c1af Reviewed-on: https://gerrit.libreoffice.org/4991 Reviewed-by: Luboš Luňák <l.lunak@suse.cz> Tested-by: Luboš Luňák <l.lunak@suse.cz>
2013-05-08Make it a fatal error to pass unrecognized options to the configuryTor Lillqvist1-0/+1
It might hurt a bit in the beginning if you have been careless with keeping your autogen.input up-to-date, but I think this is a good idea. Change-Id: I6b89c887c94755ac6ef50f63e0438ecec7157516
2013-04-22aix stuffs stuff into /opt/freeware/share in defacto defaultCaolán McNamara1-0/+1
Change-Id: I2cd8e3498f81b96041c81cdc48ca6277ccbb210d
2013-04-04revert back to usign autogen.sh cmdline arguments if givenLuboš Luňák1-8/+8
This is a partial revert of ca0c54d0fe3812cec64e5c7cc83309d4397f5e0a . Ignoring cmdline arguments if autogen.* exists is broken for several reasons: - autogen.sh of every other package passes cmdline arguments to configure - that's because if I was bothered to give them, I want them used - there's no reason to prefer autogen.input now, given that autogen.input cannot be overwritten by autogen.sh, unlike autogen.lastrun , so there's no accidental loss of the switches - running autogen.sh --foo followed by autogen.sh --bar actually runs configure with --foo the second time too, because the first one creates autogen.lastrun and the second one first complains about the cmdline args, then complains about autogen.lastrun, and then uses it Change-Id: I5868610935d0312915be74602b6435eea069f937 Reviewed-on: https://gerrit.libreoffice.org/3190 Reviewed-by: Luboš Luňák <l.lunak@suse.cz> Tested-by: Luboš Luňák <l.lunak@suse.cz>
2013-04-03Make autogen.sh prefer to read an autogen.input fileTor Lillqvist1-18/+22
For backward compatibility, an autogen.lastrun file will still be used if it exists and autogen.input does not exist. The recommended workflow is now to keep the configuration parametets in autogen.input which is never written by autogen.sh. Most (?) developers used to treat autogen.lastrun as a valuable parameter file to be edited manually anyway, and not as an ad-hoc backup copy of command-line parameters last used. The name autogen.input better reflects this usage. Change-Id: I7e3c747fa95e9f2f0bc44036419aaab8f4ad01e7 Reviewed-on: https://gerrit.libreoffice.org/3111 Reviewed-by: Michael Meeks <michael.meeks@suse.com> Tested-by: Michael Meeks <michael.meeks@suse.com>
2012-12-11Prepare for read-only source buildNorbert Thiebaud1-16/+25
This patch allows to do mkdir <build_dir> cd <build_dir> <src_root>/autogen.sh make Only the remaining dmake modules are poluting the <src_root>... which will get eventually convererd to gmake... Change-Id: Iefd64732fa12e096d554cff4eee6b777deb92338 Reviewed-on: https://gerrit.libreoffice.org/1273 Reviewed-by: Luboš Luňák <l.lunak@suse.cz> Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2012-12-01Don't require configure to appear executableTor Lillqvist1-1/+1
Makes autogen.sh work on Cygwin when the build directory is on a vmware Shared Folder volume.
2012-11-17Fixed previous commit on autogen.sh default configEnrico Weigelt, metux ITS1-2/+1
Change-Id: I29cc49dcc284b462ac29d0d040e331f3e6d08e74 Reviewed-on: https://gerrit.libreoffice.org/1097 Reviewed-by: Rene Engelhard <rene@debian.org> Tested-by: Rene Engelhard <rene@debian.org>
2012-11-17autogen.sh: support for default distro configEnrico Weigelt, metux ITS1-0/+6
Always try to read distro-configs/default.conf (if existing) before any option parsing. That way, downstreams (distros, etc) can just place there site config into the tree without having to pass any additional options to autogen.sh, and even automatic invocations will always have the right parameters. Change-Id: Ic5bf68adc719476d374cf03e31e054b69c931b72 Reviewed-on: https://gerrit.libreoffice.org/1096 Reviewed-by: Andras Timar <atimar@suse.com> Tested-by: Andras Timar <atimar@suse.com>
2012-06-05Indentation clean upStephan Bergmann1-3/+3
Change-Id: I1e3633f5bbf6b3ad0cdb2005a2a5608f3265ffdb
2012-05-17autogen.sh: append aclocal arguments to ACLOCAL_FLAGS unconditionallyRuslan Kabatsayev1-5/+2
Change-Id: I2254628edfe213c3424dce2bc5d9f164752e913c
2012-03-29deal with symlinks in your PWD breaking gnumake dependenciesMichael Meeks1-0/+11
2012-03-13Fix authgen.sh to not clobber autogen.lastrun when using --helpJosh Heidenreich1-0/+8
Fix also works for -h and -?
2012-03-05Improvement to fdo#46565Thomas Collerton1-2/+8
2012-02-29fdo#46565: perl / autogen.sh should backup autogen.lastrunThomas Collerton1-0/+4
2012-02-17add macro for extracting mingw dll names from libtool filesDavid Tardon1-1/+5
Hardcoding dll names from SuSE Linux in configure.in is not good, because they might be slightly different on other systems (notably Fedora :-), or the libraries might be compiled with different dependencies.
2012-01-09autogen: sync vim modeline with emacs oneMiklos Vajna1-1/+1
2011-08-30Fix to create autogen.lastrun for a single argument case.Stephan Bergmann1-1/+1
2011-08-29autogen.sh: don't touch autogen.lastrun if it already existsMiklos Vajna1-1/+1
2011-08-28touch autogen.lastrun to make sure that such file exist before makeNorbert Thiebaud1-0/+4
2011-08-24Allow comments in the autogen.lastrun fileTor Lillqvist1-0/+2
2011-08-18have autogen.sh return an erro if configure failedNorbert Thiebaud1-1/+1
2011-07-03I doubt we need a ChangeLog fileTor Lillqvist1-2/+0
2011-07-03Include environment variables already in autogen.sh's environmentTor Lillqvist1-2/+9
2011-07-03Allow use of $ACLOCAL to override the name aclocalTor Lillqvist1-2/+5
Useful for instance when only aclocal-1.10 exists. But, systems that are broken like that will have lots of more problems, too. It is just a (sad?) fact that building LO on anything except those platforms that people work on constantly will require lots of tweaks. Many of the assumptions in various solenv .mk files for rare platforms are rather outdated and/or arbitrary, assuming a certain mix of more or less "official" additional tools.