OK, found it.
My CC has options, as our compiler *needs* a --sysroot argument and we
pass that via CC to ensure that it is always used.
However, su-make-errors.sh does "${CC}" which means the shell tries to
find a binary called 'gcc --sysroot=/foo', which doesn't exist. The
loop has done set -e, so the error is silently absorbed.
The easy fix appears to be to simply remove the quotes around ${CC},
as they serve no purpose apart from breaking builds where CC has
arguments.
Ross
On Tue, 1 Feb 2022 at 14:53, Ross Burton <r...@burtonini.com> wrote:
>
> When I cross-compile s-nail I get a slew of errors:
>
> s-nail-14.9.23/src/mx/accmacvar.c:515:25: error: 'su_ERR_OVERFLOW'
> undeclared (first use in this function); did you mean
> 'su_STATE_ERR_OVERFLOW'?
> s-nail-14.9.23/src/mx/accmacvar.c:522:25: error: 'su_ERR_NOENT'
> undeclared (first use in this function); did you mean 'su_ERR_NONE'?
> s-nail-14.9.23/src/mx/accmacvar.c:2982:31: error: 'su_ERR_INVAL'
> undeclared (first use in this function); did you mean 'su_ERR_NONE'?
> s-nail-14.9.23/src/mx/accmacvar.c:3001:25: error: 'su_ERR_OPNOTSUPP'
> undeclared (first use in this function); did you mean 'EOPNOTSUPP'?
> s-nail-14.9.23/src/mx/accmacvar.c:3688:25: error: 'su_ERR_INVAL'
> undeclared (first use in this function); did you mean 'su_ERR_NONE'?
> s-nail-14.9.23/src/mx/accmacvar.c:3789:28: error: 'su_ERR_NOTSUP'
> undeclared (first use in this function); did you mean 'su_ERR_NONE'?
>
> A native build works, and I see that these are defined in mk-config.h.
> In my cross build, that file looks like this:
>
> #define su__ERR_NUMBER_ENUM_C \
> su_ERR_NONE = 0,\
> su_ERR_NOTOBACCO = su__ERR_NUMBER_MAX,\
> su__ERR_NUMBER = 2
>
> Any ideas why this would be happening?
>
> Thanks,
> Ross
