History log of /flex/autogen.sh (Results 1 - 23 of 23)
Revision Date Author Comments
# 9be1980e 21-Sep.-2018 Explorer09 <explorer09@gmail.com>

build: Fix autogen.sh $LIBTOOLIZE detection logic

* Don't silence `libtoolize --version` error message. It would be
useful for diagnosing any problem when `libtoolize --version` fails.

build: Fix autogen.sh $LIBTOOLIZE detection logic

* Don't silence `libtoolize --version` error message. It would be
useful for diagnosing any problem when `libtoolize --version` fails.
(libtoolize not found? No permission to execute? Now you know which
error it is.)
* Change the guessing code of libtoolize program name to a loop.
It'll perform silently.
* Silence the `libtoolize --version` output when it succeeds.

Signed-off-by: Kang-che Sung <explorer09@gmail.com>

show more ...


# 8900923e 21-Sep.-2018 Explorer09 <explorer09@gmail.com>

build: autogen.sh libtoolize invocation minor fixes.

* Let autogen.sh error message go to stderr.
* Don't quote the variable $LIBTOOLIZE when invoking it. This would
allow invocation

build: autogen.sh libtoolize invocation minor fixes.

* Let autogen.sh error message go to stderr.
* Don't quote the variable $LIBTOOLIZE when invoking it. This would
allow invocation when LIBTOOLIZE='a-future-libtoolize --gnu-compat'

Signed-off-by: Kang-che Sung <explorer09@gmail.com>

show more ...


# 4efcf28e 02-May-2017 Simon Sobisch <simonsobisch@web.de>

build: only touch ChangeLog if it does not exist


# 0a9687d1 02-May-2017 Simon Sobisch <simonsobisch@web.de>

build: check for how to call libtoolize.

Previously, we would call libtoolize and if that failed, we would call
glibtoolize since some platforms have the libtoolize program under
tha

build: check for how to call libtoolize.

Previously, we would call libtoolize and if that failed, we would call
glibtoolize since some platforms have the libtoolize program under
that name.

Instead, we check to see if the environment variable LIBTOOLIZE is set
and use that if so. Otherwise, we try to find a program "libtoolize"
on the path and failing that glibtoolize. We alert the user if no
suitable program can be found.

show more ...


# 7ddfe81a 04-Dec.-2015 Akim Demaille <akim@lrde.epita.fr>

Called glibtoolize if libtoolize run fails.

On Mac OS X, libtoolize is known as glibtoolize. In cases where libtoolize is not present, then calling glibtoolize when bootstrapping the build s

Called glibtoolize if libtoolize run fails.

On Mac OS X, libtoolize is known as glibtoolize. In cases where libtoolize is not present, then calling glibtoolize when bootstrapping the build system gives more folks a shot at getting flex built from the ground up.

show more ...


# 589bb430 10-Nov.-2015 Will Estes <westes575@gmail.com>

Called libtoolize directly because autoreconf fails to pick up LT_INIT properly


# d89def42 26-Aug.-2012 Will Estes <westes575@gmail.com>

require gettext 0.18; force autoreconf in autogen.sh; resolves #3561759

Autoconf had trouble finding the shared libraries for gettext. Using
gettext 0.18 fixes that.

When updati

require gettext 0.18; force autoreconf in autogen.sh; resolves #3561759

Autoconf had trouble finding the shared libraries for gettext. Using
gettext 0.18 fixes that.

When updating the gettext version number, autoreconf could fail to
update files, since autopoint would assume the gettext-related files had
been locally modified. Passing --force prevents that from happening.

show more ...


# fe229c62 11-May-2007 Will Estes <wlestes@users.sourceforge.net>

remove --force option from autogen.sh; much faster without it


# 57378d55 13-Feb.-2007 Will Estes <wlestes@users.sourceforge.net>

restore --install option to autogen.sh since --force does not imply --install


# 15900969 13-Feb.-2007 Will Estes <wlestes@users.sourceforge.net>

call autoreconf with --force instead of --install


# f8c43bec 27-Sep.-2002 Will Estes <wlestes@users.sourceforge.net>

use autoreconf instead of calling individual utilities separately


# 0196df98 08-Aug.-2002 Will Estes <wlestes@users.sourceforge.net>

if autopoint is going to run automatically, it's going to need to be able to update existing files


# a0df3fc3 08-Aug.-2002 Will Estes <wlestes@users.sourceforge.net>

autopoint now works so let's let it run the gettext show


# 1ba500e9 22-Jul.-2002 Will Estes <wlestes@users.sourceforge.net>

rollback on configure.in and autogen.sh because autpoint is broken


# 70c824ea 19-Jul.-2002 Will Estes <wlestes@users.sourceforge.net>

ok, we're going to start using autopoint, but the tree is going to undergo some changes after this


# a18c8b7b 08-Apr.-2002 Will Estes <wlestes@users.sourceforge.net>

test suite changes


# 043a8337 12-Mar.-2002 Will Estes <wlestes@users.sourceforge.net>

mostly, changes for gettext


# ddbcdd5c 01-Aug.-2001 Will Estes <wlestes@users.sourceforge.net>

fake automake into believing that ChangeLog already exists


# bb256b35 24-Jul.-2001 Will Estes <wlestes@users.sourceforge.net>

adjust to automake's idea of the world


# abb21f6d 23-Jul.-2001 Will Estes <wlestes@users.sourceforge.net>

we need to do the same thing in each directory


# 9939ef10 17-Jun.-2001 Will Estes <wlestes@users.sourceforge.net>

clarify usage instructions; prepare tests/ as well


# 1d7763d7 17-Jun.-2001 Will Estes <wlestes@users.sourceforge.net>

change copyright/license notices as per Vern's response to Theo


# 0ad5a842 01-May-2001 Will Estes <wlestes@users.sourceforge.net>

initial attempt at a bootstrap script for developers