-
Notifications
You must be signed in to change notification settings - Fork 53
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
setup-environment default BUILDDIR is fragile #46
Comments
Perhaps passing BUILDDIR in the same way MACHINE is passed would be more robust? |
It turns out doing MACHINE=mymachine source setup-environment "." breaks openembedded-core badly. It seems having a "." in the TMPDIR path in site.conf breaks lots of stuff, like for example "bitbake texinfo-dummy-native". Instead, doing MACHINE=mymachine source setup-environment "" works better. The errors from "bitbake texinfo-dummy-native" were: ERROR: texinfo-dummy-native-1.0-r0 do_patch: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: Subprocess output: ERROR: Logfile of failure stored in: /home/fluke/work/fluke-cda-setup/angstrom-v2019.12-zeus-fluke-cda-manifest/./tmp-angstrom-glibc/work/x86_64-linux/texinfo-dummy-native/1.0-r0/temp/log.do_patch.22320 |
If I do
MACHINE=mymachine source setup-environment
inside my script, which was passed positional parameters, then setup-environment-internal sees the $* and $1 variables set and thinks the positional parameter was passed to setup-environment. So I have to explicitly do
MACHINE=mymachine source setup-environment "."
which I did not have to do with sumo.
The text was updated successfully, but these errors were encountered: