http://bugs.winehq.org/show_bug.cgi?id=18322
Summary: Cannot recreate "configure" script Product: Wine Version: 20050930 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: build-env AssignedTo: wine-bugs@winehq.org ReportedBy: contact@philipashmore.com
I'm trying to create a paired-down version of Wine that contains only the registry and COM framework (no GUI) from Wine. I'm calling this project "v3c-com" for want of a better name, and it's purpose is to act as a development framework/runtime for COM development under GNU/Linux, ideally with DCOM interoperability with Windows.
As a first step I modified the configure.ac script: 1. package name change 2. remove configure arguments 3. remove programs and dll targets 4. Recreate "configure" - but how?
I tried just deleting the "configure" script and running tools/wineinstall...
$ tools/wineinstall Wine Installer v1.0
Running configure...
configure: error: cannot find sources (server/atom.c) in . or ..
Configure failed, aborting install.
I've indented the output for readability. Let me repeat - I deleted "configure" so what's tools/wineinstall running???
I also tried running automake, but it's giving bizarre messages - probably because aclocal.m4 isn't generated by autoconf, but it's just a guess.
http://bugs.winehq.org/show_bug.cgi?id=18322
Philip Ashmore contact@philipashmore.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|20050930 |1.1.20
--- Comment #1 from Philip Ashmore contact@philipashmore.com 2009-05-01 21:16:58 --- Changed version this bug applies to - the latest version isn't the bottom version.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Component|build-env |-unknown Resolution| |INVALID
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-01 23:36:38 --- There is no a bug in Wine. If you are changing the configure.ac an that breaks things - go and learn how to do that, don't blame Wine and report a bug here.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-01 23:36:56 --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=18322
Philip Ashmore contact@philipashmore.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |contact@philipashmore.com Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #4 from Philip Ashmore contact@philipashmore.com 2009-05-02 04:48:27 --- Thanks for your quick reply.
I can see that I haven't succeeded in making the problem abundantly clear so let's try again.
1. I want to build a package based on Wine 2. I need to modify configure.ac 3. I need the existing Wine source distribution to be able to recreate the "configure" script from a changed configure.ac
I'm stuck at (3) above because it requires that the existing Wine source distribution is able to at least recreate the configure script from an _unmodified_ configure.ac
I'm running Debian Lenny amd64. To test this yourself, go through the following steps.
Obtain the source bzipped tar ball "wine-1.1.20.tar.bz2" into a directory writeable by you as a normal user and run the following bash script
mkdir tmp # You need these otherwise (like me) wineinstall will look cd tmp # for "configure" in the _parent_ directory of wine-1.1.20 tar -xjf ../wine-1.1.20.tar.bz2 cd wine-1.1.20 rm configure # We're testing that wineinstall will re-generate this tools/wineinstall
Like me, you should get
Wine Installer v1.0
You're running this from the wrong directory. Change to the Wine source's main directory and try again.
It looks like wineinstall doesn't even try to regenerate configure.
As for reading the documentation, which version? I got "Autoconf, Automake and Libtool" from http://sources.redhat.com/autobook/autobook-1.5.tar.gz In chapter 8 of this book there is a section called "bootstrapping" that indicates that how you get to the point of running configure is a matter of taste - the options offered were "autogen.sh", "bootstrap2, "autoreconf" and "AM_MAINTAINER_MODE", non of which are available in the Wine source distribution.
I also noticed that "aclocal.m4" is hand-written, not generated from configure.ac by aclocal, and this would lead me to the conclusion that Wine is a non-standard Autotools project and therefore might have a non-standard means of re-generating "configure".
Sure, I can "try" running autoconf and see if that works, but gee I thought it might be nice if you could please tell me how you did it, so I can do it the same way!
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|contact@philipashmore.com | Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 05:28:05 --- All this is hardly a Wine bug. Wine has no any problem with generating configure from configure.ac.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 05:28:40 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18322
Philip Ashmore contact@philipashmore.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #7 from Philip Ashmore contact@philipashmore.com 2009-05-02 05:53:39 --- For the love of Pete!
I just went to great detail in showing you that wineinstall doesn't try to generate configure from configure.ac.
You need to tell me (I promise I won't tell anyone else) the _exact_ procedure that I need to follow to recreate configure.
There's no point telling me that "Wine has no any problem with generating configure from configure.ac" when you don't tell me what commands to use to generate it.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 06:00:31 --- (In reply to comment #7)
I just went to great detail in showing you that wineinstall doesn't try to generate configure from configure.ac.
Why shoud it do that?
You need to tell me (I promise I won't tell anyone else) the _exact_ procedure that I need to follow to recreate configure.
man autoconf?
There's no point telling me that "Wine has no any problem with generating configure from configure.ac" when you don't tell me what commands to use to generate it.
This is not a user support forum.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 06:01:10 --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=18322
Philip Ashmore contact@philipashmore.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #10 from Philip Ashmore contact@philipashmore.com 2009-05-02 06:41:13 --- So my guess that it was autoconf was correct! Geez that was a tough one! When running autoconf, do I need to supply any flags? I checked out "man autoconf" like you suggested and there are loads of them (flags, that is).
By continuing to ask the same question without getting a precise answer, I have to ask myself - with regards to Wine:
Is there a written offer for source that's incomplete in some way?
I would have to answer "yes". You could help me answer "no" in one of two ways.
1. Paste the command line you use into a script called "bootstrap" 2. Documenting the bootstrap procedure and include it with the source code
If you insist on pussy-footing around than you (not me) are making a case for a GPL and therefore LPGL violation.
See http://www.gnu.org/licenses/gpl-violation.html
for details.
By the way, simple omissions inability to communicate effectively and thoughtlessness aren't valid exceptions.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #11 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 07:41:38 --- Again, this is your problem, not a Wine bug of any kind. And once again, this is not a place for user support, look for it somewhere else.
http://bugs.winehq.org/show_bug.cgi?id=18322
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 07:41:56 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18322
--- Comment #13 from Austin English austinenglish@gmail.com 2009-05-02 13:48:16 --- (In reply to comment #10)
- Documenting the bootstrap procedure and include it with the source code
$ rm configure && autoconf && ./configure
works fine here.
tools/wineinstall does not generate configure, since configure is kept in tree, e.g., AJ runs autoconf whenever configure.ac changes.
If you're changing the wine source in some way, you can add that change to wineinstall, nothing's stopping you...