Bug 121150 - autogen.sh: fix removal of autom4te.cache
Summary: autogen.sh: fix removal of autom4te.cache
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-11 03:20 PDT by Alberto Garcia
Modified: 2013-09-11 04:15 PDT (History)
1 user (show)

See Also:


Attachments
Patch (1.04 KB, patch)
2013-09-11 03:24 PDT, Alberto Garcia
cgarcia: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Garcia 2013-09-11 03:20:55 PDT
autom4te.cache doesn't harm other than taking a bit of space in the
hard drive. It can be safely removed anyway.

However at the moment we have

   rm -f $top_srcdir/autom4te.cache

which doesn't work since

  1) autom4te.cache is a directory
  2) $top_srcdir is not defined in autogen.sh

Best case, that's equivalent to rm -f /autom4te.cache, which does
nothing since that file doesn't exist.

Worst case, the user has $top_srcdir set to some value and funny
surprises happen.

Since we can guarantee that we're in the root directory of the WebKit
tree we can just run

  rm -rf autom4te.cache

And this should be run _after_ autoreconf since it's not needed by
anyone else.
Comment 1 Alberto Garcia 2013-09-11 03:24:20 PDT
Created attachment 211293 [details]
Patch
Comment 2 Carlos Garcia Campos 2013-09-11 03:28:49 PDT
Comment on attachment 211293 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=211293&action=review

Thanks!

> ChangeLog:9
> +        Fix incorrect removal of autom4te.cache and put it after the
> +        autoreconf call.

Could you briefly explain here why it was wrong, the explanation in the bug summary is great.
Comment 3 Alberto Garcia 2013-09-11 04:15:01 PDT
Committed r155517: <http://trac.webkit.org/changeset/155517>