summaryrefslogtreecommitdiff
path: root/buildconf
Commit message (Collapse)AuthorAgeFilesLines
* buildconf: minor tweaks commit 430527a1 follow-upYang Tse2011-12-231-0/+2
|
* buildconf: minor tweaksYang Tse2011-12-211-60/+64
|
* configure: libtool 1.5 tweaksYang Tse2011-12-151-17/+25
|
* buildconf: follow-up for commit 7e02f7fdYang Tse2011-11-301-10/+17
|
* buildconf: fix libtool 1.5.x warnings triggered with autoconf 2.6x or laterYang Tse2011-11-301-0/+15
| | | | | | | | | Using libtool 1.5.x (x < 26) with autoconf 2.6x or later generates warnings due to some libtool variables not following naming convention for variables that will be cached. This is addressed renaming a couple of variables to make these follow expected naming convention.
* buildconf: warn about autoconf 2.67 and 2.68 generating bad/unusable scriptsYang Tse2011-10-061-2/+12
|
* curl tool: code moved to tool_*.[ch] filesYang Tse2011-10-051-1/+1
|
* Fix spelling errors in buildconfFabian Keil2011-04-211-1/+1
| | | | Found with codespell.
* symbol-scan: use configure script knowledge about how to run the C preprocessorYang Tse2010-11-251-0/+1
|
* buildconf: MAC OS X requires libtool version 1.5.26 or newerYang Tse2010-11-111-0/+6
| | | | | MAC OS X requires libtool version 1.5.26 or newer, otherwise configure will mishandle *.dSYM directories when it runs.
* In the m4 detection line, factor out the 2>dev/nullFabian Keil2010-08-281-1/+1
|
* If m4 doesn't support --version, try if gm4 does.Fabian Keil2010-08-281-1/+1
|
* If the m4 version isn't recognized at all, just say soFabian Keil2010-08-281-1/+5
| | | | 'm4 version found. You need a GNU m4 installed!' is a bit confusing.
* findtool: file name as a full path requires a slashDaniel Stenberg2010-05-091-4/+10
| | | | | | | | | | Kalle Vahlman's patch applied a while ago broke how the findtool function searches for tools, as it would always check if "$file" was present first, which thus made the bad assumption that a file in the current directory would be a match. I noticed when it found 'libtool' in the current directory but libtoolize is not there, which confused the script.
* Allow tools to be defined with full path in buildconfKalle Vahlman2010-04-261-0/+5
| | | | | | This is required in Scratchbox where LIBTOOL=/targets/links/arch_tools/bin/libtool is set in the environment.
* restore executable bits on some filesDaniel Stenberg2010-03-241-0/+0
|
* remove the CVSish $Id$ linesDaniel Stenberg2010-03-241-1/+0
|
* Add a couple of renamed files to the removal listYang Tse2009-11-151-0/+2
|
* renamed generated config.h to curl_config.h in order to avoid clashes when ↵Gunter Knauf2009-07-141-4/+4
| | | | libcurl is used with other projects which also have a config.h.
* Adjusted libtool version parsing due to libtool --version now alsoYang Tse2009-06-081-41/+19
| | | | | | reporting package version in parentheses which confused this script. Remove debug tracing used to debug this.
* debug test a non-greedy patternYang Tse2009-06-071-3/+3
|
* Add some debug tracingYang Tse2009-06-061-0/+19
|
* remove the ofending regexpYang Tse2009-06-061-1/+1
|
* remove line not intended to be committedYang Tse2009-06-061-2/+0
|
* attempt to fix regexYang Tse2009-06-061-1/+3
|
* Adjusted libtool version parsing due to libtool --version now alsoYang Tse2009-06-061-1/+1
| | | | reporting package name in parentheses which confused this script.
* Depending on the libtool and automake versions being used config.guess getsYang Tse2009-06-051-52/+57
| | | | | | | | installed in the subdirectory at different stages. With some versions it is installed when libtoolize finishes, but with others it is not installed until automake has finished. So we can not attempt to use config.guess until the very last buildconf stage.
* Remove more generated files.Yang Tse2009-06-031-3/+5
| | | | Yet unknown error might leave libtool-like files in source directory.
* Remove more generated filesYang Tse2009-06-031-0/+1
|
* Remove all generated 'Makefile' files.Yang Tse2009-06-031-0/+1
| | | | This can be done now that no file with such name exists in CVS tree.
* Remove more generated filesYang Tse2009-06-031-0/+4
|
* Temporarily disable config.guess related checksYang Tse2009-06-011-0/+4
|
* HP-UX requires libtool version 1.5.24 or newerYang Tse2009-06-011-0/+48
|
* - Andreas Farber made the 'buildconf' script check for the presence of m4Daniel Stenberg2009-03-091-0/+5
| | | | | | | scripts to make it detect a bad checkout earlier. People with older checkouts who don't do cvs update with the -d option won't get the new dirs and then will get funny outputs that can be a bit hard to understand and fix.
* Remove following files generated on previous buildconf run:Yang Tse2009-02-131-0/+4
| | | | ltoptions.m4 ltsugar.m4 ltversion.m4 lt~obsolete.m4
* Only care about the first line of libtool --version as otherwise this scriptDaniel Stenberg2009-01-081-2/+2
| | | | | get fooled by libtool 2, and at least libtool 1.5.2x do output the interesting version string in the first line.
* curlbuild.h is a generated file on configure-capable systemsYang Tse2008-08-141-0/+1
|
* Prevent buildconf from removing 'Makefile' and 'missing' files. This would blowYang Tse2008-08-071-2/+0
| | | | away our CVS checked 'missing' file and also CVS checked 'hiper/Makefile'.
* Validate that autom4te and autoconf versions match.Yang Tse2008-08-051-74/+60
| | | | | | | | Validate that aclocal and automake versions match. Improve removal of previous run generated files. Remove verbose debug logging of aclocal on Solaris.
* This line was for local testing, not intended to be committed.Yang Tse2008-08-011-1/+0
|
* Ensure that reserved keyword AC_DEFUN is only used for its purpose.Yang Tse2008-08-011-0/+1
|
* Reinstate the 'aclocal -I m4' in buildconf and 'ACLOCAL_AMFLAGS = -I m4' way ofYang Tse2008-07-301-35/+1
| | | | | including our local m4/reentrant.m4 file. This even takes care of including the file in the distribution tarball.
* Show autom4te and aclocal versions.Yang Tse2008-07-301-3/+18
| | | | Set SED for Solaris to gsed if available.
* For testing purposes on SunOS systems; directly feed acinclude.m4 withYang Tse2008-07-291-0/+12
| | | | reentrant.m4 and remove reentrant.m4 before calling aclocal.
* For debugging purposes, show all sed's available in PATH on SunOS systems.Yang Tse2008-07-291-3/+22
|
* Tests done using 'aclocal -I m4' in buildconf and 'ACLOCAL_AMFLAGS = -I m4Yang Tse2008-07-291-10/+1
| | | | | | | | | | | | in top Makefile.am triggered a problem that prevented aclocal from running successfully on SunOS 5.10 with GNU m4 1.4.5 and GNU Autoconf 2.61 A tarball which reproduces mentioned problem is the one dated July-28-2008 http://cool.haxx.se/curl-daily/curl-7.19.0-20080728.tar.gz We actually don't need all the bells and whistles that the above mechanism provides. We only need to include our m4/reentrant.m4 file in acinclude.m4 so here we go with this simpler mechanism.
* Ensure that buildconf runs from the subdirectory where configure.ac livesYang Tse2008-07-281-0/+12
|
* Remove files generated on previous buildconf/configure run,Yang Tse2008-07-281-1/+76
| | | | and for debugging purposes show ACLOCAL_FLAGS.
* When calling aclocal, user defined ACLOCAL_FLAGS will now precede ours.Yang Tse2008-07-271-2/+7
|
* For debugging purposes, run aclocal in verbose mode on SunOS systems.Yang Tse2008-07-271-1/+6
|
View Lorry Controller Status