diff options
Diffstat (limited to 'util/macros/ChangeLog')
| -rw-r--r-- | util/macros/ChangeLog | 154 |
1 files changed, 154 insertions, 0 deletions
diff --git a/util/macros/ChangeLog b/util/macros/ChangeLog index 702386b59..a44619df6 100644 --- a/util/macros/ChangeLog +++ b/util/macros/ChangeLog @@ -1,3 +1,157 @@ +commit d6584a4a52a6fb0eaf979555097bb32621c13cb1 +Author: Alan Coopersmith <alan.coopersmith@sun.com> +Date: Wed Sep 9 13:31:38 2009 -0700 + + Version bump: 1.3.0 + + Signed-off-by: Alan Coopersmith <alan.coopersmith@sun.com> + +commit 79c00a5b5c7866fcc4756993cf4bf4eb2234e9de +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Tue Sep 1 09:45:30 2009 -0400 + + Fix obsolete macro warnings for AC_HELP_STRING #23628 + + When checking for warnings in any module using XORG_RELEASE_VERSION + one or more warnings on AC_HELP_STRING appears. The macro has been + replaced with AS_HELP_STRING + + Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> + Acked-by: Alan Coopersmith <alan.coopersmith@sun.com> + +commit 4c91617d964915005634339afa24b04ec8a2f801 +Author: Peter Hutterer <peter.hutterer@who-t.net> +Date: Tue Sep 1 10:33:37 2009 +1000 + + Add XORG_DEFAULT_OPTIONS meta-macro. + + Many modules use the same set of m4 macros. Additions to the macros require + updating the configure.ac for each module affected. In the case of e.g. + protos and libs this means updating every single module. + + This patch adds a XORG_DEFAULT_OPTIONS meta-macro that uses the other macros + defined. Macros can be added to this meta-macro and modules immediately get + to make use of it - without changes required to configure.ac. + + Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> + +commit 3b7dd69d0bf6bc19f0e4403bb6611de87497aac3 +Author: Pauli Nieminen <suokkos@gmail.com> +Date: Sat Jul 25 15:53:02 2009 +0300 + + Add XORG_STRICT_OPTION macro for strict compilation option + + Strict compilation option can be used to get rid of warnings that often are + showing real hidden bug in code. That just waits to cause problems. + + CWARNFLAGS has to be added to AM_C(PP)FLAGS to use strict compilation mode + in Makefile.am. Automatic addition to compiler flags would cause some configure + checks fail. + + Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> + +commit b0618a909a56d958a6690318545379e105587d82 +Author: Peter Hutterer <peter.hutterer@who-t.net> +Date: Tue Aug 25 09:40:01 2009 +1000 + + Add AM_SILENT_RULES to default XORG_CWARNFLAGS + + Automake 1.11 supports silent builds with the new AM_SILENT_RULES. + http://sources.redhat.com/automake/automake.html#Options + + This loosely qualifies as a CWARNFLAG since it allows all the warnings to be + seen and enables modules to gain support from the feature without any + changes needed to configure. + + Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> + Signed-off-by: James Cloos <cloos@jhcloos.com> + +commit 347e2ae727ac43026776154172ca1ad0360c903c +Author: Alan Coopersmith <alan.coopersmith@sun.com> +Date: Thu Jun 18 11:26:09 2009 -0700 + + Version bump: 1.2.2 + + Signed-off-by: Alan Coopersmith <alan.coopersmith@sun.com> + +commit b885bb59ec23bb338c8df68e40c6ef2c2a9325cc +Author: Jon TURNEY <jon.turney@dronecode.org.uk> +Date: Mon Jun 8 14:17:06 2009 +0100 + + Use correct CWARNFLAGS when cross compiling + + Rather than checking the version of some random gcc which happens to be in + the path to determine which warning flags are supported, we should check the + gcc we are going to use for the build + + For example, when cross-compiling, if the host gcc is >= 3.4 but the + cross-compiler gcc is not, this will cause unsupported warning flags to be + used + + This seems to work, but I don't know enough autofoolery to be sure this is + right... + + Signed-off-by: Alan Coopersmith <alan.coopersmith@sun.com> + +commit 21a957428aa69b03f585378dc6e70ad9f5c513c6 +Author: Dan Nicholson <dbn.lists@gmail.com> +Date: Fri Feb 6 12:28:03 2009 -0800 + + Use m4 for XORG_MACROS_VERSION to error during autoconf + + Check the needed macros version with m4 so that the proper version is + determined during autoconf. This prevents a faulty configure from being + generated. + + Signed-off-by: Dan Nicholson <dbn.lists@gmail.com> + +commit 72d82ed965f9cfbc310897ec17d2dc10bddcef4e +Author: Dan <danstowell+xorg@gmail.com> +Date: Thu Feb 19 06:50:30 2009 -0800 + + Fix incorrect warning message in XORG_MACROS_VERSION + + Signed-off-by: Dan Nicholson <dbn.lists@gmail.com> + +commit b3a43fbe312d4da796aa1fcb04a8a27f7961641d +Author: Dan Nicholson <dbn.lists@gmail.com> +Date: Thu Feb 5 13:30:27 2009 -0800 + + Restore part of the XORG_MACROS_VERSION comment + + The 1.1 or later part is actually important since XORG_MACROS_VERSION + didn't exist before then. + + Signed-off-by: Dan Nicholson <dbn.lists@gmail.com> + +commit f05148fa57a1ebdb75135f026b7c5f4678a3b293 +Author: Dan Nicholson <dbn.lists@gmail.com> +Date: Thu Feb 5 09:17:17 2009 -0800 + + Fix comment in XORG_MACROS_VERSION on usage + + The comment recommending checking XORG_MACROS_VERSION with m4_ifndef was + flawed for two reasons: + + * m4_fatal should be used if the macro is not defined. There's no use + generating configure if the macro doesn't exist. Just fail during + autoconf. + * There's no reason to mention the version needed in the message. That + check does not do version verification. That's what the actual macro + is for. + + Signed-off-by: Dan Nicholson <dbn.lists@gmail.com> + +commit 96585612d17d31fa9dd0f5c260fc33f72be9a75f +Author: Jeremy Huddleston <jeremy@redxiii.local> +Date: Sun Feb 1 21:09:44 2009 -0800 + + XORG_CWARNFLAGS: += is not valid for appending in bourn scripts + + Fixes: + + ./configure: line 12921: CWARNFLAGS+= -Wold-style-definition -Wdeclaration-after-statement: command not found + commit 58803c60b73110a49aecec4202e7820887633bcc Author: Alan Coopersmith <alan.coopersmith@sun.com> Date: Tue Dec 16 15:05:46 2008 -0800 |