Hi,
On 2015/08/28 16:03, Nick Hudson wrote:
On 08/24/15 10:50, Kengo NAKAHARA wrote:
Hi,
On 2015/08/24 18:24, Nick Hudson wrote:
On 08/24/15 09:36, Kengo NAKAHARA wrote:
Hi,
On 2015/08/24 16:18, Nick Hudson wrote:
+__weak_alias(interrupt_construct_intrids, eopnotsupp);
I found this by
On 08/24/15 10:50, Kengo NAKAHARA wrote:
Hi,
On 2015/08/24 18:24, Nick Hudson wrote:
On 08/24/15 09:36, Kengo NAKAHARA wrote:
Hi,
On 2015/08/24 16:18, Nick Hudson wrote:
+__weak_alias(interrupt_construct_intrids, eopnotsupp);
I found this by running sysctl -A on an evbarm platform
Sorry,
I will probably allow $S/.. only for `object' paths. To realize
suffix rules, I have to dig subdirectories under kernel build
directory. But that is only for files that are compiled. I don't
need to dig subdirectories for objects whose relative path is
`../../../a/b/c'.
On Fri, Aug 28, 2015 at 08:31:28AM +, Masao Uebayashi wrote:
Module Name: src
Committed By: uebayasi
Date: Fri Aug 28 08:31:28 UTC 2015
Modified Files:
src/usr.bin/config: mkmakefile.c
Log Message:
Accept only relative paths (from $S) for `file' and `object'.
And there is $S/../common. Need more thought..
Such a hack is needed because config(1) has to generate rules
explicitly for each *.[cS]. If you try to override a rule (e.g.
compile this pmap_bootstrap.c with ${NOPROF_C}), it will be a
duplicated rule.
If *.[cS] - *.o will be written using suffix rules, you can safely
override rules. No
