623
623
/* HP/UX 9 (%@#!) writes to sscanf strings */
624
624
tmp_version = g_strdup("$min_glib_version");
625
@@ -12664,16 +12691,19 @@
625
@@ -12655,14 +12682,17 @@
626
627
if test -n "$PKG_CONFIG" && \
627
628
{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gtk-sharp-2.0 >= \$GTKSHARP_REQUIRED
628
gnome-sharp-2.0 >= \$GTKSHARP_REQUIRED
629
- glade-sharp-2.0 >= \$GTKSHARP_REQUIRED\""; } >&5
630
+ glade-sharp-2.0 >= \$GTKSHARP_REQUIRED
631
+ launchpad-integration-sharp\""; } >&5
629
- gnome-sharp-2.0 >= \$GTKSHARP_REQUIRED\""; } >&5
630
+ gnome-sharp-2.0 >= \$GTKSHARP_REQUIRED
631
+ launchpad-integration-sharp\""; } >&5
632
632
($PKG_CONFIG --exists --print-errors "gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
633
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
634
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED") 2>&5
635
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
636
+ launchpad-integration-sharp") 2>&5
633
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED") 2>&5
634
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
635
+ launchpad-integration-sharp") 2>&5
638
637
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
639
638
test $ac_status = 0; }; then
640
639
pkg_cv_GBRAINY_CFLAGS=`$PKG_CONFIG --cflags "gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
641
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
642
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED" 2>/dev/null`
643
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
644
+ launchpad-integration-sharp" 2>/dev/null`
640
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED" 2>/dev/null`
641
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
642
+ launchpad-integration-sharp" 2>/dev/null`
648
@@ -12688,16 +12718,19 @@
646
@@ -12676,14 +12706,17 @@
649
648
if test -n "$PKG_CONFIG" && \
650
649
{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"gtk-sharp-2.0 >= \$GTKSHARP_REQUIRED
651
gnome-sharp-2.0 >= \$GTKSHARP_REQUIRED
652
- glade-sharp-2.0 >= \$GTKSHARP_REQUIRED\""; } >&5
653
+ glade-sharp-2.0 >= \$GTKSHARP_REQUIRED
654
+ launchpad-integration-sharp\""; } >&5
650
- gnome-sharp-2.0 >= \$GTKSHARP_REQUIRED\""; } >&5
651
+ gnome-sharp-2.0 >= \$GTKSHARP_REQUIRED
652
+ launchpad-integration-sharp\""; } >&5
655
653
($PKG_CONFIG --exists --print-errors "gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
656
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
657
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED") 2>&5
658
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
659
+ launchpad-integration-sharp") 2>&5
654
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED") 2>&5
655
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
656
+ launchpad-integration-sharp") 2>&5
661
658
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
662
659
test $ac_status = 0; }; then
663
660
pkg_cv_GBRAINY_LIBS=`$PKG_CONFIG --libs "gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
664
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
665
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED" 2>/dev/null`
666
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
667
+ launchpad-integration-sharp" 2>/dev/null`
661
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED" 2>/dev/null`
662
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
663
+ launchpad-integration-sharp" 2>/dev/null`
671
@@ -12718,18 +12751,21 @@
667
@@ -12703,16 +12736,19 @@
672
669
if test $_pkg_short_errors_supported = yes; then
673
670
GBRAINY_PKG_ERRORS=`$PKG_CONFIG --short-errors --errors-to-stdout --print-errors "gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
674
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
675
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED"`
676
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
677
+ launchpad-integration-sharp"`
671
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED"`
672
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
673
+ launchpad-integration-sharp"`
679
675
GBRAINY_PKG_ERRORS=`$PKG_CONFIG --errors-to-stdout --print-errors "gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
680
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
681
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED"`
682
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
683
+ launchpad-integration-sharp"`
676
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED"`
677
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
678
+ launchpad-integration-sharp"`
685
680
# Put the nasty error message in config.log where it belongs
686
681
echo "$GBRAINY_PKG_ERRORS" >&5
688
683
as_fn_error "Package requirements (gtk-sharp-2.0 >= $GTKSHARP_REQUIRED
689
gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
690
- glade-sharp-2.0 >= $GTKSHARP_REQUIRED) were not met:
691
+ glade-sharp-2.0 >= $GTKSHARP_REQUIRED
692
+ launchpad-integration-sharp) were not met:
684
- gnome-sharp-2.0 >= $GTKSHARP_REQUIRED) were not met:
685
+ gnome-sharp-2.0 >= $GTKSHARP_REQUIRED
686
+ launchpad-integration-sharp) were not met:
694
688
$GBRAINY_PKG_ERRORS
696
@@ -14293,7 +14329,7 @@
690
@@ -14276,7 +14312,7 @@
697
691
# values after options handling.
699
This file was extended by gbrainy $as_me 1.30, which was
693
This file was extended by gbrainy $as_me 1.40, which was
700
694
-generated by GNU Autoconf 2.64. Invocation command line was
701
695
+generated by GNU Autoconf 2.65. Invocation command line was
703
697
CONFIG_FILES = $CONFIG_FILES
704
698
CONFIG_HEADERS = $CONFIG_HEADERS
705
@@ -14333,6 +14369,7 @@
699
@@ -14316,6 +14352,7 @@
707
701
-h, --help print this help, then exit
708
702
-V, --version print version number and configuration settings, then exit
752
746
s/["\\]/\\&/g; s/^/"/; s/$/"/
754
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/data/Makefile.in gbrainy-1.30.new/data/Makefile.in
755
--- gbrainy-1.30/data/Makefile.in 2010-01-03 01:18:16.000000000 +1100
756
+++ gbrainy-1.30.new/data/Makefile.in 2010-02-05 16:19:22.879617576 +1100
758
-# Makefile.in generated by automake 1.11 from Makefile.am.
759
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
762
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
763
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/help/Makefile.in gbrainy-1.30.new/help/Makefile.in
764
--- gbrainy-1.30/help/Makefile.in 2010-01-06 19:54:11.000000000 +1100
765
+++ gbrainy-1.30.new/help/Makefile.in 2010-02-05 16:19:22.952093404 +1100
767
-# Makefile.in generated by automake 1.11 from Makefile.am.
768
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
771
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
772
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/ltmain.sh gbrainy-1.30.new/ltmain.sh
773
--- gbrainy-1.30/ltmain.sh 2010-01-02 20:40:35.000000000 +1100
774
+++ gbrainy-1.30.new/ltmain.sh 2010-02-05 16:19:19.849593718 +1100
748
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/data/Makefile.in gbrainy-1.40.new/data/Makefile.in
749
--- gbrainy-1.40/data/Makefile.in 2010-02-27 06:27:54.000000000 +1100
750
+++ gbrainy-1.40.new/data/Makefile.in 2010-03-08 11:10:22.463894662 +1100
752
-# Makefile.in generated by automake 1.11 from Makefile.am.
753
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
756
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
757
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/help/Makefile.in gbrainy-1.40.new/help/Makefile.in
758
--- gbrainy-1.40/help/Makefile.in 2010-02-27 06:27:54.000000000 +1100
759
+++ gbrainy-1.40.new/help/Makefile.in 2010-03-08 11:10:22.553921045 +1100
761
-# Makefile.in generated by automake 1.11 from Makefile.am.
762
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
765
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
766
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/INSTALL gbrainy-1.40.new/INSTALL
767
--- gbrainy-1.40/INSTALL 2010-01-08 08:02:12.000000000 +1100
768
+++ gbrainy-1.40.new/INSTALL 2010-02-02 11:59:15.000000000 +1100
770
+Installation Instructions
771
+*************************
773
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
774
+2006, 2007, 2008, 2009 Free Software Foundation, Inc.
776
+ Copying and distribution of this file, with or without modification,
777
+are permitted in any medium without royalty provided the copyright
778
+notice and this notice are preserved. This file is offered as-is,
779
+without warranty of any kind.
784
- These are generic installation instructions.
785
+ Briefly, the shell commands `./configure; make; make install' should
786
+configure, build, and install this package. The following
787
+more-detailed instructions are generic; see the `README' file for
788
+instructions specific to this package. Some packages provide this
789
+`INSTALL' file but do not implement all of the features documented
790
+below. The lack of an optional feature in a given package is not
791
+necessarily a bug. More recommendations for GNU packages can be found
792
+in *note Makefile Conventions: (standards)Makefile Conventions.
794
The `configure' shell script attempts to guess correct values for
795
various system-dependent variables used during compilation. It uses
796
those values to create a `Makefile' in each directory of the package.
797
It may also create one or more `.h' files containing system-dependent
798
definitions. Finally, it creates a shell script `config.status' that
799
-you can run in the future to recreate the current configuration, a file
800
-`config.cache' that saves the results of its tests to speed up
801
-reconfiguring, and a file `config.log' containing compiler output
802
-(useful mainly for debugging `configure').
803
+you can run in the future to recreate the current configuration, and a
804
+file `config.log' containing compiler output (useful mainly for
805
+debugging `configure').
807
+ It can also use an optional file (typically called `config.cache'
808
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
809
+the results of its tests to speed up reconfiguring. Caching is
810
+disabled by default to prevent problems with accidental use of stale
813
If you need to do unusual things to compile the package, please try
814
to figure out how `configure' could check whether to do them, and mail
815
diffs or instructions to the address given in the `README' so they can
816
-be considered for the next release. If at some point `config.cache'
817
-contains results you don't want to keep, you may remove or edit it.
819
- The file `configure.in' is used to create `configure' by a program
820
-called `autoconf'. You only need `configure.in' if you want to change
821
-it or regenerate `configure' using a newer version of `autoconf'.
822
+be considered for the next release. If you are using the cache, and at
823
+some point `config.cache' contains results you don't want to keep, you
824
+may remove or edit it.
826
+ The file `configure.ac' (or `configure.in') is used to create
827
+`configure' by a program called `autoconf'. You need `configure.ac' if
828
+you want to change it or regenerate `configure' using a newer version
831
-The simplest way to compile this package is:
832
+ The simplest way to compile this package is:
834
1. `cd' to the directory containing the package's source code and type
835
- `./configure' to configure the package for your system. If you're
836
- using `csh' on an old version of System V, you might need to type
837
- `sh ./configure' instead to prevent `csh' from trying to execute
838
- `configure' itself.
839
+ `./configure' to configure the package for your system.
841
- Running `configure' takes awhile. While running, it prints some
842
- messages telling which features it is checking for.
843
+ Running `configure' might take a while. While running, it prints
844
+ some messages telling which features it is checking for.
846
2. Type `make' to compile the package.
848
3. Optionally, type `make check' to run any self-tests that come with
850
+ the package, generally using the just-built uninstalled binaries.
852
4. Type `make install' to install the programs and any data files and
854
+ documentation. When installing into a prefix owned by root, it is
855
+ recommended that the package be configured and built as a regular
856
+ user, and only the `make install' phase executed with root
859
+ 5. Optionally, type `make installcheck' to repeat any self-tests, but
860
+ this time using the binaries in their final installed location.
861
+ This target does not install anything. Running this target as a
862
+ regular user, particularly if the prior `make install' required
863
+ root privileges, verifies that the installation completed
866
- 5. You can remove the program binaries and object files from the
867
+ 6. You can remove the program binaries and object files from the
868
source code directory by typing `make clean'. To also remove the
869
files that `configure' created (so you can compile the package for
870
a different kind of computer), type `make distclean'. There is
872
all sorts of other programs in order to regenerate files that came
873
with the distribution.
875
+ 7. Often, you can also type `make uninstall' to remove the installed
876
+ files again. In practice, not all packages have tested that
877
+ uninstallation works correctly, even though it is required by the
878
+ GNU Coding Standards.
880
+ 8. Some packages, particularly those that use Automake, provide `make
881
+ distcheck', which can by used by developers to test that all other
882
+ targets like `make install' and `make uninstall' work correctly.
883
+ This target is generally not run by end users.
885
Compilers and Options
886
=====================
888
Some systems require unusual options for compilation or linking that
889
-the `configure' script does not know about. You can give `configure'
890
-initial values for variables by setting them in the environment. Using
891
-a Bourne-compatible shell, you can do that on the command line like
893
- CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
894
+the `configure' script does not know about. Run `./configure --help'
895
+for details on some of the pertinent environment variables.
897
+ You can give `configure' initial values for configuration parameters
898
+by setting variables in the command line or in the environment. Here
901
-Or on systems that have the `env' program, you can do it like this:
902
- env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
903
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
905
+ *Note Defining Variables::, for more details.
907
Compiling For Multiple Architectures
908
====================================
910
You can compile the package for more than one kind of computer at the
911
same time, by placing the object files for each architecture in their
912
-own directory. To do this, you must use a version of `make' that
913
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
914
+own directory. To do this, you can use GNU `make'. `cd' to the
915
directory where you want the object files and executables to go and run
916
the `configure' script. `configure' automatically checks for the
917
-source code in the directory that `configure' is in and in `..'.
918
+source code in the directory that `configure' is in and in `..'. This
919
+is known as a "VPATH" build.
921
+ With a non-GNU `make', it is safer to compile the package for one
922
+architecture at a time in the source code directory. After you have
923
+installed the package for one architecture, use `make distclean' before
924
+reconfiguring for another architecture.
926
+ On MacOS X 10.5 and later systems, you can create libraries and
927
+executables that work on multiple system types--known as "fat" or
928
+"universal" binaries--by specifying multiple `-arch' options to the
929
+compiler but only a single `-arch' option to the preprocessor. Like
932
- If you have to use a `make' that does not supports the `VPATH'
933
-variable, you have to compile the package for one architecture at a time
934
-in the source code directory. After you have installed the package for
935
-one architecture, use `make distclean' before reconfiguring for another
937
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
938
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
939
+ CPP="gcc -E" CXXCPP="g++ -E"
941
+ This is not guaranteed to produce working output in all cases, you
942
+may have to build one architecture at a time and combine the results
943
+using the `lipo' tool if you have problems.
948
- By default, `make install' will install the package's files in
949
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
950
-installation prefix other than `/usr/local' by giving `configure' the
951
-option `--prefix=PATH'.
952
+ By default, `make install' installs the package's commands under
953
+`/usr/local/bin', include files under `/usr/local/include', etc. You
954
+can specify an installation prefix other than `/usr/local' by giving
955
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
958
You can specify separate installation prefixes for
959
architecture-specific files and architecture-independent files. If you
960
-give `configure' the option `--exec-prefix=PATH', the package will use
961
-PATH as the prefix for installing programs and libraries.
962
-Documentation and other data files will still use the regular prefix.
963
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
964
+PREFIX as the prefix for installing programs and libraries.
965
+Documentation and other data files still use the regular prefix.
967
In addition, if you use an unusual directory layout you can give
968
-options like `--bindir=PATH' to specify different values for particular
969
+options like `--bindir=DIR' to specify different values for particular
970
kinds of files. Run `configure --help' for a list of the directories
971
-you can set and what kinds of files go in them.
972
+you can set and what kinds of files go in them. In general, the
973
+default for these options is expressed in terms of `${prefix}', so that
974
+specifying just `--prefix' will affect all of the other directory
975
+specifications that were not explicitly provided.
977
+ The most portable way to affect installation locations is to pass the
978
+correct locations to `configure'; however, many packages provide one or
979
+both of the following shortcuts of passing variable assignments to the
980
+`make install' command line to change installation locations without
981
+having to reconfigure or recompile.
983
+ The first method involves providing an override variable for each
984
+affected directory. For example, `make install
985
+prefix=/alternate/directory' will choose an alternate location for all
986
+directory configuration variables that were expressed in terms of
987
+`${prefix}'. Any directories that were specified during `configure',
988
+but not in terms of `${prefix}', must each be overridden at install
989
+time for the entire installation to be relocated. The approach of
990
+makefile variable overrides for each directory variable is required by
991
+the GNU Coding Standards, and ideally causes no recompilation.
992
+However, some platforms have known limitations with the semantics of
993
+shared libraries that end up requiring recompilation when using this
994
+method, particularly noticeable in packages that use GNU Libtool.
996
+ The second method involves providing the `DESTDIR' variable. For
997
+example, `make install DESTDIR=/alternate/directory' will prepend
998
+`/alternate/directory' before all installation names. The approach of
999
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
1000
+does not work on platforms that have drive letters. On the other hand,
1001
+it does better at avoiding recompilation issues, and works well even
1002
+when some directory options were not specified in terms of `${prefix}'
1003
+at `configure' time.
1008
If the package supports it, you can cause programs to be installed
1009
with an extra prefix or suffix on their names by giving `configure' the
1010
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
1015
Some packages pay attention to `--enable-FEATURE' options to
1016
`configure', where FEATURE indicates an optional part of the package.
1017
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
1018
@@ -119,25 +208,75 @@
1019
you can use the `configure' options `--x-includes=DIR' and
1020
`--x-libraries=DIR' to specify their locations.
1022
+ Some packages offer the ability to configure how verbose the
1023
+execution of `make' will be. For these packages, running `./configure
1024
+--enable-silent-rules' sets the default to minimal output, which can be
1025
+overridden with `make V=1'; while running `./configure
1026
+--disable-silent-rules' sets the default to verbose, which can be
1027
+overridden with `make V=0'.
1032
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU
1033
+CC is not installed, it is recommended to use the following options in
1034
+order to use an ANSI C compiler:
1036
+ ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
1038
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
1040
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
1041
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
1042
+a workaround. If GNU CC is not installed, it is therefore recommended
1045
+ ./configure CC="cc"
1047
+and if that doesn't work, try
1049
+ ./configure CC="cc -nodtk"
1051
+ On Solaris, don't put `/usr/ucb' early in your `PATH'. This
1052
+directory contains several dysfunctional programs; working variants of
1053
+these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
1054
+in your `PATH', put it _after_ `/usr/bin'.
1056
+ On Haiku, software installed for all users goes in `/boot/common',
1057
+not `/usr/local'. It is recommended to use the following options:
1059
+ ./configure --prefix=/boot/common
1061
Specifying the System Type
1062
==========================
1064
- There may be some features `configure' can not figure out
1065
-automatically, but needs to determine by the type of host the package
1066
-will run on. Usually `configure' can figure that out, but if it prints
1067
-a message saying it can not guess the host type, give it the
1068
-`--host=TYPE' option. TYPE can either be a short name for the system
1069
-type, such as `sun4', or a canonical name with three fields:
1070
+ There may be some features `configure' cannot figure out
1071
+automatically, but needs to determine by the type of machine the package
1072
+will run on. Usually, assuming the package is built to be run on the
1073
+_same_ architectures, `configure' can figure that out, but if it prints
1074
+a message saying it cannot guess the machine type, give it the
1075
+`--build=TYPE' option. TYPE can either be a short name for the system
1076
+type, such as `sun4', or a canonical name which has the form:
1080
-See the file `config.sub' for the possible values of each field. If
1081
+where SYSTEM can have one of these forms:
1086
+ See the file `config.sub' for the possible values of each field. If
1087
`config.sub' isn't included in this package, then this package doesn't
1088
-need to know the host type.
1089
+need to know the machine type.
1091
- If you are building compiler tools for cross-compiling, you can also
1092
-use the `--target=TYPE' option to select the type of system they will
1093
-produce code for and the `--build=TYPE' option to select the type of
1094
-system on which you are compiling the package.
1095
+ If you are _building_ compiler tools for cross-compiling, you should
1096
+use the option `--target=TYPE' to select the type of system they will
1099
+ If you want to _use_ a cross compiler, that generates code for a
1100
+platform different from the build platform, you should specify the
1101
+"host" platform (i.e., that on which the generated programs will
1102
+eventually be run) with `--host=TYPE'.
1106
@@ -150,19 +289,55 @@
1107
`CONFIG_SITE' environment variable to the location of the site script.
1108
A warning: not all `configure' scripts look for a site script.
1114
+ Variables not defined in a site shell script can be set in the
1115
+environment passed to `configure'. However, some packages may run
1116
+configure again during the build, and the customized values of these
1117
+variables may be lost. In order to avoid this problem, you should set
1118
+them in the `configure' command line, using `VAR=value'. For example:
1120
+ ./configure CC=/usr/local2/bin/gcc
1122
+causes the specified `gcc' to be used as the C compiler (unless it is
1123
+overridden in the site shell script).
1125
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
1126
+an Autoconf bug. Until the bug is fixed you can use this workaround:
1128
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
1130
+`configure' Invocation
1131
+======================
1133
`configure' recognizes the following options to control how it
1136
-`--cache-file=FILE'
1137
- Use and save the results of the tests in FILE instead of
1138
- `./config.cache'. Set FILE to `/dev/null' to disable caching, for
1139
- debugging `configure'.
1142
- Print a summary of the options to `configure', and exit.
1144
+ Print a summary of all of the options to `configure', and exit.
1148
+ Print a summary of the options unique to this package's
1149
+ `configure', and exit. The `short' variant lists options used
1150
+ only in the top level, while the `recursive' variant lists options
1151
+ also present in any nested packages.
1155
+ Print the version of Autoconf used to generate the `configure'
1158
+`--cache-file=FILE'
1159
+ Enable the cache: use and save the results of the tests in FILE,
1160
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
1165
+ Alias for `--cache-file=config.cache'.
1169
@@ -175,8 +350,16 @@
1170
Look for the package's source code in directory DIR. Usually
1171
`configure' can determine that directory automatically.
1174
- Print the version of Autoconf used to generate the `configure'
1177
+ Use DIR as the installation prefix. *note Installation Names::
1178
+ for more details, including other options available for fine-tuning
1179
+ the installation locations.
1183
+ Run the configure checks, but stop before creating any output
1186
+`configure' also accepts some other, not widely useful, options. Run
1187
+`configure --help' for more details.
1189
-`configure' also accepts some other, not widely useful, options.
1190
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/ltmain.sh gbrainy-1.40.new/ltmain.sh
1191
--- gbrainy-1.40/ltmain.sh 2010-02-27 05:36:54.000000000 +1100
1192
+++ gbrainy-1.40.new/ltmain.sh 2010-01-06 21:19:45.000000000 +1100
776
1194
# Generated from ltmain.m4sh.
861
1279
unzip $(distdir).zip ;;\
863
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/src/Clients/Classical/Makefile.in gbrainy-1.30.new/src/Clients/Classical/Makefile.in
864
--- gbrainy-1.30/src/Clients/Classical/Makefile.in 2010-01-03 01:18:17.000000000 +1100
865
+++ gbrainy-1.30.new/src/Clients/Classical/Makefile.in 2010-02-05 16:19:23.002092707 +1100
867
-# Makefile.in generated by automake 1.11 from Makefile.am.
868
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
871
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
872
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/src/Core/Makefile.in gbrainy-1.30.new/src/Core/Makefile.in
873
--- gbrainy-1.30/src/Core/Makefile.in 2010-01-03 01:18:17.000000000 +1100
874
+++ gbrainy-1.30.new/src/Core/Makefile.in 2010-02-05 16:19:23.052093685 +1100
876
-# Makefile.in generated by automake 1.11 from Makefile.am.
877
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
880
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
881
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/src/Games/Makefile.in gbrainy-1.30.new/src/Games/Makefile.in
882
--- gbrainy-1.30/src/Games/Makefile.in 2010-01-03 01:18:17.000000000 +1100
883
+++ gbrainy-1.30.new/src/Games/Makefile.in 2010-02-05 16:19:23.092093602 +1100
885
-# Makefile.in generated by automake 1.11 from Makefile.am.
886
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
889
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
890
diff -Nur -x '*.orig' -x '*~' gbrainy-1.30/src/Makefile.in gbrainy-1.30.new/src/Makefile.in
891
--- gbrainy-1.30/src/Makefile.in 2010-01-03 01:18:17.000000000 +1100
892
+++ gbrainy-1.30.new/src/Makefile.in 2010-02-05 16:19:23.142092906 +1100
1281
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/mkinstalldirs gbrainy-1.40.new/mkinstalldirs
1282
--- gbrainy-1.40/mkinstalldirs 2010-02-27 05:36:54.000000000 +1100
1283
+++ gbrainy-1.40.new/mkinstalldirs 2010-02-02 11:59:15.000000000 +1100
1286
# mkinstalldirs --- make directory hierarchy
1287
-# Author: Noah Friedman <friedman@prep.ai.mit.edu>
1288
-# Created: 1993-05-16
1291
+scriptversion=2009-04-28.21; # UTC
1293
+# Original author: Noah Friedman <friedman@prep.ai.mit.edu>
1294
+# Created: 1993-05-16
1297
+# This file is maintained in Automake, please report
1298
+# bugs to <bug-automake@gnu.org> or send patches to
1299
+# <automake-patches@gnu.org>.
1309
-Usage: mkinstalldirs [-h] [--help] [-m mode] dir ..."
1310
+Usage: mkinstalldirs [-h] [--help] [--version] [-m MODE] DIR ...
1312
+Create each directory DIR (with mode MODE, if specified), including all
1313
+leading file name components.
1315
+Report bugs to <bug-automake@gnu.org>."
1317
# process command line arguments
1318
while test $# -gt 0 ; do
1320
-h | --help | --h*) # -h for help
1321
- echo "$usage" 1>&2
1333
+ echo "$0 $scriptversion"
1336
--) # stop option processing
1343
+# Solaris 8's mkdir -p isn't thread-safe. If you mkdir -p a/b and
1344
+# mkdir -p a/c at the same time, both will detect that a is missing,
1345
+# one will create a, then the other will try to create a and die with
1346
+# a "File exists" error. This is a problem when calling mkinstalldirs
1347
+# from a parallel make. We use --version in the probe to restrict
1348
+# ourselves to GNU mkdir, which is thread-safe.
1351
- if mkdir -p -- . 2>/dev/null; then
1352
+ if mkdir -p --version . >/dev/null 2>&1 && test ! -d ./--version; then
1353
echo "mkdir -p -- $*"
1354
exec mkdir -p -- "$@"
1356
+ # On NextStep and OpenStep, the `mkdir' command does not
1357
+ # recognize any option. It will interpret all options as
1358
+ # directories to create, and then abort because `.' already
1360
+ test -d ./-p && rmdir ./-p
1361
+ test -d ./--version && rmdir ./--version
1365
- if mkdir -m "$dirmode" -p -- . 2>/dev/null; then
1366
+ if mkdir -m "$dirmode" -p --version . >/dev/null 2>&1 &&
1367
+ test ! -d ./--version; then
1368
echo "mkdir -m $dirmode -p -- $*"
1369
exec mkdir -m "$dirmode" -p -- "$@"
1371
+ # Clean up after NextStep and OpenStep mkdir.
1372
+ for d in ./-m ./-p ./--version "./$dirmode";
1374
+ test -d $d && rmdir $d
1382
- set fnord `echo ":$file" | sed -ne 's/^:\//#/;s/^://;s/\// /g;s/^#/\//;p'`
1396
- pathcomp="$pathcomp$d"
1397
+ test "x$d" = x && continue
1399
+ pathcomp=$pathcomp$d
1401
-*) pathcomp=./$pathcomp ;;
1403
@@ -84,21 +131,21 @@
1404
mkdir "$pathcomp" || lasterr=$?
1406
if test ! -d "$pathcomp"; then
1407
- errstatus=$lasterr
1408
+ errstatus=$lasterr
1410
- if test ! -z "$dirmode"; then
1411
+ if test ! -z "$dirmode"; then
1412
echo "chmod $dirmode $pathcomp"
1414
- chmod "$dirmode" "$pathcomp" || lasterr=$?
1416
+ chmod "$dirmode" "$pathcomp" || lasterr=$?
1418
- if test ! -z "$lasterr"; then
1419
- errstatus=$lasterr
1422
+ if test ! -z "$lasterr"; then
1423
+ errstatus=$lasterr
1429
- pathcomp="$pathcomp/"
1430
+ pathcomp=$pathcomp/
1436
# mode: shell-script
1438
+# eval: (add-hook 'write-file-hooks 'time-stamp)
1439
+# time-stamp-start: "scriptversion="
1440
+# time-stamp-format: "%:y-%02m-%02d.%02H"
1441
+# time-stamp-time-zone: "UTC"
1442
+# time-stamp-end: "; # UTC"
1444
-# mkinstalldirs ends here
1445
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/src/Clients/Classical/Makefile.in gbrainy-1.40.new/src/Clients/Classical/Makefile.in
1446
--- gbrainy-1.40/src/Clients/Classical/Makefile.in 2010-02-27 06:27:54.000000000 +1100
1447
+++ gbrainy-1.40.new/src/Clients/Classical/Makefile.in 2010-03-08 11:10:22.621393725 +1100
1449
-# Makefile.in generated by automake 1.11 from Makefile.am.
1450
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
1453
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
1454
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/src/Core/Makefile.in gbrainy-1.40.new/src/Core/Makefile.in
1455
--- gbrainy-1.40/src/Core/Makefile.in 2010-02-27 06:27:55.000000000 +1100
1456
+++ gbrainy-1.40.new/src/Core/Makefile.in 2010-03-08 11:10:22.671393932 +1100
1458
-# Makefile.in generated by automake 1.11 from Makefile.am.
1459
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
1462
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
1463
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/src/Games/Makefile.in gbrainy-1.40.new/src/Games/Makefile.in
1464
--- gbrainy-1.40/src/Games/Makefile.in 2010-02-27 06:27:55.000000000 +1100
1465
+++ gbrainy-1.40.new/src/Games/Makefile.in 2010-03-08 11:10:22.721393514 +1100
1467
-# Makefile.in generated by automake 1.11 from Makefile.am.
1468
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
1471
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
1472
diff -Nur -x '*.orig' -x '*~' gbrainy-1.40/src/Makefile.in gbrainy-1.40.new/src/Makefile.in
1473
--- gbrainy-1.40/src/Makefile.in 2010-02-27 06:27:55.000000000 +1100
1474
+++ gbrainy-1.40.new/src/Makefile.in 2010-03-08 11:10:22.771393375 +1100
894
1476
-# Makefile.in generated by automake 1.11 from Makefile.am.
895
1477
+# Makefile.in generated by automake 1.11.1 from Makefile.am.