Bug 127312 – Webkit GTK 2.2.3 release generates another configure file

• Component: WebKitGTK
• Status: RESOLVED CONFIGURATION CHANGED

[Niranjan Rao]

I am not certain if this is a bug, but it does creates some problems for those who try to use released version.

We download the tar ball of Webkit GTK 2.2.3 release and add it to our git repository.When attempting to build from this tar ball, we have observed than first run configure command generates/overwrites the configure script again. It appears that new configure command might have some machine specific information which defeats the purpose of first configure command. Example parameters used for --prefix command.

As git shows files as modified, team member commit this file which may not be usable on other machine as others may want to use different locations for building. But in the process, original configure command that came with package is lost.


Its not our intention to modify webkit source code, but to make sure we have all the source pieces available to us to build on different machines. Especially important since many dependencies for 2.2.3 are not part of standard distribution on platforms such as Ubuntu 12.04

Our current workaround for this problem is copy sources to some other directory and build from new directory.

[Zan Dobersek]

Do you perhaps have a diff of what changes are made to the configure file?

[Carlos Garcia Campos]

How do you build from the tarball?

[Niranjan Rao]

Created attachment 221925 [details]
Diff file for the configure file getting overwritten.

Diff file for the configure file getting overwritten.

[Niranjan Rao]

I usually build it with following configure parameters

./configure --enable-gtk-doc=no --enable-gtk-doc-html=no  --enable-gtk-doc-pdf=no  --enable-webkit1=no --enable-credential-storage=no --enable-debug-symbols=full

After the run is over, files are same at this point. But when you start building, first thing make does is (re)configure. At this point file is overwritten.

[Zan Dobersek]

This seems to occur because you're using autoconf 2.68 while the configure script was generated with autoconf 2.69. I'm not certain this is necessarily a bad thing (i.e. a valid bug).

If you're not able to upgrade to autoconf 2.69, you should probably work around this by forcing a mock configuration of the source tree before adding it to the git repository.

[Martin Robinson]

Closing this since WebKitGTK no longer uses autotools.