Issue 36456 - config_office/configure can't be run
Summary: config_office/configure can't be run
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: configure (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-01 14:14 UTC by rodarvus
Modified: 2006-03-14 21:02 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Update config_office/configure to version 1.74 of config_office/configure.in (25.77 KB, patch)
2004-11-01 14:20 UTC, rodarvus 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description rodarvus 2004-11-01 14:14:12 UTC 
After the merge of cws_src680_rodarvus01, config_office/configure was not 
(manually) regenerated. Thus, running configure returns the following error:

(after a lot of output)
[...]
configure: creating ./config.status
config.status: creating set_soenv
Useless use of a constant in void context at ./set_soenv line 1072.
Possible unintended interpolation of @ENABLE_GTK in string at ./set_soenv line 
1417.
Possible unintended interpolation of @ENABLE_KDE in string at ./set_soenv line 
1421.
Possible unintended interpolation of @KDE_CFLAGS in string at ./set_soenv line 
1422.
Possible unintended interpolation of @KDE_LIBS in string at ./set_soenv line 
1423.
Global symbol "@ENABLE_GTK" requires explicit package name at ./set_soenv line 
1417.
Global symbol "@ENABLE_KDE" requires explicit package name at ./set_soenv line 
1421.
Global symbol "@KDE_CFLAGS" requires explicit package name at ./set_soenv line 
1422.
Global symbol "@KDE_LIBS" requires explicit package name at ./set_soenv line 
1423.
Execution of ./set_soenv aborted due to compilation errors.
Comment 1 rodarvus 2004-11-01 14:18:36 UTC 
This can be fixed simply by running "autoconf" from inside config_office/ 
(preferably a recent version, like 2.59)

I don't think it is advisable to have config_office/configure automatically 
generated from inside a CWS, as this would make multiple CWS merging almost 
impossible, if at least two of them touched config_office/configure.in.

I'll attach a patch to HEAD versions of configure.in and configure (versions 
1.56 and 1.74 respectively)
Comment 2 rodarvus 2004-11-01 14:20:50 UTC 
Created attachment 18804 [details]
Update config_office/configure to version 1.74 of config_office/configure.in
Comment 3 hjs 2004-11-01 14:42:56 UTC 
.
Comment 4 Martin Hollmichel 2005-04-08 13:56:09 UTC 
close issue.