On 2017-Jun-18, at 11:57 PM, Dimitry Andric <dim at FreeBSD.org> wrote:

> On 19 Jun 2017, at 08:46, Mark Millard <markmi at dsl-only.net> wrote:
>> This is a variant of the wording in bugzilla 220125:
>> Unless buildworld (not just kernel-toolchain) is used before
>> buildkernel the result for arm64 is:
>> --- armv8_crypto_wrap.o ---
>> In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46:
>> /usr/obj/cortexA53dbg_clang/arm64.aarch64/usr/src/tmp/usr/bin/../lib/clang/4.0.0/include/arm_neon.h:31:10:
>> fatal error: 'stdint.h' file not found
> ...
>> A) kernel-toolchain needs to establish a stdint.h
>>  that would be found
>> vs.
>> B) arm_neon.h needs to avoid needing stdint.h
>>  (presumes armv8_crypto_wrap.c is correct to
>>   include arm_neon.h )

(B) variant: Possibly finding a distinct stdint.h
when there is no $(WORLDTMP} tied one to be found?
(Avoiding needing the specific stdint.h that is
used when buildworld is used first.) Look in some
new place as a last resort (extended search path

>> at least if the kernel-toolchain then buildkernel
>> sequence is to be supported for arm64.
> Solution A is problematic because it then would require to install
> headers into ${WORLDTMP}.  This is what buildworld does.

Is there anyplace outside of $(WORLDTMP} where an alternate
stdint.h could be made to be found if the ${WORLDTMP} places
do not have one to find? (The include notation is currently
<stdint.h> .)

Might some place related to (using my example full path
just for illustration, showing post-subsitutions):


be allowed have its own "failover" stdint.h to find as a
last resort?

(I do not claim this is well thought out.)

> Solution B is problematic because arm_neon.h uses stdint.h types
> extensively.

The instance of the file name need not be from the usual
place when there is no $(WORLDTMP} tied stdint.h to find?
So a different stdint.h instead of no stdint.h ?

> Maybe the solution with the least amount of work is to provide a
> kernel-specific wrapper header with the stdint.h types.

With also avoiding the #include <stdint.h> that would
otherwise fail?

> Otherwise, just use buildworld before buildkernel.

For now buildworld first is what I'd do for arm64.

Mark Millard
markmi at dsl-only.net

freebsd-toolchain@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

Reply via email to