[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: TARGET_ARCH
From: |
Oleksandr Gavenko |
Subject: |
Re: TARGET_ARCH |
Date: |
Fri, 28 May 2010 15:27:05 +0300 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 |
On 2010.05.27 18:09, address@hidden wrote:
What is TARGET_ARCH typically expected to be set to for cross building with the
implicit gmake rules?
The C implicit rule is:
COMPILE.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c
But most hits I see talk about defining TARGET_ARCH to be "arm" or similar. Of course,
doing that makes gcc say "gcc: arm: No such file or directory".
The info pages have nothing to say.
The only reference I saw in the mailing list archives was from 2005, and it
advised just not using implicit rules.
$ info make | grep TARGET_ARCH || echo nothing found
print nothing found. This is not GNU Make issue.
Under "The GNU Project Build Tools" doc you can find:
`target'
The canonical configuration name of the target.
`target_cpu'
`target_vendor'
`target_os'
The first three parts of the canonical target configuration name.
usually this vars joined into triplet:
target=$(target_cpu)-$(target_vendor)-$(target_os)
this like you target_arch.
And these vars used in conditions, not command line switches.
--
С уважением, Александр Гавенко.
- TARGET_ARCH, 3r6evx86te, 2010/05/27
- Re: TARGET_ARCH,
Oleksandr Gavenko <=