Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues configuring or building an example with pre-compiled docker image #132

Open
rajames opened this issue Mar 22, 2021 · 9 comments
Open

Comments

@rajames
Copy link
Contributor

rajames commented Mar 22, 2021

Description of the issue:

When using the prebuilt docker image I'm unable to configure and/or build the
hello example after following instructions in README.

How to reproduce:

$ git clone --recursive https://github.com/sonydevworld/spresense.git
$ git submodule foreach git checkout master

Then using the docker image:

$ source spresense_env.sh 
This script has to be sourced.
. ./spresense_env.sh or source spresense_env.sh
 
Using default tag: latest
latest: Pulling from devworldsony/spresense-sdk-env
Digest: sha256:3a2f02cf9e0a1063585db66ddca43d5633dd65545ea9d00dd88983de39ca24d6
Status: Image is up to date for devworldsony/spresense-sdk-env:latest
docker.io/devworldsony/spresense-sdk-env:latest
After this script executed successfully:
Usage: spresense [command]
This will run command in the Spresense SDK docker environment.

Followed by:

SpresenseSDK:$ spresense sh -c "cd /spresense/sdk && tools/config.py examples/hello"
make[1]: *** [include/arch/board] Error 1
make: *** [olddefconfig] Error 2
Post process failed. 512
Try 'make distclean' first.

Describe your hardware setup:

Software version used:

On master (commit: 6cb78083)

@rajames
Copy link
Contributor Author

rajames commented Mar 22, 2021

It appears that the following:

git submodule foreach git checkout master

updates the submodules:

modified   externals/nnablart/nnabla-c-runtime
@@ -1 +1 @@
-Subproject commit c58c11ddd182e8ed04eb931bbf2a82f190874c9d
+Subproject commit 57dd88dde097a51cd1864810814afc31eef9de5a
modified   nuttx
@@ -1 +1 @@
-Subproject commit 7686b71a7cfe17bf8f3fb1be7749594278b0c808
+Subproject commit f28c114ccdd5c58b2a372634d71440c676bd2fae

reverting the above changes seems to give better results (and 'fix' the problem)

@kamtom480
Copy link
Contributor

Hi @rajames

Does this mean the problem has been resolved and we can close this issue?

@rajames
Copy link
Contributor Author

rajames commented Mar 23, 2021

Hi @kamtom480 the problem is not resolved since following the README instructions I get the above described issue.
If you omit the git submodule foreach .. command from the README as you mentioned in #131 then this should resolve the issue.

@kamtom480
Copy link
Contributor

@rajames

Thank you for your confirmation. I created a PR #133 for this. When the #133 is merged I will close this issue.

@fxmarty
Copy link

fxmarty commented Apr 16, 2021

Hi, in which way this git issue is related with make olddefconfig failing?

@rajames
Copy link
Contributor Author

rajames commented Apr 21, 2021

@fxmarty Sorry, I'm not familiar with issue related with make olddefconfig

@kamtom480
Copy link
Contributor

@fxmarty This issue should not be related to make olddefconfig failing. Do you have problems with make olddefconfig?

@fxmarty
Copy link

fxmarty commented Apr 28, 2021

Sorry to pollute this issue then, I will post this single message.

Yes, spresense SDK's tools/config.py (e.g. called as ./tools/config.py examples/hello) would fail for me in do_olddefconfig(), when we try to perform make olddefconfig. Despite doing make distclean as suggested the error persists.

The actual root problem is the following, when executing make olddefconfig:

make[2]: Leaving directory '/home/felix/spresense/sdk/apps'
../sdk/apps/Kconfig:10: can't open file "/home/felix/spresense/sdk/apps/examples/Kconfig"

I wonder why in my case this Kconfig file is missing. I found a manual solution which at least does not show errors, which is to delete sdk/Kconfig and sdk/apps/Kconfig files. Deleting nuttx/.config is an alternative which also works.

After deleting such files, tools/config.py do not complain anymore.

@kamtom480
Copy link
Contributor

@fxmarty Could you please send me step by step what you do from the moment the repository is cloned until an error occurs?

What OS are you using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants