Copyright © https://mongoose-os.com

Mongoose OS Forum

frame
ATTENTION! This forum has moved to:

https://community.mongoose-os.com

Do not post any new messages.

Building in Ubuntu 12

edited December 2015 in Mongoose OS

I was just trying to build a simple device for testing under a Linux VM and getting an error during the build. I'm working through the Building section of the quickstart and the build for the local machine fails.

The build for esp8266 works as from the build guide. But since I don't have a board yet I can't use it.

makearm

The makearm build fails because makearm.sh is missing a ')' on line 5. When that's corrected it fails with:

$ ./makearm.sh
//bin/bash: line 0: cd: /cesanta/platforms/posix: No such file or directory

$ docker run --rm -it -v /home/user/proj/smart.js/cesanta docker.cesanta.com:5000/eabihf-arm-build //bin/bash -c "ls /cesanta"

$

The /cesanta directory is empty and I'm new to docker and don't know enough to know what you're trying to do with it

linux x64

The local build also fails with an error:

$ uname -a
Linux ubuntu 3.13.0-74-generic #118~precise1-Ubuntu SMP Fri Dec 18 10:38:55 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

$ gcc --version
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
[...]

$ pwd
/home/user/proj/smart.js/smartjs/platforms/posix

$ make
CC ../../../v7/v7.c -> build/v7.o
../../../v7/v7.c:2488:9: error: unknown option after ‘#pragma GCC diagnostic’ kind [-Werror=pragmas]
cc1: all warnings being treated as errors
make: *** [build/v7.o] Error 1

I could fix that specific error and let warnings be warnings but I'm betting there some kind of simple version error here.

Comments

  • Hi @rreay,

    We fixed the makearm.sh issue in the latest HEAD

    Those pragmas are only needed to suppress a gcc specific warning. Feel free to remove those lines and ignore the warning yourself.

    I'll try to see if perhaps we don't need that suppression anymore, or any other solution; we aim at build V7 everywhere.

  • Thanks.  I'll check out both next time I get a chance to work with it.
  • dvvdvv Russia
    Hello! I try to build current master for a 512K esp-01 via recommended docker method and it generates 0x00000, 0x01000, 0x11000 and 0xe0000 bins. The latter surely out of addressable space. Where and what to tune? TIA

  • dvvdvv Russia
    Setting FLASH_SIZE=512K leads to
    make: Entering directory `/cesanta/smartjs/platforms/esp8266'
      LD /cesanta/smartjs/platforms/esp8266/build/smartjs.out
    /opt/Espressif/esp-open-sdk/xtensa-lx106-elf/lib/gcc/xtensa-lx106-elf/4.8.2/../../../../xtensa-lx106-elf/bin/ld: /cesanta/smartjs/platforms/esp8266/build/smartjs.out section `.irom0.text' will not fit in region `irom0_0_seg'
    collect2: error: ld returned 1 exit status
    make: *** [/cesanta/smartjs/platforms/esp8266/build/smartjs.out] Error 1

  • adminadmin Dublin, Ireland
    Our firmware size exceeds 512k, so ESP-01 is not supported.
  • dvvdvv Russia
    Any chance to shrink it? I had success with flashing ESP-01 with _release_.
  • dvvdvv Russia
    E.g. if I don't want cloud functionality, how do I comment it out?
  • adminadmin Dublin, Ireland
    Do you mean general networking, or just Cesanta cloud?
  • dvvdvv Russia
    Cesanta
  • SergeySergey Dublin, Ireland
    build with

    make CFLAGS_EXTRA=-DDISABLE_C_CLUBBY


  • dvvdvv Russia
    Ping
    I've a handful of esp-01 and want to give them a try.
    If there's no way to comment out some stuff to fit 512K, please just say No and I'll go searching for alternatives.
    TIA

  • SergeySergey Dublin, Ireland
    Go search for alternatives.
    We do not aim for ESP-01 support.
Sign In or Register to comment.