Bug 8508 - VENDOR_RELEASE expands as glob pattern
Summary: VENDOR_RELEASE expands as glob pattern
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86 (IA32) NetBSD
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-04 17:51 UTC by Jeremy C. Reed
Modified: 2018-06-12 18:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jeremy C. Reed 2006-10-04 17:51:33 UTC
I noticed in April and someone else also told me the same that VENDOR_RELEASE
expanded the multiplication asterisks as globbing wildcards.

This kills my build. I reported this in April
http://lists.freedesktop.org/archives/xorg/2006-April/014873.html
but no reply.

Okay to just set it at cofnigure time?

diff --git a/configure.ac b/configure.ac
index 76f5e04..08e66e8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -790,7 +790,7 @@ if test "x$USE_RGB_BUILTIN" = xyes; then
 	AC_DEFINE(USE_RGB_BUILTIN, 1, [Use built-in RGB color database])
 fi
 
-VENDOR_RELEASE="((($VERSION_MAJOR) * 10000000) + (($VERSION_MINOR) * 100000) +
(($VERSION_PATCH) * 1000) + $VERSION_SNAP)"
+VENDOR_RELEASE=`expr \( $VERSION_MAJOR \* 10000000 \) + \( $VERSION_MINOR \*
100000 \) + \( $VERSION_PATCH \* 1000 \) + $VERSION_SNAP`
 
 if test $VERSION_SNAP = "0"; then
 	if test $VERSION_PATCH = "0"; then
Comment 1 Daniel Stone 2007-02-27 01:33:53 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 Adam Jackson 2007-05-17 19:06:46 UTC
Yeah, if this is still an issue for you, go ahead and fix it.
Comment 3 Adam Jackson 2018-06-12 18:43:39 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.