On 4/22/11 12:07 AM, Daniel Richard G. wrote:
> On Thu, 2011 Apr 21 16:36-0400, Chet Ramey wrote:
>>
>> What is the part of CFLAGS that fixes this, and why not just add it to
>> CFLAGS_FOR_BUILD?  CFLAGS_FOR_BUILD is for the `build tools' part of
>> the builtins library.
> 
> I believe the "+DD64" bit is salient. (Generate 64-bit instead of
> 32-bit code.)
> 
> The problem here is that the makefile is compiling without CFLAGS
> (a.k.a. with CFLAGS_FOR_BUILD), and then linking with CFLAGS. Whether
> it's CFLAGS or CFLAGS_FOR_BUILD isn't the issue; it's that the makefile
> is using one and then the other on the same object.

That's not what actually happens.  CCFLAGS and CCFLAGS_FOR_BUILD share a
common set of options but differ in their use of CPPFLAGS and CFLAGS.  The
link is done with LDFLAGS_FOR_BUILD.  It's hard to tell where the DD64 is
coming from, since it doesn't get added by anything in the bash configure
scripts, but I suspect it gets put into LOCAL_DEFS somehow.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    c...@case.edu    http://cnswww.cns.cwru.edu/~chet/

Reply via email to