Hi Tim,

Try to compile with verbose enabled:

$ make V=1

Probably your board is bringing some older definition that is causing a
variable to be created incorrectly, because "-T/something" doesn't appear a
valid target.

BR,

Alan

On Wednesday, August 17, 2022, TimH <t...@jti.uk.com> wrote:

> Hi All,
>
>
>
> My project has been in hibernation for 6 months for personal reasons but
> today was the day I fired the custom board up again to restart porting
> work.
>
>
>
> My 10.2-based "in progress" work behaves as before (which was a relief) so
> I
> decided I would merge in 10.3 to make sure I restarted with the latest
> release (not withstanding that 10.4 is close!).
>
>
>
> Most issues were easily solved by referring to release notes or good ol'
> Google but I am left with one major and 1 minor problem.
>
>
>
> 1.      Final change that allowed a compile was when I changed the
> defconfig
> to have the new:
>
>
>
> CONFIG_INIT_ENTRYPOINT="nsh_main"
>
> CONFIG_INIT_ENTRYNAME="nsh"
>
>
>
> It all boots and I get the nsh prompt but I get continuous:
>
>
>
> nsh_session: cle failed: 22
>
>
>
> I'm assuming that's EINVAL, but I can't work out why?
>
>
>
> 2.      my board Make.defs file is an edited clone of another from the same
> device (SAMA5D2) and is virtually identical to many other similar files for
> other chips of course. I am running "Ubuntu 20.04.3 TLS"
>
>
>
> This is included in virtually all these files for any chip/arch:
>
>
>
> ifeq ($(CONFIG_CYGWIN_WINTOOL),y)
>
>   ARCHSCRIPT = -T "${shell cygpath -w
> $(BOARD_DIR)$(DELIM)scripts$(DELIM)$(LDSCRIPT)}"
>
> else
>
>   ARCHSCRIPT = -T$(BOARD_DIR)$(DELIM)scripts$(DELIM)$(LDSCRIPT)
>
> endif
>
>
>
> But the compiler complains that there's:
>
>
>
> no rule to make target  '-T/home/{rest of the path}'
>
>
>
> If I remove the -T it is fine.
>
>
>
> Linux/Ubuntu is including the -T in the path I assume? Seems very odd that
> 10.2 was OK with this but not 10.3 - so not a Ubuntu issue I assume? Linux
> skills are definitely lacking, so any suggestions welcomed!
>
>

Reply via email to