sdl: fix autoreconf timing issue
authorMaxime Hadjinlian <maxime.hadjinlian@gmail.com>
Tue, 11 Feb 2014 09:12:35 +0000 (10:12 +0100)
committerPeter Korsgaard <peter@korsgaard.com>
Tue, 11 Feb 2014 09:36:56 +0000 (10:36 +0100)
commit8a66ebabffe4fa965c2530488016512a32cc4d3d
treed4a8c1a842498a95031f34fa2388bfa2923db87e
parentff163385ec2a0bf7ab17f37dbdf8241dff240f31
sdl: fix autoreconf timing issue

Context:
The autobuilders were failing on the symbol _XData32 being in conflicts.
A patch had been added to SDL to add a check to the configure.in

Problem:
Sometimes, the build would fail, because of an _XData32 symbol being in
conflicts eventhrough the patch was here.

What was happening:
Following the classic buildroot workflow:
   - Extract
   - [...]
   - Apply 001 patch, which touches configure.in AND configure
   - Apply 002 patch, which touches configure.in
   - Invoke autogen.sh
   - [...]

Right before running autogen.sh, we have configure.in which is more
recent than configure, which is fine.
We then, execute autogen.sh which, basically, runs autoconf.

If your machine was lighty loaded, the time difference between
configure.in and configure was really tiny (ms order), which seems to be
neglected by autoconf.
The results was that the configure was *NOT* generated. And our second
patch was not taken into account.

If your machine was under heavy load, the time difference between the
two files would have been greater and then *maybe* picked up by
autoconf. And then the configure file was re-generated.

When the 0001 patch was introduced, SDL package did *NOT* run it's
autogen.sh, which is why it touches also the configure.
This came later, causing this behavior.

Fixes:
  http://autobuild.buildroot.net/results/d1c/d1c36f634dbf6b6e5d18444c2a23dfd129202b80/

Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
package/sdl/sdl-0001-use-correct-directfb-config.patch