[yocto] Biweekly Status Report WW52~53'2010 --OSEL SDK Liping Ke
[Summary] 1. OSEL SDK related jobs 2. Others [Details] SDK related jobs: 1. Modified sdk installer scripts according to Josh's feedback, including a. Folder reorganization per Josh's suggestion, make the structure more user friendly b. Move sudo to a smaller granularity, so that user could input $HOME as parameters which will be parsed correctly outside sudo. c. restructure shell scripts, and move some scripts to another file for readability. d. Provide silent install and interactive install, so that user have more choices 2. Fixed several bugs/defects for shell scripts and bb files a. Made downloading files optional if the files exists. b. stored pseudo database in target rootfs, and export the path, so pseudo extract nfs does not need sudo at all. c. Linked ld.so.cache file into the host filesystem d. Moved tar actions to do_deploy from do_install, etc. 3. Add editor box UI in eclipse plugin for qemu extra parameters. 4. Do integral testing, bitbake installer tarball, untar the installer, install the sdk, And then launch eclipse plugin, and launch qemu. Fixed several bugs such as sdk version Problems (we now add version support), opkg source file chksum issues, etc. Now I have sent out all installer related materials for review. 5. Spent some time investigating why unfs qemu fails to boot, it was caused by latest kernel. 0.9 kernel + current unfs works fine. 6. Spent one day in looking bitbake code (ast, bbhandler, confhandler) for technical sharing session. Next step is that we need to find a repository, containing all archs build result, so That we can have a whole testing. I guess we need local build machine to do this. Others: 1. Take 2 days' annual leave 2. Take weekly project meeting and technical sharing meeting. Thanks & Regards, criping _ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] linux yocto private branch
On 10-12-28 07:54 PM, João Henrique Freitas wrote:
Hi,
This question is about how I can track linux yocto and maintain a
private kernel.
I am tracking the yocto master on git.
My target is to use linux-yocto kernel and with my personal machine
(IBM and HP blade servers x86-64 or x86).
Probably I need to setup some special driver like disk controller or
network device, but it's not the case now.
I want to track linux-yocto kernel. To accomplish it, I created a
linux-yocto_git.bbappend with:
SRC_URI =
"git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;fullclone=1;branch=${KBRANCH};name=machine
\
git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;noclone=1;branch=meta;name=meta
\
file://defconfig"
KMACHINE_mpg = "yocto/standard/common-pc/base"< it's right?
This will be right in a few weeks, but right now, the
searching for machine specific configuration is triggered
from the branch name, so you still require a machine
specific branch. This is a long standing optimization to
represent validated configurations in the kernel tree, but
to control branch "explosion" I've completed some changes
that allow many (unlimited) boards to be built from a single
branch.
So for this, you'd want "yocto/standard/common-pc/mpg", and
have a kernel tree that contains the branch (this is BSP
bootstrapping). I have a meta-kernel-dev layer that facilitates
a local clone (where you can easily make your own branch), and
it will be available in the poky-extras repo very soon (I don't
have push access at the moment).
COMPATIBLE_MACHINE = "mpg"<--- my kernel config
My doubt: KMACHINE_mpg can be "yocto/standard/mpg" or it need to be a
strict branch on yocto git?
See above. Your doubt was correct.
In other words, Can I have a private branch and track a default
yocto/standard/common-pc/base?
You can. You need to initially create your BSP branch from that
point, and as you update your tree, merge common-pc/base into
your BSP to pickup the main kernel updates.
To have your own kernel configuration, see the examples for
other BSPs on the 'meta' branch. Create your own infrastructure
there, and things will work. Since you are tracking a branch
besides 'standard/base' you need to have your own .scc file
on the meta branch since the auto detect logic will fall back
to tracking standard.
Cheers,
Bruce
I read kernel-manual_9.pdf, section 3.4.4 but I believe it's a bit outdate now.
Currently I can build linux-yocto and create a full image to be use
with VirtualBox and with real hardware.
Thanks.
PS:
I think that yocto can be use to build and runs in big machines too,
not only in small devices.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Recent build issues.
On 10-12-23 05:08 PM, Flanagan, Elizabeth wrote: Recent build issues: - There seem to be a few issues going on with sanity testing: First, I've made a change to how sanity tests are run on the autobuilder that should speed them up some. bitbake @ -c qemuimagetest creates a rootfs. I've switched this to bitbake @ -c qemuimagetest_standalone, so this shouldn't create a rootfs and should use the one already existing. We should see some performance improvement with this. I thought this had been included in my pull with BB 0.8.3 but I must have not included it. Next, the following bugs have been making it difficult to track down build failures: Sanity Test Boot test returns invalid results. http://bugzilla.pokylinux.org/show_bug.cgi?id=611 Sanity tests do not always kill QEMU once timeout is reached http://bugzilla.pokylinux.org/show_bug.cgi?id=595 There are also sanity test failures in a few images: qemuarm poky-image-sato qemuarm poky-image-minimal qemumips poky-image-sato mips seems to have run poky-image-minimal ok, but with Bug #611, I can't be sure that is the case and I doubt it's actually the case. My inclination is that there is an issue with arm and mips builds that should be looked at. - PPC is broken. PPC is having serious issues that seem to revolve around linux-yocto-2.6.37. Bruce I believe is working on this. Can anyone give an update around where this stands? Were we talking build or boot for this one ? The slow boot is only being seen during auto-tests, and I've never reproduced it here. I'm looking for someone who has time to debug this by tweaking the kernel configuration, but as for what we produce for qemuppc the configuration is sane and boots fine. Does anyone who can reproduce this have time to look into it a bit more, or get me access to a reproducing environment ? Bruce I'm running nightly-incremental and nightly now to pull in some changes made this morning and to prepare for weekend delivery to QA. I'll send out those build results on Sunday (or whenever the build finishes.) -b ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] Autobuilder fixes and added functionality
Some minor fixes to the Autobuilder. I've reverted to Buildbot 0.8.2 for the time being, as well as fixed some issues with poky-autobuild-generate-sources-tarball. There is also a nasty issue when you have easy_install installed on a system. The BB installer will attempt to install via easy_install, however, if the install directory does not exist, it fails to install. I now create the install directories beforehand. This is actually something that should be fixed on the BB side, and when I have some time I'll look at it. I've also added a --installbase option which does away with having to set all of the --(*)dir= options when you are trying to relocate the install from ~. Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: eflanagan/poky-ab-fixes Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=eflanagan/poky-ab-fixes Thanks, Beth Flanagan --- Beth Flanagan (1): Fix for easy_install, source tarball and 0.8.3 scripts/poky-autobuild-generate-sources-tarball |2 +- scripts/poky-setup-autobuilder | 59 +-- 2 files changed, 35 insertions(+), 26 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] Fix for easy_install, source tarball and 0.8.3
A few fixes here. First, reverting down to 0.8.2 for the time being since
there was issues with 0.8.3's git poller. Also, fixing an issue with how
bb setup.py works when setuptools is installed.
Fixing a known error in how generate sources tarball performs
Signed-off-by: Beth Flanagan
---
scripts/poky-autobuild-generate-sources-tarball |2 +-
scripts/poky-setup-autobuilder | 59 +--
2 files changed, 35 insertions(+), 26 deletions(-)
diff --git a/scripts/poky-autobuild-generate-sources-tarball
b/scripts/poky-autobuild-generate-sources-tarball
index 11ebda1..c445f24 100755
--- a/scripts/poky-autobuild-generate-sources-tarball
+++ b/scripts/poky-autobuild-generate-sources-tarball
@@ -19,7 +19,7 @@ if [[ -z "$RELEASE" || -z "$VERSION" ]]; then
fi
if [[ -z "$BRANCH" ]]; then
- $BRANCH = "master"
+ BRANCH = "master"
fi
BASEDIR=poky-tarball
diff --git a/scripts/poky-setup-autobuilder b/scripts/poky-setup-autobuilder
index 51e06eb..299b8c2 100755
--- a/scripts/poky-setup-autobuilder
+++ b/scripts/poky-setup-autobuilder
@@ -130,32 +130,33 @@ def configureBot(buildtype):
elif buildtype == "slave":
URL = bbSlaveDownloadUrl
bbInstallFile = "./" + URL.rpartition("/")[2]
-try:
-bbSourceDir = bbInstallerHome + "/" +
bbInstallFile.rpartition("/")[2].replace(".tar.gz", "")
-print "Configuring " + bbSourceDir
-os.chdir(bbSourceDir)
-os.system ("echo 'export PYTHONPATH=" + bbSourceDir +
"/lib/python2.6/site-packages/:$PYTHONPATH' >> "
-+ bbHome + "/.profile" )
-if buildtype == "master":
-bbInstallDir = bbMasterDir
-elif buildtype == "slave":
-bbInstallDir = bbSlaveDir
-cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
"/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py install
--prefix=" + bbInstallDir
-os.system (cmd)
-except:
-print "Issues Configuring "
-sys.exit(1)
-
-
-#BuildBot download parameters
-bbVersion = "0.8.3"
+#try:
+bbSourceDir = bbInstallerHome + "/" +
bbInstallFile.rpartition("/")[2].replace(".tar.gz", "")
+print "Configuring " + bbSourceDir
+os.chdir(bbSourceDir)
+os.system ("echo 'export PYTHONPATH=" + bbSourceDir +
"/lib/python2.6/site-packages/:$PYTHONPATH' >> "
++ bbHome + "/.profile" )
+if buildtype == "master":
+bbInstallDir = bbMasterDir
+elif buildtype == "slave":
+bbInstallDir = bbSlaveDir
+cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
"/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py build; python
./setup.py install --prefix=" + bbInstallDir
+os.system (cmd)
+#except:
+#print "Issues Configuring "
+#sys.exit(1)
+
+
+# BuildBot download parameters
+#bbVersion = "0.8.3"
+# Pushing this back down to 0.8.2 until 0.8.3p1 comes out.
+bbVersion = "0.8.2"
bbMasterDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-"; +
bbVersion + ".tar.gz"
bbSlaveDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-slave-"; +
bbVersion + ".tar.gz"
bbConfigDownloadUrl = None
bbInstallerHome = os.getcwd()
bbInstallFile = ""
-# We need the expanded path for ~ later
-bbHome = os.path.expanduser('~')
+bbHome = ""
bbType = None
bbSlaveDesc="Poky Autobuilder Example"
@@ -188,7 +189,8 @@ parser.add_option( "--maxlogs", help = "The max number of
logs you want saved. I
action = "store", dest = "bbMaxLogs", default = "10" )
parser.add_option( "--adminmail", help = "The administrator email address. If
left unset we set it to current user @ localhost",
action = "store", dest = "bbAdminMail", default =
"r...@localhost" )
-
+parser.add_option( "--installbase", help = "The base install directory. If
left unset we set we'll use --masterdir/slavedir/sourcedir/pstagedir/controldir
or their defaults",
+ action = "store", dest = "bbHome", default =
os.path.expanduser('~') )
options, args = parser.parse_args( sys.argv )
# We need to decide if we're doing a master or slave install or both
@@ -236,7 +238,10 @@ if bbPStagingDir == "":
if bbType == "master" or bbType == "both":
try:
-os.mkdir(bbMasterDir)
+# We do this here, because if setuputils is installed BuildBot wants
to use it the easy_install way
+# however, their easy_install way will fail if the dir does not exist.
It's a bug in the BB installer
+# that I'm going to have to figure out and push upstream.
+os.makedirs(bbMasterDir + "/lib/python2.6/site-packages/")
except:
print bbMasterDir + " already exists."
pass
@@ -332,7 +337,10 @@ c['projectURL'] = pokyABConfig.poky_projurl
if bbType == "slave" or bbType == "both":
try:
-os.mkdir(bbSlaveDir)
+#
[yocto] [PATCH 0/1] Autobuilder fixes and added functionality
Some minor fixes to the Autobuilder. I've reverted to Buildbot 0.8.2 for the time being, as well as fixed some issues with poky-autobuild-generate-sources-tarball. There is also a nasty issue when you have easy_install installed on a system. The BB installer will attempt to install via easy_install, however, if the install directory does not exist, it fails to install. I now create the install directories beforehand. This is actually something that should be fixed on the BB side, and when I have some time I'll look at it. I've also added a --installbase option which does away with having to set all of the --(*)dir= options when you are trying to relocate the install from ~. Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: eflanagan/bb-0.8.3 Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=eflanagan/bb-0.8.3 Thanks, Beth Flanagan --- Beth Flanagan (1): Fix for easy_install, source tarball and 0.8.3 scripts/poky-autobuild-generate-sources-tarball |2 +- scripts/poky-setup-autobuilder | 27 +++--- 2 files changed, 19 insertions(+), 10 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] Fix for easy_install, source tarball and 0.8.3
A few fixes here. First, reverting down to 0.8.2 for the time being since
there was issues with 0.8.3's git poller. Also, fixing an issue with how
bb setup.py works when setuptools is installed.
Fixing a known error in how generate sources tarball performs
Signed-off-by: Beth Flanagan
---
scripts/poky-autobuild-generate-sources-tarball |2 +-
scripts/poky-setup-autobuilder | 27 +++---
2 files changed, 19 insertions(+), 10 deletions(-)
diff --git a/scripts/poky-autobuild-generate-sources-tarball
b/scripts/poky-autobuild-generate-sources-tarball
index 11ebda1..c445f24 100755
--- a/scripts/poky-autobuild-generate-sources-tarball
+++ b/scripts/poky-autobuild-generate-sources-tarball
@@ -19,7 +19,7 @@ if [[ -z "$RELEASE" || -z "$VERSION" ]]; then
fi
if [[ -z "$BRANCH" ]]; then
- $BRANCH = "master"
+ BRANCH = "master"
fi
BASEDIR=poky-tarball
diff --git a/scripts/poky-setup-autobuilder b/scripts/poky-setup-autobuilder
index 51e06eb..ad31fef 100755
--- a/scripts/poky-setup-autobuilder
+++ b/scripts/poky-setup-autobuilder
@@ -140,22 +140,23 @@ def configureBot(buildtype):
bbInstallDir = bbMasterDir
elif buildtype == "slave":
bbInstallDir = bbSlaveDir
-cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
"/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py install
--prefix=" + bbInstallDir
+cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
"/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py build; python
./setup.py install --prefix=" + bbInstallDir
os.system (cmd)
except:
print "Issues Configuring "
sys.exit(1)
-#BuildBot download parameters
-bbVersion = "0.8.3"
+# BuildBot download parameters
+#bbVersion = "0.8.3"
+# Pushing this back down to 0.8.2 until 0.8.3p1 comes out.
+bbVersion = "0.8.2"
bbMasterDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-"; +
bbVersion + ".tar.gz"
bbSlaveDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-slave-"; +
bbVersion + ".tar.gz"
bbConfigDownloadUrl = None
bbInstallerHome = os.getcwd()
bbInstallFile = ""
-# We need the expanded path for ~ later
-bbHome = os.path.expanduser('~')
+bbHome = ""
bbType = None
bbSlaveDesc="Poky Autobuilder Example"
@@ -188,7 +189,8 @@ parser.add_option( "--maxlogs", help = "The max number of
logs you want saved. I
action = "store", dest = "bbMaxLogs", default = "10" )
parser.add_option( "--adminmail", help = "The administrator email address. If
left unset we set it to current user @ localhost",
action = "store", dest = "bbAdminMail", default =
"r...@localhost" )
-
+parser.add_option( "--installbase", help = "The base install directory. If
left unset we set we'll use --masterdir/slavedir/sourcedir/pstagedir/controldir
or their defaults",
+ action = "store", dest = "bbHome", default =
os.path.expanduser('~') )
options, args = parser.parse_args( sys.argv )
# We need to decide if we're doing a master or slave install or both
@@ -236,7 +238,10 @@ if bbPStagingDir == "":
if bbType == "master" or bbType == "both":
try:
-os.mkdir(bbMasterDir)
+# We do this here, because if setuputils is installed BuildBot wants
to use it the easy_install way
+# however, their easy_install way will fail if the dir does not exist.
It's a bug in the BB installer
+# that I'm going to have to figure out and push upstream.
+os.makedirs(bbMasterDir + "/lib/python2.6/site-packages/")
except:
print bbMasterDir + " already exists."
pass
@@ -332,7 +337,10 @@ c['projectURL'] = pokyABConfig.poky_projurl
if bbType == "slave" or bbType == "both":
try:
-os.mkdir(bbSlaveDir)
+# We do this here, because if setuputils is installed BuildBot wants
to use it the easy_install way
+# however, their easy_install way will fail if the dir does not exist.
It's a bug in the BB installer
+# that I'm going to have to figure out and push upstream.
+os.makedirs(bbSlaveDir + "/lib/python2.6/site-packages/")
os.mkdir(bbOutputDir)
os.mkdir(bbPStagingDir)
@@ -400,7 +408,7 @@ PSTAGEDIR=%s
# We should correct this for slave only/master only builds
print """
-nstallation complete. Please review the output above for any errors.
+Installation complete. Please review the output above for any errors.
Then edit the master.cfg file in %s and start the build master and
build slave by running 'make start' in %s and %s directories.
-
@@ -418,3 +426,4 @@ cd ; make start
""" % (bbMasterDir, bbMasterDir, bbSlaveDir, bbSlaveDir, bbSlaveDir,
bbSlaveDir)
+
--
1.7.1
___
yocto mailing lis
Re: [yocto] [PATCH 1/1] Fix for easy_install, source tarball and 0.8.3
Sorry about this. My initial reply to scrap the previous pull went to
only me and for some reason my generation of the second pull request is
pulling the wrong branch.
-b
On 01/03/2011 04:39 PM, Flanagan, Elizabeth wrote:
> A few fixes here. First, reverting down to 0.8.2 for the time being since
> there was issues with 0.8.3's git poller. Also, fixing an issue with how
> bb setup.py works when setuptools is installed.
>
> Fixing a known error in how generate sources tarball performs
>
> Signed-off-by: Beth Flanagan
> ---
> scripts/poky-autobuild-generate-sources-tarball |2 +-
> scripts/poky-setup-autobuilder | 27 +++---
> 2 files changed, 19 insertions(+), 10 deletions(-)
>
> diff --git a/scripts/poky-autobuild-generate-sources-tarball
> b/scripts/poky-autobuild-generate-sources-tarball
> index 11ebda1..c445f24 100755
> --- a/scripts/poky-autobuild-generate-sources-tarball
> +++ b/scripts/poky-autobuild-generate-sources-tarball
> @@ -19,7 +19,7 @@ if [[ -z "$RELEASE" || -z "$VERSION" ]]; then
> fi
>
> if [[ -z "$BRANCH" ]]; then
> - $BRANCH = "master"
> + BRANCH = "master"
> fi
>
> BASEDIR=poky-tarball
> diff --git a/scripts/poky-setup-autobuilder b/scripts/poky-setup-autobuilder
> index 51e06eb..ad31fef 100755
> --- a/scripts/poky-setup-autobuilder
> +++ b/scripts/poky-setup-autobuilder
> @@ -140,22 +140,23 @@ def configureBot(buildtype):
> bbInstallDir = bbMasterDir
> elif buildtype == "slave":
> bbInstallDir = bbSlaveDir
> -cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
> "/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py install
> --prefix=" + bbInstallDir
> +cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
> "/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py build; python
> ./setup.py install --prefix=" + bbInstallDir
> os.system (cmd)
> except:
> print "Issues Configuring "
> sys.exit(1)
>
>
> -#BuildBot download parameters
> -bbVersion = "0.8.3"
> +# BuildBot download parameters
> +#bbVersion = "0.8.3"
> +# Pushing this back down to 0.8.2 until 0.8.3p1 comes out.
> +bbVersion = "0.8.2"
> bbMasterDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-"; +
> bbVersion + ".tar.gz"
> bbSlaveDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-slave-";
> + bbVersion + ".tar.gz"
> bbConfigDownloadUrl = None
> bbInstallerHome = os.getcwd()
> bbInstallFile = ""
> -# We need the expanded path for ~ later
> -bbHome = os.path.expanduser('~')
> +bbHome = ""
> bbType = None
> bbSlaveDesc="Poky Autobuilder Example"
>
> @@ -188,7 +189,8 @@ parser.add_option( "--maxlogs", help = "The max number of
> logs you want saved. I
> action = "store", dest = "bbMaxLogs", default = "10"
> )
> parser.add_option( "--adminmail", help = "The administrator email address.
> If left unset we set it to current user @ localhost",
> action = "store", dest = "bbAdminMail", default =
> "r...@localhost" )
> -
> +parser.add_option( "--installbase", help = "The base install directory. If
> left unset we set we'll use
> --masterdir/slavedir/sourcedir/pstagedir/controldir or their defaults",
> + action = "store", dest = "bbHome", default =
> os.path.expanduser('~') )
> options, args = parser.parse_args( sys.argv )
>
> # We need to decide if we're doing a master or slave install or both
> @@ -236,7 +238,10 @@ if bbPStagingDir == "":
>
> if bbType == "master" or bbType == "both":
> try:
> -os.mkdir(bbMasterDir)
> +# We do this here, because if setuputils is installed BuildBot wants
> to use it the easy_install way
> +# however, their easy_install way will fail if the dir does not
> exist. It's a bug in the BB installer
> +# that I'm going to have to figure out and push upstream.
> +os.makedirs(bbMasterDir + "/lib/python2.6/site-packages/")
> except:
> print bbMasterDir + " already exists."
> pass
> @@ -332,7 +337,10 @@ c['projectURL'] = pokyABConfig.poky_projurl
>
> if bbType == "slave" or bbType == "both":
> try:
> -os.mkdir(bbSlaveDir)
> +# We do this here, because if setuputils is installed BuildBot wants
> to use it the easy_install way
> +# however, their easy_install way will fail if the dir does not
> exist. It's a bug in the BB installer
> +# that I'm going to have to figure out and push upstream.
> +os.makedirs(bbSlaveDir + "/lib/python2.6/site-packages/")
> os.mkdir(bbOutputDir)
> os.mkdir(bbPStagingDir)
>
> @@ -400,7 +408,7 @@ PSTAGEDIR=%s
> # We should correct this for slave only/master only builds
>
> print """
> -nstallation complete. Please review the output above for any errors.
> +Installation complete.
[yocto] [PATCH 0/1] Autobuilder fixes and added functionality
Some minor fixes to the Autobuilder. I've reverted to Buildbot 0.8.2 for the time being, as well as fixed some issues with poky-autobuild-generate-sources-tarball. There is also a nasty issue when you have easy_install installed on a system. The BB installer will attempt to install via easy_install, however, if the install directory does not exist, it fails to install. I now create the install directories beforehand. This is actually something that should be fixed on the BB side, and when I have some time I'll look at it. I've also added a --installbase option which does away with having to set all of the --(*)dir= options when you are trying to relocate the install from ~. Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: eflanagan/bb-0.8.3 Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=eflanagan/bb-0.8.3 Thanks, Beth Flanagan --- Beth Flanagan (1): Fix for easy_install, source tarball and 0.8.3 scripts/poky-autobuild-generate-sources-tarball |2 +- scripts/poky-setup-autobuilder | 27 +++--- 2 files changed, 19 insertions(+), 10 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] Fix for easy_install, source tarball and 0.8.3
A few fixes here. First, reverting down to 0.8.2 for the time being since
there was issues with 0.8.3's git poller. Also, fixing an issue with how
bb setup.py works when setuptools is installed.
Fixing a known error in how generate sources tarball performs
Signed-off-by: Beth Flanagan
---
scripts/poky-autobuild-generate-sources-tarball |2 +-
scripts/poky-setup-autobuilder | 27 +++---
2 files changed, 19 insertions(+), 10 deletions(-)
diff --git a/scripts/poky-autobuild-generate-sources-tarball
b/scripts/poky-autobuild-generate-sources-tarball
index 11ebda1..c445f24 100755
--- a/scripts/poky-autobuild-generate-sources-tarball
+++ b/scripts/poky-autobuild-generate-sources-tarball
@@ -19,7 +19,7 @@ if [[ -z "$RELEASE" || -z "$VERSION" ]]; then
fi
if [[ -z "$BRANCH" ]]; then
- $BRANCH = "master"
+ BRANCH = "master"
fi
BASEDIR=poky-tarball
diff --git a/scripts/poky-setup-autobuilder b/scripts/poky-setup-autobuilder
index 51e06eb..ad31fef 100755
--- a/scripts/poky-setup-autobuilder
+++ b/scripts/poky-setup-autobuilder
@@ -140,22 +140,23 @@ def configureBot(buildtype):
bbInstallDir = bbMasterDir
elif buildtype == "slave":
bbInstallDir = bbSlaveDir
-cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
"/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py install
--prefix=" + bbInstallDir
+cmd = "cd " + bbSourceDir + "; export PYTHONPATH=" + bbInstallDir +
"/lib/python2.6/site-packages/:$PYTHONPATH; python ./setup.py build; python
./setup.py install --prefix=" + bbInstallDir
os.system (cmd)
except:
print "Issues Configuring "
sys.exit(1)
-#BuildBot download parameters
-bbVersion = "0.8.3"
+# BuildBot download parameters
+#bbVersion = "0.8.3"
+# Pushing this back down to 0.8.2 until 0.8.3p1 comes out.
+bbVersion = "0.8.2"
bbMasterDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-"; +
bbVersion + ".tar.gz"
bbSlaveDownloadUrl = "http://buildbot.googlecode.com/files/buildbot-slave-"; +
bbVersion + ".tar.gz"
bbConfigDownloadUrl = None
bbInstallerHome = os.getcwd()
bbInstallFile = ""
-# We need the expanded path for ~ later
-bbHome = os.path.expanduser('~')
+bbHome = ""
bbType = None
bbSlaveDesc="Poky Autobuilder Example"
@@ -188,7 +189,8 @@ parser.add_option( "--maxlogs", help = "The max number of
logs you want saved. I
action = "store", dest = "bbMaxLogs", default = "10" )
parser.add_option( "--adminmail", help = "The administrator email address. If
left unset we set it to current user @ localhost",
action = "store", dest = "bbAdminMail", default =
"r...@localhost" )
-
+parser.add_option( "--installbase", help = "The base install directory. If
left unset we set we'll use --masterdir/slavedir/sourcedir/pstagedir/controldir
or their defaults",
+ action = "store", dest = "bbHome", default =
os.path.expanduser('~') )
options, args = parser.parse_args( sys.argv )
# We need to decide if we're doing a master or slave install or both
@@ -236,7 +238,10 @@ if bbPStagingDir == "":
if bbType == "master" or bbType == "both":
try:
-os.mkdir(bbMasterDir)
+# We do this here, because if setuputils is installed BuildBot wants
to use it the easy_install way
+# however, their easy_install way will fail if the dir does not exist.
It's a bug in the BB installer
+# that I'm going to have to figure out and push upstream.
+os.makedirs(bbMasterDir + "/lib/python2.6/site-packages/")
except:
print bbMasterDir + " already exists."
pass
@@ -332,7 +337,10 @@ c['projectURL'] = pokyABConfig.poky_projurl
if bbType == "slave" or bbType == "both":
try:
-os.mkdir(bbSlaveDir)
+# We do this here, because if setuputils is installed BuildBot wants
to use it the easy_install way
+# however, their easy_install way will fail if the dir does not exist.
It's a bug in the BB installer
+# that I'm going to have to figure out and push upstream.
+os.makedirs(bbSlaveDir + "/lib/python2.6/site-packages/")
os.mkdir(bbOutputDir)
os.mkdir(bbPStagingDir)
@@ -400,7 +408,7 @@ PSTAGEDIR=%s
# We should correct this for slave only/master only builds
print """
-nstallation complete. Please review the output above for any errors.
+Installation complete. Please review the output above for any errors.
Then edit the master.cfg file in %s and start the build master and
build slave by running 'make start' in %s and %s directories.
-
@@ -418,3 +426,4 @@ cd ; make start
""" % (bbMasterDir, bbMasterDir, bbSlaveDir, bbSlaveDir, bbSlaveDir,
bbSlaveDir)
+
--
1.7.1
___
yocto mailing lis
Re: [yocto] [poky] [PATCH 0/1] linux-yocto: update to 2.6.37-rc8 v2
On 12/31/2010 12:06 PM, Bruce Ashfield wrote: Saul, Here's the updated 2.6.37-rc8 pull request. The meta branch commit is now the correct 2.6.37 variant, and worked for my build testing here. Cheers, Bruce Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: zedd/kernel Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Thanks, Bruce Ashfield --- Bruce Ashfield (1): linux-yocto: update to 2.6.37-rc8 .../conf/distro/include/poky-default-revisions.inc | 22 ++-- 1 files changed, 11 insertions(+), 11 deletions(-) ___ poky mailing list p...@yoctoproject.org https://lists.yoctoproject.org/listinfo/poky Pulled into Master Thanks Sau! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [poky] [PATCH 0/1] linux-yocto/stable: update to 2.6.34.x -longterm
On 01/02/2011 10:11 PM, Bruce Ashfield wrote: Richard/Saul, Paul Gortmaker maintains the upstream 2.6.34.x -longerm tree. The yocto stable kernel tracks this tree and incorporates those nominated changes. We are picking up lots of bug fixes and security updates to the -stable tree with this change. This commit updates the BSP SRCREVs to the latest 2.6.34.x merge and picks up 260 -stable commits for each BSP. Tom: the meta-emenlow layer should be updated with the new SRCREV. I updated the master version, and simply tossed any changes to the drivers modified by the emenlow. So taking a quick look at the merge might be a good idea as well. I did my own build tests here and everything looked sane. Darren: I had to resolve a merge in the -rt branches, and preferred the -rt implementation of the files in question. I used your patches that are out for review and confirmed that qemux86-64-preempt_rt builds with the updated kernel. I built all the -stable boards, and everything looks sane, so this one should be good to go. Cheers, Bruce Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: zedd/stable Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/stable Thanks, Bruce Ashfield --- Bruce Ashfield (1): linux-yocto/stable: update SRCREVs for 2.6.34.x -stable update .../conf/distro/include/poky-default-revisions.inc | 20 ++-- 1 files changed, 10 insertions(+), 10 deletions(-) ___ poky mailing list p...@yoctoproject.org https://lists.yoctoproject.org/listinfo/poky Pulled into Master Thanks Sau! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] M3 Package Update List
Hi Saul, Here is an update for recipes in the list under my name. I upgraded most of the recipes except: 1) upstream check error, actually they are up to date. Speex, net-tools, libid3tag, libgsmd 2) git development tree: Mtd-utils 3) dependency on other recipes: Clutter-gst (depend on latest version of clutter). Thanks, Dongxiao Saul Wold wrote: > Folks, > > Please find attached the list of M3 Recipe Updates, our goal for 1.0 > M3 release is to complete the update process we started in 0.9 and > 1.0 M2. > There are about 150 recipes in this list, some people may have more > and if there is a need to request help, please let me know. If you > plan on helping, please let the current owner know that you will be > updating a recipe. > > Unless I hear otherwise, I will work to update the "None" maintained > list, but I believe some of these are owned by people and the distro > tracking information needs to be updated. > > Thanks again to the team for the hard work during 0.9 and M2, we will > always have updates to do, but they will get easier with our gained > experience and expertise. > > Happy Holidays and Happy New Year to all. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
