Apache OpenOffice (AOO) Bugzilla – Issue 11714
"configure" of SDK is broken
Last modified: 2013-08-07 15:35:14 UTC
[This issue relates to installation of Beta SDK. I don't know where to file it correctly.] The configure script expects "make --version to print out something like; GNU Make version <versnr>. Actually GNU make 3.80 (on Debian) prints out the following text: $ make --version GNU Make 3.80 Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Hence configure fails. I will append a patch which solves the problem.
Created attachment 4829 [details] Patch making configure detect GNU make
Hello Sander, please have a look.
reassigned
Can someone provide me with some info. I assume this is actually the ODK module. THere is a configure script there but there is no configure.in so I cannot reqork from scratch. If you want to resolve this yourself take the version checking straight from config_office 644 tree.
Yes this is the ODK module. I cannot check in the patch myself, because I do not have write access.
I have applied this patch to OOO_STABLE_1 branch. The whole script will have to be restructured. It is not portable will not work in an sh environment. $ cvs commit -m"11714: change the way that gnu make version is sensed" configureChecking in configure; /cvs/api/odk/configure,v <-- configure new revision: 1.4.2.3; previous revision: 1.4.2.2 done Processing log script arguments... Mailing the commit message to cvs@api.openoffice.org (from waratah@openoffice.org)
*** Issue 11923 has been marked as a duplicate of this issue. ***
Downgrading the rewrite to proper autoconf to a later fix.
Accepting issue to shut up issuezilla whinges.
This is one I will not get to.
Reassign issue to owner of selected subcomponent
Another historic issue that was forgotten but fixed in the meantime anyway. configure of sdk is a perl one since 2003-04-17, and at least the current check doesn't make any assumptions on the sting, but rather just matches on <number>.<number>
closing. fixed a couple of years ago..