SVN woes persist
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 1286462951.15840.6345.camel@rex
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 1286475616.15840.6565.camel@rex
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 23 lines · Gary Thomas
I updated to include these changes and gave it a try. Here's what I did:
% mkdir /work/new_build
% cd /work/poky_tree
% . poky-init-build-env /work/new_build
... adjustDL_DIR, etc inconf/local.conf
SSTATE_MIRRORSis not defined yet
% bitbake some-image% mv sstate-cache sstate
% mv tmp tmp.old... adjust conf/local.conf to set SSTATE_MIRRORS like this SSTATE_MIRRORS ?= "\ file://.* file:///work/new_build/sstate/"% bitbake some-image
First of all, it took an incredible length of time (maybe a minute on my fast machine) to even move past the resolve step. Then it went off spewing lines about the state files (sadly I didn't save them). It then proceeded to run through some 322 steps, telling me more about state files. This took quite some time. Then it seemed to just start the normal build all over, apparently without regard to any of the sstate info.
Quoted 5 lines
Did I miss something? Is this how it should work?
Sorry to be such a pain over this, but I'd really like to see this part working. If there's something I can help with it, please let me know - I know my way around Python code, but I don't know all the internals of how you expect this to work.
Sorry not to get back to you sooner, I'm being pulled in a few different directions and we're coming up to release.
In my own tests I've noticed a few issues and I've just pushed a number of fixes into the master branch which should help in various areas.
With regard to your specific test and problem, it shouldn't rebuild everything. It turns out that I'd tested with http:// mirror urls and not file:// ones which needed and extra piece of code to handle them correctly.
Have another try with master and see if things are better this time!
Cheers,
Richard
Quoted 36 lines · Richard Purdie
Quoted 23 lines · Gary Thomas
I updated to include these changes and gave it a try. Here's what I did:
% mkdir /work/new_build
% cd /work/poky_tree
% . poky-init-build-env /work/new_build
... adjustDL_DIR, etc inconf/local.conf
SSTATE_MIRRORSis not defined yet
% bitbake some-image% mv sstate-cache sstate
% mv tmp tmp.old
... adjustconf/local.confto setSSTATE_MIRRORSlike this
SSTATE_MIRRORS?= "\
file://.* file:///work/new_build/sstate/"% bitbake some-image
First of all, it took an incredible length of time (maybe a minute on my fast machine) to even move past the resolve step. Then it went off spewing lines about the state files (sadly I didn't save them). It then proceeded to run through some 322 steps, telling me more about state files. This took quite some time. Then it seemed to just start the normal build all over, apparently without regard to any of the sstate info.
Quoted 5 lines
Did I miss something? Is this how it should work?
Sorry to be such a pain over this, but I'd really like to see this part working. If there's something I can help with it, please let me know - I know my way around Python code, but I don't know all the internals of how you expect this to work.
Sorry not to get back to you sooner, I'm being pulled in a few different directions and we're coming up to release.
In my own tests I've noticed a few issues and I've just pushed a number of fixes into the master branch which should help in various areas.
Quoted 6 lines
With regard to your specific test and problem, it shouldn't rebuild everything. It turns out that I'd tested with http:// mirror urls and not file:// ones which needed and extra piece of code to handle them correctly.
Have another try with master and see if things are better this time!
Will do.
Should this address the similar issue with GIT packages. These seem to be updating every time as well:
git_github.com.wrpseudo.pseudo.git.tar.gz git_git.pokylinux.org.wr-kernel-tools.git.tar.gz git_git.pokylinux.org.prelink-cross.git.tar.gz
I'm still hoping for a way to have a static (no network needed) setup soon. I have to provide such in a training for some of my customers in about a month :-)
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 7 lines · Gary Thomas
Will do.
Should this address the similar issue with GIT packages. These seem to be updating every time as well:
git_github.com.wrpseudo.pseudo.git.tar.gz git_git.pokylinux.org.wr-kernel-tools.git.tar.gz git_git.pokylinux.org.prelink-cross.git.tar.gz
There are changes in master which will stop everything except the linux-wrs recipe doing that. The linux-wrs recipe uses "fullclone" mode of the git fetcher and this has known issues which we will address soon.
If anything other than linux-wrs is refreshing on master other than that recipe, let us know.
Quoted 3 lines
I'm still hoping for a way to have a static (no network needed) setup soon. I have to provide such in a training for some of my customers in about a month :-)
It is meant to work like that!
Cheers,
Richard
Quoted 9 lines · Richard Purdie
Quoted 7 lines · Gary Thomas
Will do.
Should this address the similar issue with GIT packages. These seem to be updating every time as well:
git_github.com.wrpseudo.pseudo.git.tar.gz git_git.pokylinux.org.wr-kernel-tools.git.tar.gz git_git.pokylinux.org.prelink-cross.git.tar.gz
Quoted 6 lines
There are changes in master which will stop everything except the linux-wrs recipe doing that. The linux-wrs recipe uses "fullclone" mode of the git fetcher and this has known issues which we will address soon.
If anything other than linux-wrs is refreshing on master other than that recipe, let us know.
Looks good. The one one that got updated today with a full build was pseudo and that's because the pinned revision was changed since I last merged.
Quoted 5 lines
Quoted 3 lines
I'm still hoping for a way to have a static (no network needed) setup soon. I have to provide such in a training for some of my customers in about a month :-)
It is meant to work like that!
This part is working much better now, thanks.
Any progress on a way to hot-start things with the staged packages? When last I tried it, it brought my system to its knees with no benefit (see original message from 2010-10-07)
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 14 lines · Gary Thomas
Quoted 13 lines · Richard Purdie
Quoted 7 lines · Gary Thomas
Will do.
Should this address the similar issue with GIT packages. These seem to be updating every time as well:
git_github.com.wrpseudo.pseudo.git.tar.gz git_git.pokylinux.org.wr-kernel-tools.git.tar.gz git_git.pokylinux.org.prelink-cross.git.tar.gzThere are changes in master which will stop everything except the linux-wrs recipe doing that. The linux-wrs recipe uses "fullclone" mode of the git fetcher and this has known issues which we will address soon.
Quoted 5 lines
Quoted 2 lines
If anything other than linux-wrs is refreshing on master other than that recipe, let us know.
Looks good. The one one that got updated today with a full build was pseudo and that's because the pinned revision was changed since I last merged.
Right, once its generated its tarball, it shouldn't touch the repo again.
Quoted 11 lines
Quoted 5 lines
Quoted 3 lines
I'm still hoping for a way to have a static (no network needed) setup soon. I have to provide such in a training for some of my customers in about a month :-)
It is meant to work like that!
This part is working much better now, thanks.
Any progress on a way to hot-start things with the staged packages? When last I tried it, it brought my system to its knees with no benefit (see original message from 2010-10-07)
I thought my last email made this clear, we've fixed issues, it works better now.
Unfortunately there is an issue with the bits of the toolchain overwriting each other so a build using the packages isn't entirely working but you can for example generate images using them. All the pieces are there and we just need to iron out a few bugs.
Cheers,
Richard