Hi Pedro and Simon, I submitted a patch to include xxd in our documentation.
BR, Alan On 2/24/23, Petro Karashchenko <petro.karashche...@gmail.com> wrote: > Hello Simon, > > Maybe adding "apt-get install -y xxd" -- I mean adding xxd separately > instead of vim-common and let package manager to resolve dependencies is a > better approach? > > Best regards, > Petro > > пт, 24 лют. 2023 р. о 10:46 Simon Filgis <si...@ingenieurbuero-filgis.de> > пише: > >> Hi Alan, >> >> many thanks: >> >> xxd -i romfs.img | sed -e "s/^unsigned char/const unsigned char >> aligned_data(4)/g" >> etctmp.c >> /bin/sh: 1: xxd: not found >> rm romfs.img >> >> >> xxd is part of vim-common. Now it works. >> >> Should we add vim-common to the list of dependencies, or is this a corner >> case? >> >> Simon >> >> -- >> Hard- and Softwaredevelopment Consultant >> Ingenieurbüro-Filgis >> USt-IdNr.: DE305343278 >> >> >> On Thu, Feb 23, 2023 at 10:22 PM Alan C. Assis <acas...@gmail.com> wrote: >> >> > Hi Simon, >> > >> > Please try to compile with verbose enabled: >> > >> > make V=1 >> > >> > It could disclose more information about the issue. >> > >> > BR, >> > >> > Alan >> > >> > On 2/23/23, Simon Filgis <si...@ingenieurbuero-filgis.de> wrote: >> > > Hi Alan, >> > > >> > > my custom board. It compiles well on my computer. Romfs fails only >> > > the >> > > bitbucket pipe docker. How can I check if the generation was >> successful? >> > In >> > > the log, it looks fine, doesn't it? >> > > >> > > Simon >> > > >> > > >> > > -- >> > > Hard- and Softwaredevelopment Consultant >> > > Ingenieurbüro-Filgis >> > > USt-IdNr.: DE305343278 >> > > >> > > >> > > On Thu, Feb 23, 2023 at 3:27 PM Alan C. Assis <acas...@gmail.com> >> wrote: >> > > >> > >> Hi Simon, >> > >> >> > >> What board and board profile are you using? >> > >> >> > >> This error normally happens when genromfs didn't generated the romfs >> > >> image. >> > >> >> > >> BR, >> > >> >> > >> Alan >> > >> >> > >> On 2/23/23, Simon Filgis <si...@ingenieurbuero-filgis.de> wrote: >> > >> > Dear all, >> > >> > >> > >> > I'm setting up a build-pipeline in bitbucket. It fails with: >> > >> > arm-none-eabi-ld: >> > >> > >> > >> >> > >> /opt/atlassian/pipelines/agent/build/nuttx/staging/libapps.a(nsh_romfsetc.c.opt.atlassian.pipelines.agent.build.apps.nshlib.o): >> > >> > in function `nsh_romfsetc': >> > >> > 3126 >> > >> > /opt/atlassian/pipelines/agent/build/apps/nshlib/nsh_romfsetc.c:97: >> > >> > undefined reference to `romfs_img_len' >> > >> > 3127 >> > >> > arm-none-eabi-ld: >> > >> > /opt/atlassian/pipelines/agent/build/apps/nshlib/nsh_romfsetc.c:97: >> > >> > undefined reference to `romfs_img' >> > >> > 3128 >> > >> > make[1]: *** [Makefile:159: nuttx] Error 1 >> > >> > >> > >> > Has anybody a hint or idea howto overcome this? >> > >> > >> > >> > Simon >> > >> > >> > >> > -- >> > >> > Hard- and Softwaredevelopment Consultant >> > >> > Ingenieurbüro-Filgis >> > >> > USt-IdNr.: DE305343278 >> > >> > >> > >> >> > > >> > >> >
