Dear Bob,
Many thanks for your response and sorry aobut the delay of mine.
Bob Friesenhahn (2019/08/08 08:05 -0500):
> On Thu, 8 Aug 2019, Sébastien Hinderer wrote:
>
> > Dear all,
> >
> > Are there some conventions about the properties a build system should
> > have regarding certain standard bu
On Mon, 26 Aug 2019, Sébastien Hinderer wrote:
For instance, regarding variables such as CC or CFLAGS, when they are
passed to configure, should they be recorded somewhere so that a future
invocation of make takes them into account?
Yes, they should normally be recorded in the Makefile so that
On 8/26/19, Sébastien Hinderer wrote:
> Similarly, I kind of remember that if, say, make install is invoked with
> a different value of PREFIX that value must be taken into acocunt and
> that it is required that PREFIX can have different values during make
> and make isntall. I am wondering whethe
Hi all,
The autotest testsuite as generated by AT_INIT() (from autoconf 2.69)
puts the full path into the generated file, which can result
in "regen churn" when different checkout paths are used.
E.g., if I've regenerated in a "build" subdir of a checkout with
something like:
mkdir build
On Tue, 27 Aug 2019, Luke Mewburn wrote:
I notice that autoconf generating configure, and automake generating
Makefile.in both store the basename of the source file in the comments.
Currently I'm using the following to simulate this in testsuite.at
after AT_INIT():
m4_cleardivert([HEADER
