[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mutilating my own stdlib.h
From: |
Bruce Korb |
Subject: |
Mutilating my own stdlib.h |
Date: |
Fri, 01 Apr 2011 17:24:53 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7 |
Just to be clear: I spelled the macro "LIBPOSIX_EARLY"
instead of "gl_EARLY". Oops. Entirely my fault.
The only additional thing that might have been done
is a sanity check on the substitutions. But, heck.
The header was sufficiently mutilated to convince me
I was in the weeds. I just needed a hint about how
I got there. :) Thank you.
WRT "distclean", I never do that any more.
I clone the repo into a build directory and do all my
fiddling there. Yes, "git" has a command to remove
everything, but I developed my procedures back in
CVS (pre-svn) days, and old habits die hard....
Purging all non-SCM managed sources is very reliable.
Additionally, when it occurs in an isolated project, the developer knows
what were his most recent changes; this is not the case any more for the
average gnulib user when it comes to the recent changes in gnulib.
Since blindly rerunning "make" is unreliable, I find that people should
know that "make distclean; ./configure; make" is more reliable, since that
will save them time.
Yes, too unreliable.
clonetree src dest;cd dest;bootstrap;configure .....
- Mutilating my own stdlib.h,
Bruce Korb <=