View Single Post
Old 03-26-2019, 04:27 PM   #26
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,482
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
How was that TC built? koxtoolchain targets glibc-2.15, so it can't pull newer symbols unless you're doing things wrong .
See my earlier mention of disabling hardening, but even if that fixes it, that doesn't mean that your setup isn't seriously broken .

Speaking of: exceedingly few things should require you to manually enforce CC, CXX, AR, NM, LD & friends. Very few things actually rely on a CROSS_something env var either (OTOH, busybox and OpenSSL would be two exceptions, each expecting a slightly different env var, with a slightly different syntax, IIRC).
What *is* almost ubiquitous, though, is autotool's confusingly named --host argument, which accepts a toolchain triplet, and automatically obeys it to set CC & co.

EDIT: As far as 2019.77 is concerned, my best guess is you're picking up your system includes/glibc because of aforementioned mistakes, and as such it's detecting strlcat/strlcpy as available, while they're definitely not .

Last edited by NiLuJe; 03-26-2019 at 04:45 PM.
NiLuJe is offline   Reply With Quote