https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
Mark Millard changed:
What|Removed |Added
Severity|Affects Some People |Affects Only Me
--- Comment #11 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #10 from Heinz N. Gies ---
I see I totally missunderstood your ticket then, but you're right it'd make
sense if the toolchain itself would do that!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #9 from Mark Millard ---
(In reply to Heinz N. Gies from comment #8)
buildworld creates the files below in the
build directory tree involved:
./contrib/libstdc++/include/tr1/stdint.h
./contrib/llvm/tools/clang/lib/Headers/stdi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #8 from Heinz N. Gies ---
Hmm interesting,
I must have done something wrong. To double check, I ran build world again and
then re-build the kernel after removing the stdint.h I copied, it build
cleaninly
root@mystery-box:/usr/s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #7 from Heinz N. Gies ---
Oh yes I wasn't cross compiling I was compiling a kernel on the host with
slightly modified config (RCTL/VNET) so the stdint.h should be the same I
guess.
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #6 from Mark Millard ---
(In reply to Heinz N. Gies from comment #5)
If the build-host system type is the same as
the build-target system type and stdint.h
has not actually changed then
/usr/lib/include/stdint.h
content may w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #5 from Heinz N. Gies ---
I admit I've no idea what I'm doing ;), I'm just trying to bang my head around
getting it to work. But what you say makes sense. I'm just happy it worked!
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #4 from Mark Millard ---
(In reply to Heinz N. Gies from comment #3)
I do not expect that the working "buildworld"
puts a stdint.h in /usr/lib/clang/5.0.0/include/
so I do not expect that that is the right place.
I do expect t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #3 from Heinz N. Gies ---
This is most likely not a good solution but I could get the kernel to compile
with this:
cp /usr/lib/include/stdint.h /usr/lib/clang/5.0.0/include/
it seems the /usr/lib/clang/5.0.0/include/ dir is w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
--- Comment #2 from Heinz N. Gies ---
I think Mark is right, it's a toolchain issue. Some googling later it looks
like the issue is also present on non BSD systems that use NEON:
- http://discuss.redbear.cc/t/solved-stdint-h-not-found-duri
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
Mark Millard changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
Heinz N. Gies changed:
What|Removed |Added
CC||he...@project-fifo.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
Bug ID: 220125
Summary: head -r320059 (e.g.) arm64: buildkernel after
kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c
compile fails with
.../lib/clang/4.0.
13 matches
Mail list logo