element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Moto Mods
  • Products
  • Manufacturers
  • Moto Mods
  • More
  • Cancel
Moto Mods
Forum Help with the developer problem(Developer Tools: Build from Source)
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Moto Mods to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 57 subscribers
  • Views 527 views
  • Users 0 members are here
  • developer tools: build from source
Related

Help with the developer problem(Developer Tools: Build from Source)

erisonkwok
erisonkwok over 8 years ago

Hey guys.

My Ubuntu(ubuntu-14.04.5-desktop-amd64) systerm run within a virtual machine.

I am doing what https://developer.motorola.com/build/tools/setup-environment tell me to do.Here seems nothing wrong.

 

Next step https://developer.motorola.com/build/tools/build-from-source ,there is one error.

$ export PATH=$PATH:$BUILD_TOP/manifesto:$BUILD_TOP/bootrom-tools                (this step run correctly)
$ cd $BUILD_TOP/nuttx/nuttx                                                      (this step run correctly)
$ make distclean                                                                 (this step run correctly)
$ cd $BUILD_TOP/nuttx/nuttx/tools                                                (this step run correctly)
$ ./configure.sh hdk/muc/base_unpowered                                          (this step run correctly)

$ cd $BUILD_TOP/nuttx/nuttx                                                      (this step run correctly)
$ make                                                                           (this step goes wrong)

The results are as follows,

Missing path to the output file

USAGE: tools/version.sh [-d|-h] [-b <build>] -v <major.minor> <outfile-path>

Try 'tools/version.sh -h' for more information

chmod: cannot access ‘.version’: No such file or directory

make: *** [/home/xcjapp/Build_Environment/nuttx/nuttx/.version] Error 1

 

So,how can I fix it?

Thank you very much.

  • Sign in to reply
  • Cancel

Top Replies

  • leo.andrade
    leo.andrade over 8 years ago +1 suggested
    Hi Erison. I am also using a VM and I did not face this issue. By checking the logs, in my case, the version.sh is being called with the following parameters: tools/version.sh -v 0.1 -b bdf298a .version…
  • leo.andrade
    leo.andrade over 8 years ago in reply to erisonkwok +1 suggested
    Erison, Strange! The nuttx directory should be retrieved from a git repository created by the command " git clone https://github.com/MotorolaMobilityLLC/nuttx " that you had executed during the "Download…
  • erisonkwok
    erisonkwok over 8 years ago in reply to leo.andrade +1
    Hi Leo, Thank you very much. The error is gone. Doing what you suggest,step by step,everything goes well,and did not face that issue again.Maybe the last time I clone the nuttx folder missing some documents…
Parents
  • leo.andrade
    0 leo.andrade over 8 years ago

    Hi Erison.

     

    I am also using a VM and I did not face this issue.

    By checking the logs, in my case, the version.sh is being called with the following parameters:

    tools/version.sh -v 0.1 -b bdf298a .version

     

    However, I noticed that If I remove the parameter for the -b, I have the same error than you:

    $ tools/version.sh -v 0.1 -b .version
    Missing path to the output file
    USAGE: tools/version.sh [-d|-h] [-b <build>] -v <major.minor> <outfile-path>
    Try 'tools/version.sh -h' for more information

     

    So, it seems that the build parameter is missing when it is called by the make because the OVERRIDE_BUILD_NUM (in Makefile.unix) is empty.

     

    Can you check what the "git describe --always --dirty --match nothing" command in $BUILD_TOP/nuttx/nuttx folder is returning for you? It should be an hexa value.

     

    Thanks

     

    Leo

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • leo.andrade
    0 leo.andrade over 8 years ago

    Hi Erison.

     

    I am also using a VM and I did not face this issue.

    By checking the logs, in my case, the version.sh is being called with the following parameters:

    tools/version.sh -v 0.1 -b bdf298a .version

     

    However, I noticed that If I remove the parameter for the -b, I have the same error than you:

    $ tools/version.sh -v 0.1 -b .version
    Missing path to the output file
    USAGE: tools/version.sh [-d|-h] [-b <build>] -v <major.minor> <outfile-path>
    Try 'tools/version.sh -h' for more information

     

    So, it seems that the build parameter is missing when it is called by the make because the OVERRIDE_BUILD_NUM (in Makefile.unix) is empty.

     

    Can you check what the "git describe --always --dirty --match nothing" command in $BUILD_TOP/nuttx/nuttx folder is returning for you? It should be an hexa value.

     

    Thanks

     

    Leo

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
  • erisonkwok
    0 erisonkwok over 8 years ago in reply to leo.andrade

    Hi Leo.

     

    First of the all,thanks for your time.

     

    Check the command what you tell me,it seems return somthing different.The result are as follow,

     

    xcjapp@xcj-virtual-machine:~/Build_Environment/nuttx/nuttx$ git describe --always --dirty --match nothing

    fatal: Not a git repository (or any of the parent directories): .git

     

    Thanks again!

     

    Erison.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • leo.andrade
    0 leo.andrade over 8 years ago in reply to erisonkwok

    Erison,

     

    Strange! The nuttx directory should be retrieved from a git repository created by the command "git clone https://github.com/MotorolaMobilityLLC/nuttx" that you had executed during the "Download Source Code" section.  Do you remember to move the dir or perform any other operation in this dir?

     

    My suggestion, if you do not have anything to loose (your code and changes), remove the nuttx and get the git repo again:

    cd $BUILD_TOP
    rm -Rf nuttx
    git clone https://github.com/MotorolaMobilityLLC/nuttx

     

    After that, follow the steps in your first post.

     

    Thanks

     

    Leo

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • erisonkwok
    0 erisonkwok over 8 years ago in reply to leo.andrade

    Hi Leo,

     

    Thank you very much.The error is gone.

    Doing what you suggest,step by step,everything goes well,and did not face that issue again.Maybe the last time I clone the nuttx folder missing some documents.

     

    Thanks

     

    Erison

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube