Makeinstall.mk provides information on how nmake was built and installed user makefiles should use the CC.* probe variables for build time architecture specifics the CC.* variables will always be consistent with the current $(CC)
On Mon, 16 Jan 2012 18:06:20 -0500 Bruce Lilly wrote: > I note that > http://www2.research.att.com/~gsf/download/optast.html > states that some probe-generated files will be moved to a point > under /var for FHS compliance in some future release of AST. However, > I wonder if there is not a similar issue with nmake. While looking at > files under $INSTALLROOT, I see that > ${INSTALLROOT}/lib/make/Makeinstall.mk contains: > _architecture_ = amd64 i386-64 > _machine_ = amd64 i386-64 > The first machine that I installed the linux.i386-64 binary version on > in fact has an AMD processor, however all other 64-bit machines here > are Intel-based (package emits linux.i386-64 for all). > ${INSTALLROOT}/lib/make also contains a compiled makerules.mo (which > also has some "amd" strings in it). > Could these shared files cause problems when using nmake to generate > code on Intel-based linux.i386-64 machines? > Wouldn't it be prudent to put the compiled .mo file(s) under /var? > The top line of ${INSTALLROOT}/lib/make/Makeinstall.mk says: > /* : : generated from cc assertions : : */ > which leads be to believe that that file also would be best placed > under /var (in case different machines with the same package-generated > architecture string use different compilers). In that case, the issue > probably isn't 64-bit-specific. _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
