Lines Matching refs:configure

49 directory where you ran `configure`.
55 The first time you build PETSc, you must first run `configure` which (among other
65 While many things that `configure` must check are liable to change in between
66 consecutive `configure` invocations, some things are very unlikely -- if ever -- to
67 change. Hence `configure` can safely cache and reuse these values in subsequent
68 `configure` runs, helping to speed up the lengthy process. A similar system is also used
72 While the caching system used by `configure` is very useful, it usually errs on
74 change how a package/program is compiled, `configure` will automatically rebuild this
77 If you would like to enforce that `configure` does not use any cached values, you may
81 $ ./configure --some-args --force
84 Keep in mind however that this will only disable `configure`'s cache, not any other
91 If one still suspects malfeasance due to `configure` caching, or some corruption has
92 occurred due to a faulty `configure` one may use the nuclear option
95 running `configure`. The only thing preserved during this process is the
99 $ ./configure --many-args --with-clean
108 `configure`. `reconfigure` is a short-hand way of repeating your original
109 `configure` invocation with the same arguments. In addition, `reconfigure` will also
110 always explicitly define `PETSC_ARCH` within the `configure` arguments, so there is no
113 For example running the following `configure`:
116 $ ./configure --download-mpich --download-fblaslapack --with-debugging=1
127   import configure
134   configure.petsc_configure(configure_options)
137 In order to rerun this `configure` with the same arguments simply do:
145 ability to additively set new `configure` options, and also to change the values of
146 previous `configure` options! This is particularly useful if one has a lot of
151 if it were the regular `configure`. Suppose one had an installation of PETSc with the following arg…
159   import configure
166   configure.petsc_configure(configure_options)
179 While it is automatically done for you the first time you `configure` and build PETSc,