make distclean fails to remove src/config.cache
55 views
Skip to first unread message
dv1...@wayne.edu
May 19, 2013, 1:12:07 AM5/19/13
to vim...@googlegroups.com
Hi Bj�rn,
Doing 'make distclean' doesn't remove src/config.cache. Shouldn't it?
I went to compare this to the BramVim repo, but found that the BramVim
repo's ./configure script never even creates src/config.cache in the
first place.
If I forget to do the "export CC=clang" bit before ./configuring on Lion
or greater, then realize my error and go back and do it, then do make
distclean to clear the cache, the ./configure script yells at me to do
"make distclean" even though I already did. Sure enough,
src/config.cache is still sitting there. I have to manually remove the
file.
-gmn
Doing 'make distclean' doesn't remove src/config.cache. Shouldn't it?
I went to compare this to the BramVim repo, but found that the BramVim
repo's ./configure script never even creates src/config.cache in the
first place.
If I forget to do the "export CC=clang" bit before ./configuring on Lion
or greater, then realize my error and go back and do it, then do make
distclean to clear the cache, the ./configure script yells at me to do
"make distclean" even though I already did. Sure enough,
src/config.cache is still sitting there. I have to manually remove the
file.
-gmn
Bram Moolenaar
May 19, 2013, 4:08:26 PM5/19/13
to dv1...@wayne.edu, vim...@googlegroups.com
something went wrong.
--
If an elephant is left tied to a parking meter, the parking fee has to be paid
just as it would for a vehicle.
[real standing law in Florida, United States of America]
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
dv1...@wayne.edu
May 19, 2013, 4:16:38 PM5/19/13
to vim...@googlegroups.com
Bram Moolenaar wrote:
>
> > Doing 'make distclean' doesn't remove src/config.cache. Shouldn't it?
> > I went to compare this to the BramVim repo, but found that the BramVim
> > repo's ./configure script never even creates src/config.cache in the
> > first place.
> >
> > If I forget to do the "export CC=clang" bit before ./configuring on Lion
> > or greater, then realize my error and go back and do it, then do make
> > distclean to clear the cache, the ./configure script yells at me to do
> > "make distclean" even though I already did. Sure enough,
> > src/config.cache is still sitting there. I have to manually remove the
> > file.
>
> Vim puts config.cache in src/auto. If you have one in src then
> something went wrong.
That's what I suspected, but MacVim has been doing this for what seems like at least a year.
>
> > Doing 'make distclean' doesn't remove src/config.cache. Shouldn't it?
> > I went to compare this to the BramVim repo, but found that the BramVim
> > repo's ./configure script never even creates src/config.cache in the
> > first place.
> >
> > If I forget to do the "export CC=clang" bit before ./configuring on Lion
> > or greater, then realize my error and go back and do it, then do make
> > distclean to clear the cache, the ./configure script yells at me to do
> > "make distclean" even though I already did. Sure enough,
> > src/config.cache is still sitting there. I have to manually remove the
> > file.
>
> Vim puts config.cache in src/auto. If you have one in src then
> something went wrong.
-gmn
björn
May 24, 2013, 9:39:41 AM5/24/13
to vim...@googlegroups.com
I don't have config.cache in src/. Not sure why you do but as far as I can tell MacVim is not the cause of this. There should not be any reason why it should create this file (at least I never patched the configure script to do so).
Björn
dv1...@wayne.edu
May 27, 2013, 10:46:11 AM5/27/13
to vim...@googlegroups.com
(Bram, you'll probably be interested in this thread still)
Now I know why (a) I have that file in MacVim repo clones, and (b) I
don't have it in BramVim repo clones.
Whenever I configure MacVim or BramVim, I always do "./configure -C
someflags" (note the -C flag). I do this whenever I build pretty much
anything, by reflex, because most of my machines are pretty slow and I
like the speedup that comes from caching boring config tests.
I just checked './configure --help', and both MacVim and BramVim say:
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
Now the difference between MacVim and BramVim: When I use the "-C" flag,
as I always do, BramVim puts "config.cache" in src/auto, whereas MacVim
puts it in "src". The output of "./configure -C" in MacVim says
"configure: creating cache config.cache", whereas the output of that
same command in a BramVim repo says "configure: creating cache
auto/config.cache".
I suspect that Bj�rn sees no such file because he is not using the "-C"
flag with "./configure". Or at least, I *hope* that's why!
In my opinion, whatever scripts in MacVim that control this ought to be
changed so that the result matches BramVim, and config.cache files will
go in src/auto rather than just src. That way, "make distclean" in a
MacVim repo will in fact clean them.
As a side note: although './configure --help' seems to say otherwise,
"--cache-file" is in fact NOT disabled by either MacVim or BramVim,
since I've been doing "-C" which is an alias for
"--cache-file=config.cache", and it *has* been caching (thank God) in
both MacVim and BramVim. (I suspect that "disabled" *really* is
supposed to mean "there will be no caching by default, but there will be
caching if you explicitly ask for it"; the wording of the output,
however, makes it appear that there is no way to get caching).
-gmn
don't have it in BramVim repo clones.
Whenever I configure MacVim or BramVim, I always do "./configure -C
someflags" (note the -C flag). I do this whenever I build pretty much
anything, by reflex, because most of my machines are pretty slow and I
like the speedup that comes from caching boring config tests.
I just checked './configure --help', and both MacVim and BramVim say:
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
Now the difference between MacVim and BramVim: When I use the "-C" flag,
as I always do, BramVim puts "config.cache" in src/auto, whereas MacVim
puts it in "src". The output of "./configure -C" in MacVim says
"configure: creating cache config.cache", whereas the output of that
same command in a BramVim repo says "configure: creating cache
auto/config.cache".
I suspect that Bj�rn sees no such file because he is not using the "-C"
flag with "./configure". Or at least, I *hope* that's why!
In my opinion, whatever scripts in MacVim that control this ought to be
changed so that the result matches BramVim, and config.cache files will
go in src/auto rather than just src. That way, "make distclean" in a
MacVim repo will in fact clean them.
As a side note: although './configure --help' seems to say otherwise,
"--cache-file" is in fact NOT disabled by either MacVim or BramVim,
since I've been doing "-C" which is an alias for
"--cache-file=config.cache", and it *has* been caching (thank God) in
both MacVim and BramVim. (I suspect that "disabled" *really* is
supposed to mean "there will be no caching by default, but there will be
caching if you explicitly ask for it"; the wording of the output,
however, makes it appear that there is no way to get caching).
-gmn
dv1...@wayne.edu
May 27, 2013, 1:10:59 PM5/27/13
to vim...@googlegroups.com
On 05/27/13 at 10:46:11 -0400 gmn wrote:
> In my opinion, whatever scripts in MacVim that control this ought to be
> changed so that the result matches BramVim, and config.cache files will
> go in src/auto rather than just src. That way, "make distclean" in a
> MacVim repo will in fact clean them.
That is to say, *if* it is easy to do so, then the relevant scripts ought to be changed so that blah blah.
> In my opinion, whatever scripts in MacVim that control this ought to be
> changed so that the result matches BramVim, and config.cache files will
> go in src/auto rather than just src. That way, "make distclean" in a
> MacVim repo will in fact clean them.
(Or perhaps 'make distclean' can be patched to also obliterate any existing src/config.cache)
If it isn't an easy thing, just forget it. I can deal with it.
-gmn
dv1...@wayne.edu
May 27, 2013, 1:17:14 PM5/27/13
to vim...@googlegroups.com
Two things, for the record,
1. To prevent any confusion with my other ongoing thread re Tiger PPC, I note that this business about config.cache happens on all archs. I see it on Tiger PPC, Leopard PPC, Lion and Mountain Lion.
2. Also, besides config.cache, the following files are put into "src/auto" in BramVim but in "src" on MacVim: config.log, config.status.
-gmn
1. To prevent any confusion with my other ongoing thread re Tiger PPC, I note that this business about config.cache happens on all archs. I see it on Tiger PPC, Leopard PPC, Lion and Mountain Lion.
2. Also, besides config.cache, the following files are put into "src/auto" in BramVim but in "src" on MacVim: config.log, config.status.
-gmn
dv1...@wayne.edu
Jun 13, 2013, 3:55:48 PM6/13/13
to vim...@googlegroups.com
Although I discovered how to trigger the issue, I don't know what causes
it. I don't know enough about makefiles or confiure scripts to wade
through the difference between those of MacVim and those of BramVim. So
I propose modifying, in MacVim, src/Makefile according the the below
diff.
The line two lines above my added one is doing almost nothing at all,
because the files auto/config.{status,log,cache} are never created by
MacVim as far as I can see:
** If I call './configure -C', they get put in src/, which is what
generated this bug-reporting thread.
** If on the other hand I call plain './configure', then no caches are
created, so there's nothing for that line of the Makefile to destroy.
** If I call './configure --cache-file=src/auto/config.cache (which
'./configure --help tells me is kosher), then no config.cache is put
*anywhere*, and config.{log,status} are put straight into src/ where
the latter won't get wiped out by 'make distclean'.
Therefore I propose leaving that line in place (since it's doing no
harm), but adding one that allows 'make distclean' to destroy
'src/config.{cache,log,status}'. I tested this locally and it seems to
work. Thus 'make distclean' will destroy the things it's supposed to
destroy.
-gmn
--- a/src/Makefile
+++ b/src/Makefile
@@ -2394,6 +2394,7 @@
scrub scratch:
-rm -f auto/config.status auto/config.cache config.log auto/config.log
-rm -f auto/config.h auto/link.log auto/link.sed auto/config.mk
+ -rm -f config.cache config.log config.status
touch auto/config.h
cp config.mk.dist auto/config.mk
björn
Jun 18, 2013, 3:27:17 PM6/18/13
to vim...@googlegroups.com
On Thu, Jun 13, 2013 at 9:55 PM, wrote:
instead of blindly patching. I don't know what causes it though, so I
can't help.
Björn
> On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
>> On 05/27/13 at 10:46:11 -0400 gmn wrote:
>> > In my opinion, whatever scripts in MacVim that control this ought to
>> > be changed so that the result matches BramVim, and config.cache
>> > files will go in src/auto rather than just src. That way, "make
>> > distclean" in a MacVim repo will in fact clean them.
>>
>> That is to say, *if* it is easy to do so, then the relevant scripts
>> ought to be changed so that blah blah.
>>
>> (Or perhaps 'make distclean' can be patched to also obliterate any
>> existing src/config.cache)
>>
>> If it isn't an easy thing, just forget it. I can deal with it.
>
> Hi Björn,
>> On 05/27/13 at 10:46:11 -0400 gmn wrote:
>> > In my opinion, whatever scripts in MacVim that control this ought to
>> > be changed so that the result matches BramVim, and config.cache
>> > files will go in src/auto rather than just src. That way, "make
>> > distclean" in a MacVim repo will in fact clean them.
>>
>> That is to say, *if* it is easy to do so, then the relevant scripts
>> ought to be changed so that blah blah.
>>
>> (Or perhaps 'make distclean' can be patched to also obliterate any
>> existing src/config.cache)
>>
>> If it isn't an easy thing, just forget it. I can deal with it.
>
>
> Although I discovered how to trigger the issue, I don't know what causes
> it. I don't know enough about makefiles or confiure scripts to wade
> through the difference between those of MacVim and those of BramVim. So
> I propose modifying, in MacVim, src/Makefile according the the below
> diff.
>
> The line two lines above my added one is doing almost nothing at all,
> because the files auto/config.{status,log,cache} are never created by
> MacVim as far as I can see:
>
> ** If I call './configure -C', they get put in src/, which is what
> generated this bug-reporting thread.
>
> ** If on the other hand I call plain './configure', then no caches are
> created, so there's nothing for that line of the Makefile to destroy.
>
> ** If I call './configure --cache-file=src/auto/config.cache (which
> './configure --help tells me is kosher), then no config.cache is put
> *anywhere*, and config.{log,status} are put straight into src/ where
> the latter won't get wiped out by 'make distclean'.
>
> Therefore I propose leaving that line in place (since it's doing no
> harm), but adding one that allows 'make distclean' to destroy
> 'src/config.{cache,log,status}'. I tested this locally and it seems to
> work. Thus 'make distclean' will destroy the things it's supposed to
> destroy.
I think it would be better to figure out why there is a difference
> Although I discovered how to trigger the issue, I don't know what causes
> it. I don't know enough about makefiles or confiure scripts to wade
> through the difference between those of MacVim and those of BramVim. So
> I propose modifying, in MacVim, src/Makefile according the the below
> diff.
>
> The line two lines above my added one is doing almost nothing at all,
> because the files auto/config.{status,log,cache} are never created by
> MacVim as far as I can see:
>
> ** If I call './configure -C', they get put in src/, which is what
> generated this bug-reporting thread.
>
> ** If on the other hand I call plain './configure', then no caches are
> created, so there's nothing for that line of the Makefile to destroy.
>
> ** If I call './configure --cache-file=src/auto/config.cache (which
> './configure --help tells me is kosher), then no config.cache is put
> *anywhere*, and config.{log,status} are put straight into src/ where
> the latter won't get wiped out by 'make distclean'.
>
> Therefore I propose leaving that line in place (since it's doing no
> harm), but adding one that allows 'make distclean' to destroy
> 'src/config.{cache,log,status}'. I tested this locally and it seems to
> work. Thus 'make distclean' will destroy the things it's supposed to
> destroy.
instead of blindly patching. I don't know what causes it though, so I
can't help.
Björn
dv1...@wayne.edu
Jun 18, 2013, 5:51:30 PM6/18/13
to vim...@googlegroups.com
On Tue, Jun 18, 2013 at 09:27:17PM +0200, bj�rn wrote:
> I think it would be better to figure out why there is a difference
> instead of blindly patching. I don't know what causes it though, so I
> can't help.
Very well then :)
> I think it would be better to figure out why there is a difference
> instead of blindly patching. I don't know what causes it though, so I
> can't help.
To all: don't use the '-C' flag with './configure', or else you will
ruin 'make distclean' for yourself. It won't destroy your configure
cache.
(Unless you're aware of this and willing to remove the relevant things
manually or patch your local Makefile as I did earlier in this thread).
-gmn
dv1...@wayne.edu
Jun 21, 2013, 1:46:18 AM6/21/13
to vim...@googlegroups.com
On Tue, Jun 18, 2013 at 09:27:17PM +0200, bj�rn wrote:
> On Thu, Jun 13, 2013 at 9:55 PM, wrote:
> > On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
> >> On 05/27/13 at 10:46:11 -0400 gmn wrote:
> >> > In my opinion, whatever scripts in MacVim that control this ought to
> >> > be changed so that the result matches BramVim, and config.cache
> >> > files will go in src/auto rather than just src. That way, "make
> >> > distclean" in a MacVim repo will in fact clean them.
> >>
> >> That is to say, *if* it is easy to do so, then the relevant scripts
> >> ought to be changed so that blah blah.
> >>
> >> (Or perhaps 'make distclean' can be patched to also obliterate any
> >> existing src/config.cache)
> >>
> >> If it isn't an easy thing, just forget it. I can deal with it.
> >
> > Hi Bj�rn,
> > On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
> >> On 05/27/13 at 10:46:11 -0400 gmn wrote:
> >> > In my opinion, whatever scripts in MacVim that control this ought to
> >> > be changed so that the result matches BramVim, and config.cache
> >> > files will go in src/auto rather than just src. That way, "make
> >> > distclean" in a MacVim repo will in fact clean them.
> >>
> >> That is to say, *if* it is easy to do so, then the relevant scripts
> >> ought to be changed so that blah blah.
> >>
> >> (Or perhaps 'make distclean' can be patched to also obliterate any
> >> existing src/config.cache)
> >>
> >> If it isn't an easy thing, just forget it. I can deal with it.
> >
> >
> > Although I discovered how to trigger the issue, I don't know what causes
> > it. I don't know enough about makefiles or confiure scripts to wade
> > through the difference between those of MacVim and those of BramVim. So
> > I propose modifying, in MacVim, src/Makefile according the the below
> > diff.
> >
> > The line two lines above my added one is doing almost nothing at all,
> > because the files auto/config.{status,log,cache} are never created by
> > MacVim as far as I can see:
> >
> > ** If I call './configure -C', they get put in src/, which is what
> > generated this bug-reporting thread.
> >
> > ** If on the other hand I call plain './configure', then no caches are
> > created, so there's nothing for that line of the Makefile to destroy.
> >
> > ** If I call './configure --cache-file=src/auto/config.cache (which
> > './configure --help tells me is kosher), then no config.cache is put
> > *anywhere*, and config.{log,status} are put straight into src/ where
> > the latter won't get wiped out by 'make distclean'.
> >
> > Therefore I propose leaving that line in place (since it's doing no
> > harm), but adding one that allows 'make distclean' to destroy
> > 'src/config.{cache,log,status}'. I tested this locally and it seems to
> > work. Thus 'make distclean' will destroy the things it's supposed to
> > destroy.
>
> I think it would be better to figure out why there is a difference
> instead of blindly patching. I don't know what causes it though, so I
> can't help.
Hi Bj�rn,
> > Although I discovered how to trigger the issue, I don't know what causes
> > it. I don't know enough about makefiles or confiure scripts to wade
> > through the difference between those of MacVim and those of BramVim. So
> > I propose modifying, in MacVim, src/Makefile according the the below
> > diff.
> >
> > The line two lines above my added one is doing almost nothing at all,
> > because the files auto/config.{status,log,cache} are never created by
> > MacVim as far as I can see:
> >
> > ** If I call './configure -C', they get put in src/, which is what
> > generated this bug-reporting thread.
> >
> > ** If on the other hand I call plain './configure', then no caches are
> > created, so there's nothing for that line of the Makefile to destroy.
> >
> > ** If I call './configure --cache-file=src/auto/config.cache (which
> > './configure --help tells me is kosher), then no config.cache is put
> > *anywhere*, and config.{log,status} are put straight into src/ where
> > the latter won't get wiped out by 'make distclean'.
> >
> > Therefore I propose leaving that line in place (since it's doing no
> > harm), but adding one that allows 'make distclean' to destroy
> > 'src/config.{cache,log,status}'. I tested this locally and it seems to
> > work. Thus 'make distclean' will destroy the things it's supposed to
> > destroy.
>
> I think it would be better to figure out why there is a difference
> instead of blindly patching. I don't know what causes it though, so I
> can't help.
I think I've found out why MacVim is putting config.cache (et. al.) in
the "wrong" place (which is itself why 'make distclean' isn't seeking
and destroying those files).
Could it be because MacVim has TWO 'configure' files of substance, while
BramVim only has one?
In MacVim repo:
'configure' is just a tiny wrapper.
'src/configure' is "meaty".
'src/auto/configure' is even meatier (by ~175KB!!).
In BramVim repo:
'configure' is just a tiny wrapper.
'src/configure' is a slightly larger wrapper.
'src/auto/configure' is meaty, about as meaty as 'src/configure' from
MacVim.
If, in MacVim, the meaty config script that's governing cachefile
placement is the one sitting in /src, then that would explain why it's
dropping config.cache right in /src (look at its line 914, see a
relative path).
In BramVim, the only meaty config script is in 'src/auto', so the
corresponding line would dump config.cache in src/auto, right?
Of further interest: BramVim's 'src/configure' appears to be calling
'src/auto/configure' with an explicit request that config.cache be left
in 'src/auto'.
If I am right that this is what's causing MacVim to put the files in a
different place from BramVim, it seems to me that either:
(a) one of MacVim's two meaty configure scripts (or both??) should be
made to drop config.cache (and .log, and .status) in 'src/auto', and to
know that that's where to read cached info from.
Or,
(b) the Makefile's 'make distclean' should be tweaked to find those
files in their current location ('src/'). Of course, this needn't be
done in exactly the way I proposed earlier.
BTW, MacVim's 'src/configure' appears to correspond to BramVim's
'src/auto/configure'. There are many differences, but they seem to be
almost all tiny differences. Also, MacVim's 'src/auto/configure'
appears to be older than 'src/configure'.
-gmn
björn
Jun 21, 2013, 10:02:59 AM6/21/13
to vim...@googlegroups.com
On Fri, Jun 21, 2013 at 7:46 AM, <dv1...@wayne.edu> wrote:
I'm sorry, but the speculation doesn't help. All I can say is that I
have done nothing to change the way the configure script works for
MacVim. There are a few (not many) changes in the configure.in
script, but that's it. If you figure it out, please send me a patch,
otherwise I can not be of much help.
Björn
> On Tue, Jun 18, 2013 at 09:27:17PM +0200, björn wrote:
>> On Thu, Jun 13, 2013 at 9:55 PM, wrote:
>> > On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
>> >> On 05/27/13 at 10:46:11 -0400 gmn wrote:
>> >> > In my opinion, whatever scripts in MacVim that control this ought to
>> >> > be changed so that the result matches BramVim, and config.cache
>> >> > files will go in src/auto rather than just src. That way, "make
>> >> > distclean" in a MacVim repo will in fact clean them.
>> >>
>> >> That is to say, *if* it is easy to do so, then the relevant scripts
>> >> ought to be changed so that blah blah.
>> >>
>> >> (Or perhaps 'make distclean' can be patched to also obliterate any
>> >> existing src/config.cache)
>> >>
>> >> If it isn't an easy thing, just forget it. I can deal with it.
>> >
>> > Hi Björn,
>> On Thu, Jun 13, 2013 at 9:55 PM, wrote:
>> > On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
>> >> On 05/27/13 at 10:46:11 -0400 gmn wrote:
>> >> > In my opinion, whatever scripts in MacVim that control this ought to
>> >> > be changed so that the result matches BramVim, and config.cache
>> >> > files will go in src/auto rather than just src. That way, "make
>> >> > distclean" in a MacVim repo will in fact clean them.
>> >>
>> >> That is to say, *if* it is easy to do so, then the relevant scripts
>> >> ought to be changed so that blah blah.
>> >>
>> >> (Or perhaps 'make distclean' can be patched to also obliterate any
>> >> existing src/config.cache)
>> >>
>> >> If it isn't an easy thing, just forget it. I can deal with it.
>> >
>> >
>> > Although I discovered how to trigger the issue, I don't know what causes
>> > it. I don't know enough about makefiles or confiure scripts to wade
>> > through the difference between those of MacVim and those of BramVim. So
>> > I propose modifying, in MacVim, src/Makefile according the the below
>> > diff.
>> >
>> > The line two lines above my added one is doing almost nothing at all,
>> > because the files auto/config.{status,log,cache} are never created by
>> > MacVim as far as I can see:
>> >
>> > ** If I call './configure -C', they get put in src/, which is what
>> > generated this bug-reporting thread.
>> >
>> > ** If on the other hand I call plain './configure', then no caches are
>> > created, so there's nothing for that line of the Makefile to destroy.
>> >
>> > ** If I call './configure --cache-file=src/auto/config.cache (which
>> > './configure --help tells me is kosher), then no config.cache is put
>> > *anywhere*, and config.{log,status} are put straight into src/ where
>> > the latter won't get wiped out by 'make distclean'.
>> >
>> > Therefore I propose leaving that line in place (since it's doing no
>> > harm), but adding one that allows 'make distclean' to destroy
>> > 'src/config.{cache,log,status}'. I tested this locally and it seems to
>> > work. Thus 'make distclean' will destroy the things it's supposed to
>> > destroy.
>>
>> I think it would be better to figure out why there is a difference
>> instead of blindly patching. I don't know what causes it though, so I
>> can't help.
>
> Hi Björn,
>> > Although I discovered how to trigger the issue, I don't know what causes
>> > it. I don't know enough about makefiles or confiure scripts to wade
>> > through the difference between those of MacVim and those of BramVim. So
>> > I propose modifying, in MacVim, src/Makefile according the the below
>> > diff.
>> >
>> > The line two lines above my added one is doing almost nothing at all,
>> > because the files auto/config.{status,log,cache} are never created by
>> > MacVim as far as I can see:
>> >
>> > ** If I call './configure -C', they get put in src/, which is what
>> > generated this bug-reporting thread.
>> >
>> > ** If on the other hand I call plain './configure', then no caches are
>> > created, so there's nothing for that line of the Makefile to destroy.
>> >
>> > ** If I call './configure --cache-file=src/auto/config.cache (which
>> > './configure --help tells me is kosher), then no config.cache is put
>> > *anywhere*, and config.{log,status} are put straight into src/ where
>> > the latter won't get wiped out by 'make distclean'.
>> >
>> > Therefore I propose leaving that line in place (since it's doing no
>> > harm), but adding one that allows 'make distclean' to destroy
>> > 'src/config.{cache,log,status}'. I tested this locally and it seems to
>> > work. Thus 'make distclean' will destroy the things it's supposed to
>> > destroy.
>>
>> I think it would be better to figure out why there is a difference
>> instead of blindly patching. I don't know what causes it though, so I
>> can't help.
>
have done nothing to change the way the configure script works for
MacVim. There are a few (not many) changes in the configure.in
script, but that's it. If you figure it out, please send me a patch,
otherwise I can not be of much help.
Björn
dv1...@wayne.edu
Jun 21, 2013, 2:03:01 PM6/21/13
to vim...@googlegroups.com
On Fri, Jun 21, 2013 at 04:02:59PM +0200, bj�rn wrote:
> On Fri, Jun 21, 2013 at 7:46 AM, <dv1...@wayne.edu> wrote:
> On Fri, Jun 21, 2013 at 7:46 AM, <dv1...@wayne.edu> wrote:
> > On Tue, Jun 18, 2013 at 09:27:17PM +0200, bj�rn wrote:
> >> On Thu, Jun 13, 2013 at 9:55 PM, wrote:
> >> > On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
> >> >> On 05/27/13 at 10:46:11 -0400 gmn wrote:
> >> >> > In my opinion, whatever scripts in MacVim that control this ought to
> >> >> > be changed so that the result matches BramVim, and config.cache
> >> >> > files will go in src/auto rather than just src. That way, "make
> >> >> > distclean" in a MacVim repo will in fact clean them.
> >> >>
> >> >> That is to say, *if* it is easy to do so, then the relevant scripts
> >> >> ought to be changed so that blah blah.
> >> >>
> >> >> (Or perhaps 'make distclean' can be patched to also obliterate any
> >> >> existing src/config.cache)
> >> >>
> >> >> If it isn't an easy thing, just forget it. I can deal with it.
> >> >
> >> > Hi Bj�rn,
> >> On Thu, Jun 13, 2013 at 9:55 PM, wrote:
> >> > On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
> >> >> On 05/27/13 at 10:46:11 -0400 gmn wrote:
> >> >> > In my opinion, whatever scripts in MacVim that control this ought to
> >> >> > be changed so that the result matches BramVim, and config.cache
> >> >> > files will go in src/auto rather than just src. That way, "make
> >> >> > distclean" in a MacVim repo will in fact clean them.
> >> >>
> >> >> That is to say, *if* it is easy to do so, then the relevant scripts
> >> >> ought to be changed so that blah blah.
> >> >>
> >> >> (Or perhaps 'make distclean' can be patched to also obliterate any
> >> >> existing src/config.cache)
> >> >>
> >> >> If it isn't an easy thing, just forget it. I can deal with it.
> >> >
> >> >
> >> > Although I discovered how to trigger the issue, I don't know what causes
> >> > it. I don't know enough about makefiles or confiure scripts to wade
> >> > through the difference between those of MacVim and those of BramVim. So
> >> > I propose modifying, in MacVim, src/Makefile according the the below
> >> > diff.
> >> >
> >> > The line two lines above my added one is doing almost nothing at all,
> >> > because the files auto/config.{status,log,cache} are never created by
> >> > MacVim as far as I can see:
> >> >
> >> > ** If I call './configure -C', they get put in src/, which is what
> >> > generated this bug-reporting thread.
> >> >
> >> > ** If on the other hand I call plain './configure', then no caches are
> >> > created, so there's nothing for that line of the Makefile to destroy.
> >> >
> >> > ** If I call './configure --cache-file=src/auto/config.cache (which
> >> > './configure --help tells me is kosher), then no config.cache is put
> >> > *anywhere*, and config.{log,status} are put straight into src/ where
> >> > the latter won't get wiped out by 'make distclean'.
> >> >
> >> > Therefore I propose leaving that line in place (since it's doing no
> >> > harm), but adding one that allows 'make distclean' to destroy
> >> > 'src/config.{cache,log,status}'. I tested this locally and it seems to
> >> > work. Thus 'make distclean' will destroy the things it's supposed to
> >> > destroy.
> >>
> >> I think it would be better to figure out why there is a difference
> >> instead of blindly patching. I don't know what causes it though, so I
> >> can't help.
> >
> > Hi Bj�rn,
> >> > Although I discovered how to trigger the issue, I don't know what causes
> >> > it. I don't know enough about makefiles or confiure scripts to wade
> >> > through the difference between those of MacVim and those of BramVim. So
> >> > I propose modifying, in MacVim, src/Makefile according the the below
> >> > diff.
> >> >
> >> > The line two lines above my added one is doing almost nothing at all,
> >> > because the files auto/config.{status,log,cache} are never created by
> >> > MacVim as far as I can see:
> >> >
> >> > ** If I call './configure -C', they get put in src/, which is what
> >> > generated this bug-reporting thread.
> >> >
> >> > ** If on the other hand I call plain './configure', then no caches are
> >> > created, so there's nothing for that line of the Makefile to destroy.
> >> >
> >> > ** If I call './configure --cache-file=src/auto/config.cache (which
> >> > './configure --help tells me is kosher), then no config.cache is put
> >> > *anywhere*, and config.{log,status} are put straight into src/ where
> >> > the latter won't get wiped out by 'make distclean'.
> >> >
> >> > Therefore I propose leaving that line in place (since it's doing no
> >> > harm), but adding one that allows 'make distclean' to destroy
> >> > 'src/config.{cache,log,status}'. I tested this locally and it seems to
> >> > work. Thus 'make distclean' will destroy the things it's supposed to
> >> > destroy.
> >>
> >> I think it would be better to figure out why there is a difference
> >> instead of blindly patching. I don't know what causes it though, so I
> >> can't help.
> >
that I've identified the cause and how to fix it:
MacVim puts config.{cache,log,status} in src, because src/configure is
NOT merely a wrapper (as it is in BramVim), so there is no special
request to src/auto/configure to put the cache in src/auto (as there is
in BramVim). This alone clinches that the *cache* goes in src/.
But in addition, note that src/auto/configure TRIES to put config.log in
explicitly src/auto (line 1496 and three other places), and
config.status *implicitly* in src/auto (via the relative path
./config.status in line 19814). I say "tries", because these are
totally ignored, and in fact it's src/configure that governs the
placement of config.{log,status}. In fact, src/auto/configure's
declarations for where to put *all three* files are ignored, and totally
governed by src/configure.
To help confirm my diagnosis and work on a patch, I ran two further
tests:
ONE: I moved src/configure into src/auto, overwriting the configure
script that was there. I then copied from BramVim the wrapper
src/configure to the same spot in MacVim. Testing revealed that all of
config.{cache,log,status} went into src/auto. MacVim even built without
errors. This proves it's the interplay between src/configure and
src/auto/configure that's causing the issue.
TWO: I went into src/configure and altered line 914 to use a prefix
'auto/', then I made the string 'config.log' take a prefix 'auto/' in
lines 2224, 2234, 13404, and 13996, then gave the string 'config.status'
a prefix of 'auto/' in line 12831. In other words, I told src/configure
to put the files into src/auto. And then that's where it in fact put
them.
I don't know what else you want to know before a patch of some kind is
made.
-gmn
dv1...@wayne.edu
Jun 21, 2013, 2:10:57 PM6/21/13
to vim...@googlegroups.com
On Fri, Jun 21, 2013 at 04:02:59PM +0200, bj�rn wrote:
> On Fri, Jun 21, 2013 at 7:46 AM, <dv1...@wayne.edu> wrote:
> > Could it be because MacVim has TWO 'configure' files of substance, while
> > BramVim only has one?
> >
> > In MacVim repo:
> > 'configure' is just a tiny wrapper.
> > 'src/configure' is "meaty".
> > 'src/auto/configure' is even meatier (by ~175KB!!).
> >
> > In BramVim repo:
> > 'configure' is just a tiny wrapper.
> > 'src/configure' is a slightly larger wrapper.
> > 'src/auto/configure' is meaty, about as meaty as 'src/configure' from
> > MacVim.
> >
> > If, in MacVim, the meaty config script that's governing cachefile
> > placement is the one sitting in /src, then that would explain why it's
> > dropping config.cache right in /src (look at its line 914, see a
> > relative path).
> >
> > In BramVim, the only meaty config script is in 'src/auto', so the
> > corresponding line would dump config.cache in src/auto, right?
This particular message below is not me agitating for a patch, but just
> > Could it be because MacVim has TWO 'configure' files of substance, while
> > BramVim only has one?
> >
> > In MacVim repo:
> > 'configure' is just a tiny wrapper.
> > 'src/configure' is "meaty".
> > 'src/auto/configure' is even meatier (by ~175KB!!).
> >
> > In BramVim repo:
> > 'configure' is just a tiny wrapper.
> > 'src/configure' is a slightly larger wrapper.
> > 'src/auto/configure' is meaty, about as meaty as 'src/configure' from
> > MacVim.
> >
> > If, in MacVim, the meaty config script that's governing cachefile
> > placement is the one sitting in /src, then that would explain why it's
> > dropping config.cache right in /src (look at its line 914, see a
> > relative path).
> >
> > In BramVim, the only meaty config script is in 'src/auto', so the
> > corresponding line would dump config.cache in src/auto, right?
asking a question so I can learn more about how MacVim works.
Why is it that MacVim has two configure scripts of substance,
src/configure and src/auto/configure, whereas in BramVim src/configure
is just a wrapper that calls src/auto/configure?
The git logs tell me that originally MacVim's src/configure WAS just a
wrapper, but that it became "meaty" on Oct 18th 2007, where the commit
message was "Generated configure script"
-gmn
björn
Jun 23, 2013, 10:13:44 AM6/23/13
to vim...@googlegroups.com
On Fri, Jun 21, 2013 at 8:10 PM, <dv1...@wayne.edu> wrote:
OK, I've restored the src/configure script from upstream now. Thanks
for figuring this out and pointing it out to me. I made the mistake
of running "autoconf" instead of "make autoconf" and that is what
caused the problem in the first place.
I don't want to sound ungrateful or discouraging, but unfortunately
your posts are often so long that it makes it hard for me to get the
point and I often don't have the energy to read all the multiple
postings to one thread. In this case, if you had kept it to one post
which simply said "replace src/configure with the one from upstream"
it would have been so much easier for me to fix this. Instead I
misunderstood what you were talking about and hence my very delayed
reaction. My apologies for this.
Anyway, I hope everything works as it should now and thanks once again.
Björn
for figuring this out and pointing it out to me. I made the mistake
of running "autoconf" instead of "make autoconf" and that is what
caused the problem in the first place.
I don't want to sound ungrateful or discouraging, but unfortunately
your posts are often so long that it makes it hard for me to get the
point and I often don't have the energy to read all the multiple
postings to one thread. In this case, if you had kept it to one post
which simply said "replace src/configure with the one from upstream"
it would have been so much easier for me to fix this. Instead I
misunderstood what you were talking about and hence my very delayed
reaction. My apologies for this.
Anyway, I hope everything works as it should now and thanks once again.
Björn
gmn
Jun 23, 2013, 4:56:24 PM6/23/13
to vim...@googlegroups.com
On Sun, Jun 23, 2013 at 04:13:44PM +0200, bj�rn wrote:
> OK, I've restored the src/configure script from upstream now.
Will test forthwith.
> OK, I've restored the src/configure script from upstream now.
BTW, you don't sound ungrateful :)
> In this case, if you had kept it to one post which simply said
> "replace src/configure with the one from upstream" it would have been
> so much easier for me to fix this.
know that that is in fact the correct solution. For all I knew, there
may have been a very good reason for there to be two different, meaty
configure scripts.
Therefore I tried to provide as much info as seemed relevant for
helping you to diagnose the problem. I apologize that it was a flood.
Best,
-gmn
Steven Michalske
Jun 23, 2013, 5:12:07 PM6/23/13
to vim...@googlegroups.com
On Jun 23, 2013, at 1:56 PM, gmn <dv1...@wayne.edu> wrote:
> I would certainly have done so, but not being a programmer, I didn't
> know that that is in fact the correct solution. For all I knew, there
> may have been a very good reason for there to be two different, meaty
> configure scripts.
>
> Therefore I tried to provide as much info as seemed relevant for
> helping you to diagnose the problem. I apologize that it was a flood.
Also, if you get a vague reply and details were spread across a thread it is helpful to send a recap email.
dv1...@wayne.edu
Jun 23, 2013, 6:18:17 PM6/23/13
to vim...@googlegroups.com
On Sun, Jun 23, 2013 at 04:13:44PM +0200, bj�rn wrote:
> OK, I've restored the src/configure script from upstream now.
Tested and works.
Thanks again.
-gmn
Reply all
Reply to author
Forward
0 new messages