Do you include my patch?
https://github.com/apache/incubator-nuttx-apps/pull/79
And does the same config pass the build yesterday?
This patch modify some z80 specifical Make.defs:
commit 342f76a5292d4b5f70cb0184d21225689c3ccec2
Author: Xiang Xiao <xiaoxi...@xiaomi.com>
Date:   Wed Feb 19 19:41:54 2020 +0800

    Makefile: Remove @echo from ARCHIVE

    to avoid shell complain that @echo can't find if the variable
expand in the compound
    command(e.g. ARLOCK) and remove $(Q) before $AR so the result is
almost same as before.
But the change is minor.

Thanks
Xiang

On Fri, Feb 21, 2020 at 1:00 AM Gregory Nutt <spudan...@gmail.com> wrote:
>
> Hi, Xiang, Chao,
>
> I am building for the ez80-based  z20x board now and running into some
> problems.  I am getting warnings like this in every directory under apps:
>
>     make[2]: Entering directory
>     '/cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/mkfatfs'
>     mkfatfs.c
>     configfat.c
>     writefat.c
>     (Module: D:\Spuda\Documents\projects\nuttx\master\apps\libapps.lib)
>     WARNING (610) --> Module
>     
> "mkfatfs.cygdrive.d.Spuda.Documents.projects.nuttx.master.apps.fsutils.mkfatfs.obj"
>     not found.
>     (Module: D:\Spuda\Documents\projects\nuttx\master\apps\libapps.lib)
>     WARNING (610) --> Module
>     
> "configfat.cygdrive.d.Spuda.Documents.projects.nuttx.master.apps.fsutils.mkfatfs.obj"
>     not found.
>     (Module: D:\Spuda\Documents\projects\nuttx\master\apps\libapps.lib)
>     WARNING (610) --> Module
>     
> "writefat.cygdrive.d.Spuda.Documents.projects.nuttx.master.apps.fsutils.mkfatfs.obj"
>     not found.
>     make[2]: Leaving directory
>     '/cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/mkfatfs'
>
> That is a shorter example that illustrates the problem.  At the end of
> the successful compilation, I also get some linker errors that would
> seem to indicate that there is file corruption, but I cannot yet be
> certain of that.
>
> Any thought?  The warnings are annoying if nothing else.
>
> Greg
>
>

Reply via email to