Date   

Re: Bug Verify

Bruce Ashfield <bruce.ashfield@...>
 

On 10-12-13 11:47 AM, Scott Garman wrote:
On 12/13/2010 01:20 AM, Yu, Ke wrote:
Hi,

I hate to raise this question, but there is still bunch of bugs that
is fixed but not verified. According to the process, it is reporter's
responsibility to verify the bug, so could I ask the reporter's help
on this? Process is sometime tedious but helpful to quality
assurance. Thanks a lot for your effort.
I have now verified all my bugs.

However, the process doesn't seem right to me. As the person who fixed
the bug, presumably I performed verification that my fix actually works,
which is why I marked the bug as fixed to begin with.

At every other company I've been with, bug verification is performed by
the QA team - and I think the purpose of it is to ensure someone other
than the developer who fixed the bug can independently verify the bug is
indeed resolved. A second pair of eyes can spot new problems more easily.
I'd second Scott's opinion here. I wasn't marking my bugs
as verified, since as a submitter, I've never had to do
this in 10+ years in the 'biz'.

Cheers,

Bruce


JMO,

Scott


Re: Bug Verify

Scott Garman <scott.a.garman@...>
 

On 12/13/2010 01:20 AM, Yu, Ke wrote:
Hi,

I hate to raise this question, but there is still bunch of bugs that
is fixed but not verified. According to the process, it is reporter's
responsibility to verify the bug, so could I ask the reporter's help
on this? Process is sometime tedious but helpful to quality
assurance. Thanks a lot for your effort.
I have now verified all my bugs.

However, the process doesn't seem right to me. As the person who fixed the bug, presumably I performed verification that my fix actually works, which is why I marked the bug as fixed to begin with.

At every other company I've been with, bug verification is performed by the QA team - and I think the purpose of it is to ensure someone other than the developer who fixed the bug can independently verify the bug is indeed resolved. A second pair of eyes can spot new problems more easily.

JMO,

Scott

--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project


Re: update status of M2 sprint tasks

Mark Hatle <mark.hatle@...>
 

On 12/13/10 5:53 AM, Tian, Kevin wrote:
Hi, owners,

Since M2 code frozen happened last week and now M2 test has been started, could owners
of each M2 sprint tasks update the latest status on the wiki?

https://wiki.yoctoproject.org/wiki/Yocto_1.0_Schedule

As Saul sent out earlier, we only accept bug fixes on M2 branch now. So if a given task has
not been done (WIP or on track), could you either move it into M3 or fill an updated date
when current one is past?

--M2SB--

"Distro Audit: Package Description/Summary completed", "WIP, Done by Dec 08" (Mark)
I have the work done and tested. Is it too late to submit this?

(There are no code changes, just recipe Description/Summary changes..)

"Zypper/RPM (small writeup)", "WIP, Done by Dec 06" (Mark/Qing)
The write up is done, and outside of the tree.. I just have to post it on the wiki..

"oprofileUI", "WIP, done by Dec 10 " (Jessica)

--M2SC--
"Distro Audit: Licence Checksums ", "WIP, done by Dec 10 " (Saul)
"Zypper/RPM (upgrade to latest version)", "Starting, done by Dec 10" (Mark/Qing)
"push of all relevant Wind River patchs to Yocto ", "WIP, on track for completion by Dec 03 " (Mark)
"Tracing: blktrace and sysprof recipes ", "sysprof by Dec 03 " (Tom)

--M2SD--
"Yocto Installer for SDK Generator Installation functions support ", "WIP, done Dec 09" (Jessica)
"Yocto Installer support for image-creator ", "WIP" (Jessica)

--M2SE--
"Zypper/RPM (integration design)", "slipped out from sprint D" (Mark/Qing)
"Distro Audit: Upgrades Completed (Phase1)", "WIP" (Saul)
"Distro Audit: Src Checksums", "WIP, Done by Dec 9" (Saul)
"enable KVM with qemu", "on track" (Saul/Edwin)
"Performance Enhancement Completed", "on track being reviewed" (Saul/Dongxiao/Qing)
"User specified qemu config support", "on track for Dec 9" (Saul/Criping)
"SDK Version Control support in SDK generator installer", "on track" (Jessica)
"Tracing: Initial SystemTap recipe", "on track" (Tom)
"Documentation for swabber", "on track" (Alex)
"Defect triage process in public documented and implemented" (Saul)

Thanks
Kevin


Re: Some simple tests about pseudo performance

Mark Hatle <mark.hatle@...>
 

On 12/9/10 9:09 PM, Xu, Dongxiao wrote:
Test results are:

Native: 2.729 secs
Fakeroot: 2.752 secs
Pseudo: 51.814 secs

We saw pseudo cost about 20 times of seconds than native and fakeroot.
I believe that this is part of the fundamental differences between fakeroot and
pseudo. Fakeroot only persists data on shutdown, while pseudo does persistence
during the read/writes.

What I'm surprised by is that opening/closing the SAME file is so busy. I would
have expected the larger overhead to be in multiple file read/writes.

I did a profile when the program is running. From the following table we saw
that a lot of cycles are within sqlite3 operations...

I am wondering whether this point can be optimized? For example, is it
workable to cache those database operations in memory and finally flush it into
disk when pseudo exits?
Pseudo is using sqlite directly.

I did some basic checking, and sqlite has been instructed to run with the
following modes:

PRAGMA legacy_file_format = OFF
PRAGMA journal_mode = PERSIST
PRAGMA locking_mode = EXCLUSIVE
PRAGMA synchronous = OFF

Without doing any further investigation perhaps those modes aren't the best ones
to use? Also in prior work I've done with sqlite using transaction cues seemed
to also help with performance.

It would be interesting to determine where the performance penalties are in
this. I'm guessing it's the name resolution... but I'm still surprised at the
speed. (There is also an IPC transaction between libpseudo and the pseudo
server. From your logs that doesn't appear to be too bad though.)

--Mark

It's just a first thought and any suggestion and comment is welcome.

Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask of 0x00 (No unit mask) count 100000
samples % image name app name symbol name
693127 58.2980 no-vmlinux no-vmlinux /no-vmlinux
211108 17.7560 libsqlite3.so.0.8.6 libsqlite3.so.0.8.6 /usr/lib/libsqlite3.so.0.8.6
112269 9.4428 libc-2.10.1.so libc-2.10.1.so /lib/tls/i686/cmov/libc-2.10.1.so
16792 1.4124 [vdso] (tgid:28674 range:0xfd0000-0xfd1000) a.out [vdso] (tgid:28674 range:0xfd0000-0xfd1000)
15256 1.2832 libpthread-2.10.1.so libpthread-2.10.1.so pthread_mutex_lock
13163 1.1071 libpthread-2.10.1.so libpthread-2.10.1.so __pthread_mutex_unlock_usercnt
7386 0.6212 libpseudo.so libpseudo.so pseudo_client_op
6753 0.5680 libpseudo.so libpseudo.so pseudo_debug_real
6680 0.5618 pseudo pseudo pseudo_server_start
6663 0.5604 [vdso] (tgid:28676 range:0x8d6000-0x8d7000) pseudo [vdso] (tgid:28676 range:0x8d6000-0x8d7000)
5049 0.4247 pseudo pseudo pseudo_op
4906 0.4126 [vdso] (tgid:28467 range:0xd32000-0xd33000) a.out [vdso] (tgid:28467 range:0xd32000-0xd33000)
4427 0.3723 [vdso] (tgid:28607 range:0x5c0000-0x5c1000) a.out [vdso] (tgid:28607 range:0x5c0000-0x5c1000)
4391 0.3693 [vdso] (tgid:29027 range:0x6d0000-0x6d1000) a.out [vdso] (tgid:29027 range:0x6d0000-0x6d1000)
4188 0.3522 [vdso] (tgid:29172 range:0x41a000-0x41b000) a.out [vdso] (tgid:29172 range:0x41a000-0x41b000)
3584 0.3014 [vdso] (tgid:2411 range:0x892000-0x893000) a.out [vdso] (tgid:2411 range:0x892000-0x893000)
2985 0.2511 pseudo pseudo pseudo_debug_real
2921 0.2457 postgres postgres /usr/lib/postgresql/8.3/bin/postgres
2905 0.2443 vim.basic vim.basic /usr/bin/vim.basic
2449 0.2060 bash bash /bin/bash
2439 0.2051 libpseudo.so libpseudo.so fopen
2163 0.1819 [vdso] (tgid:28609 range:0x3da000-0x3db000) pseudo [vdso] (tgid:28609 range:0x3da000-0x3db000)
2096 0.1763 [vdso] (tgid:29029 range:0xfef000-0xff0000) pseudo [vdso] (tgid:29029 range:0xfef000-0xff0000)
2086 0.1755 libpseudo.so libpseudo.so pseudo_append_element
1917 0.1612 [vdso] (tgid:28469 range:0xe72000-0xe73000) pseudo [vdso] (tgid:28469 range:0xe72000-0xe73000)
1835 0.1543 libpseudo.so libpseudo.so wrap_fopen
1833 0.1542 libpseudo.so libpseudo.so pseudo_msg_receive
1819 0.1530 libpseudo.so libpseudo.so __lxstat64
1762 0.1482 libpseudo.so libpseudo.so __i686.get_pc_thunk.bx

Thanks,
Dongxiao


Re: version problems about SDK

Tian, Kevin <kevin.tian@...>
 

From: Joshua Lock
Sent: Monday, December 13, 2010 8:01 PM

On Sun, 2010-12-12 at 23:53 -0800, Zhang, Jessica wrote:
Tian, Kevin wrote:
From: Ke, Liping
Sent: Monday, December 13, 2010 2:53 PM

Hi, Jessica & Josh

When we are trying to run installer script on lianhao's x86_64
machine, we found if the images are build in two days, according to
current version naming convention, some of the packages will be
installed to /opt/poky/0.9+snapshot-20101210, some will be to
/opt/poky/0.9+snapshot-20101210.
It will cause problem since we need to know the exact version number
before installing and searching some files (environment script file,
etc). And the same releases of packages belong to different version
(just the build date is not in the same day) seems very strange and
hard to handle for us?
I think Josh has laid down the base for multiple version SDK support.
The only problem is:

SDKPATH = "/opt/${DISTRO}/${DISTRO_VERSION}"

which obviously is not what we want. We need a similar variable like
SDK_VERSION, which is incremented only when SDK team thinks there's a
need for a new version release or
else it keeps same in the life cycle of current version.
I disagree, I think it's definitely useful to know which distribution
version your SDK is built against. In fact as the SDK components are
generated from the distro metadata introducing an extra variable seems a
little superfluous and just increases the number of things which need to
be changed for a release.
Yes, SDK is generated from the distro metadata, which however doesn't prevent SDK
as a standalone component to have its own version variable. We can have:

SDK_VERSION = ${DISTRO_VERSION}

or,

SDK_VERSION = ${DISTRO_VERSION}${SDK_REVISION}

or,

SDK_VERSION = ...

I'm just a little bit worried to deduce SDK version from another variable (SDKPATH)
implicitly.

I agree that to have distribution version included will be informative, e.g in Android:
"SDK platform Andriod 2.3, API 9, revision 1"


Also note the DATE element is only included in the DISTRO_VERSION for
development snapshots.
Good to know this info.

Thanks
Kevin


Re: Bug Verify

Tian, Kevin <kevin.tian@...>
 

From: Joshua Lock [mailto:josh@...]
Sent: Monday, December 13, 2010 8:07 PM

On Mon, 2010-12-13 at 19:56 +0800, Tian, Kevin wrote:
From: Joshua Lock
Sent: Monday, December 13, 2010 7:49 PM

On Mon, 2010-12-13 at 17:20 +0800, Yu, Ke wrote:
Hi,

I hate to raise this question, but there is still bunch of bugs that is fixed but not verified.
According to the process, it is reporter's responsibility to verify the bug, so could I ask
the
reporter's help on this? Process is sometime tedious but helpful to quality assurance.
Thanks
a lot for your effort.

I've just gone through and verified the bugs I've filed. I think we
could make this process easier to remember if we had a shared saved
search "bugs I need to verify"?
You should be able to save that search under your account directly... :-)
Of course, but I can only create a saved search for myself (and I now
have that).

However, I was assuming the bugzilla admin could create a search which
would show the logged in user all of their bugs which need verifying.

Just trying to think of ways to make this process more obvious for the
team.
Got it. I'm not an export on Bugzilla. Perhaps Kangkang can have some comment whether
this is feasible. It looks a good thing though. :-)

Thanks
Kevin


[PATCH 0/1] bug#565: adding environment files

Lianhao Lu <lianhao.lu@...>
 

I rebased the previous patch of adding package of environment files to
be compatible with the new cross-canadian.bbclass

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: llu/bug565
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=llu/bug565

Thanks,
Lianhao Lu <lianhao.lu@...>
---


Lianhao Lu (1):
Fix bug #565.

meta/classes/toolchain-scripts.bbclass | 32 ++++++++++
meta/recipes-core/meta/meta-environment.bb | 74 ++++++++++++++++++++++++
meta/recipes-core/tasks/task-cross-canadian.bb | 1 +
3 files changed, 107 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-core/meta/meta-environment.bb


Re: Bug Verify

Joshua Lock <josh@...>
 

On Mon, 2010-12-13 at 19:56 +0800, Tian, Kevin wrote:
From: Joshua Lock
Sent: Monday, December 13, 2010 7:49 PM

On Mon, 2010-12-13 at 17:20 +0800, Yu, Ke wrote:
Hi,

I hate to raise this question, but there is still bunch of bugs that is fixed but not verified.
According to the process, it is reporter's responsibility to verify the bug, so could I ask the
reporter's help on this? Process is sometime tedious but helpful to quality assurance. Thanks
a lot for your effort.

I've just gone through and verified the bugs I've filed. I think we
could make this process easier to remember if we had a shared saved
search "bugs I need to verify"?
You should be able to save that search under your account directly... :-)
Of course, but I can only create a saved search for myself (and I now
have that).

However, I was assuming the bugzilla admin could create a search which
would show the logged in user all of their bugs which need verifying.

Just trying to think of ways to make this process more obvious for the
team.

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre


Re: version problems about SDK

Joshua Lock <joshua.lock@...>
 

On Sun, 2010-12-12 at 23:53 -0800, Zhang, Jessica wrote:
Tian, Kevin wrote:
From: Ke, Liping
Sent: Monday, December 13, 2010 2:53 PM

Hi, Jessica & Josh

When we are trying to run installer script on lianhao's x86_64
machine, we found if the images are build in two days, according to
current version naming convention, some of the packages will be
installed to /opt/poky/0.9+snapshot-20101210, some will be to
/opt/poky/0.9+snapshot-20101210.
It will cause problem since we need to know the exact version number
before installing and searching some files (environment script file,
etc). And the same releases of packages belong to different version
(just the build date is not in the same day) seems very strange and
hard to handle for us?
I think Josh has laid down the base for multiple version SDK support.
The only problem is:

SDKPATH = "/opt/${DISTRO}/${DISTRO_VERSION}"

which obviously is not what we want. We need a similar variable like
SDK_VERSION, which is incremented only when SDK team thinks there's a
need for a new version release or
else it keeps same in the life cycle of current version.
I disagree, I think it's definitely useful to know which distribution
version your SDK is built against. In fact as the SDK components are
generated from the distro metadata introducing an extra variable seems a
little superfluous and just increases the number of things which need to
be changed for a release.

Also note the DATE element is only included in the DISTRO_VERSION for
development snapshots.

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


Re: update status of M2 sprint tasks

Tian, Kevin <kevin.tian@...>
 

I tried to CC all the owners in original mail, which however ended up to need moderation
because too many recipients. (not sure why only Saul is kept. :-)) So please take a look
on below list to make sure your owned item being updated.

Thanks
Kevin

From: Tian, Kevin
Sent: Monday, December 13, 2010 7:54 PM

Hi, owners,

Since M2 code frozen happened last week and now M2 test has been started, could owners
of each M2 sprint tasks update the latest status on the wiki?

https://wiki.yoctoproject.org/wiki/Yocto_1.0_Schedule

As Saul sent out earlier, we only accept bug fixes on M2 branch now. So if a given task has
not been done (WIP or on track), could you either move it into M3 or fill an updated date
when current one is past?

--M2SB--

"Distro Audit: Package Description/Summary completed", "WIP, Done by Dec 08" (Mark)
"Zypper/RPM (small writeup)", "WIP, Done by Dec 06" (Mark/Qing)
"oprofileUI", "WIP, done by Dec 10 " (Jessica)

--M2SC--
"Distro Audit: Licence Checksums ", "WIP, done by Dec 10 " (Saul)
"Zypper/RPM (upgrade to latest version)", "Starting, done by Dec 10" (Mark/Qing)
"push of all relevant Wind River patchs to Yocto ", "WIP, on track for completion by Dec 03
" (Mark)
"Tracing: blktrace and sysprof recipes ", "sysprof by Dec 03 " (Tom)

--M2SD--
"Yocto Installer for SDK Generator Installation functions support ", "WIP, done Dec 09"
(Jessica)
"Yocto Installer support for image-creator ", "WIP" (Jessica)

--M2SE--
"Zypper/RPM (integration design)", "slipped out from sprint D" (Mark/Qing)
"Distro Audit: Upgrades Completed (Phase1)", "WIP" (Saul)
"Distro Audit: Src Checksums", "WIP, Done by Dec 9" (Saul)
"enable KVM with qemu", "on track" (Saul/Edwin)
"Performance Enhancement Completed", "on track being reviewed" (Saul/Dongxiao/Qing)
"User specified qemu config support", "on track for Dec 9" (Saul/Criping)
"SDK Version Control support in SDK generator installer", "on track" (Jessica)
"Tracing: Initial SystemTap recipe", "on track" (Tom)
"Documentation for swabber", "on track" (Alex)
"Defect triage process in public documented and implemented" (Saul)

Thanks
Kevin
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: Bug Verify

Tian, Kevin <kevin.tian@...>
 

From: Joshua Lock
Sent: Monday, December 13, 2010 7:49 PM

On Mon, 2010-12-13 at 17:20 +0800, Yu, Ke wrote:
Hi,

I hate to raise this question, but there is still bunch of bugs that is fixed but not verified.
According to the process, it is reporter's responsibility to verify the bug, so could I ask the
reporter's help on this? Process is sometime tedious but helpful to quality assurance. Thanks
a lot for your effort.

I've just gone through and verified the bugs I've filed. I think we
could make this process easier to remember if we had a shared saved
search "bugs I need to verify"?
You should be able to save that search under your account directly... :-)

Thanks
Kevin


update status of M2 sprint tasks

Tian, Kevin <kevin.tian@...>
 

Hi, owners,

Since M2 code frozen happened last week and now M2 test has been started, could owners
of each M2 sprint tasks update the latest status on the wiki?

https://wiki.yoctoproject.org/wiki/Yocto_1.0_Schedule

As Saul sent out earlier, we only accept bug fixes on M2 branch now. So if a given task has
not been done (WIP or on track), could you either move it into M3 or fill an updated date
when current one is past?

--M2SB--

"Distro Audit: Package Description/Summary completed", "WIP, Done by Dec 08" (Mark)
"Zypper/RPM (small writeup)", "WIP, Done by Dec 06" (Mark/Qing)
"oprofileUI", "WIP, done by Dec 10 " (Jessica)

--M2SC--
"Distro Audit: Licence Checksums ", "WIP, done by Dec 10 " (Saul)
"Zypper/RPM (upgrade to latest version)", "Starting, done by Dec 10" (Mark/Qing)
"push of all relevant Wind River patchs to Yocto ", "WIP, on track for completion by Dec 03 " (Mark)
"Tracing: blktrace and sysprof recipes ", "sysprof by Dec 03 " (Tom)

--M2SD--
"Yocto Installer for SDK Generator Installation functions support ", "WIP, done Dec 09" (Jessica)
"Yocto Installer support for image-creator ", "WIP" (Jessica)

--M2SE--
"Zypper/RPM (integration design)", "slipped out from sprint D" (Mark/Qing)
"Distro Audit: Upgrades Completed (Phase1)", "WIP" (Saul)
"Distro Audit: Src Checksums", "WIP, Done by Dec 9" (Saul)
"enable KVM with qemu", "on track" (Saul/Edwin)
"Performance Enhancement Completed", "on track being reviewed" (Saul/Dongxiao/Qing)
"User specified qemu config support", "on track for Dec 9" (Saul/Criping)
"SDK Version Control support in SDK generator installer", "on track" (Jessica)
"Tracing: Initial SystemTap recipe", "on track" (Tom)
"Documentation for swabber", "on track" (Alex)
"Defect triage process in public documented and implemented" (Saul)

Thanks
Kevin


Re: Bug Verify

Joshua Lock <josh@...>
 

On Mon, 2010-12-13 at 17:20 +0800, Yu, Ke wrote:
Hi,

I hate to raise this question, but there is still bunch of bugs that is fixed but not verified. According to the process, it is reporter's responsibility to verify the bug, so could I ask the reporter's help on this? Process is sometime tedious but helpful to quality assurance. Thanks a lot for your effort.
I've just gone through and verified the bugs I've filed. I think we
could make this process easier to remember if we had a shared saved
search "bugs I need to verify"?

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre


[PATCH 1/1] Fix bug #565.

Lianhao Lu <lianhao.lu@...>
 

Added package of meta-environment-${TARGET_ARCH} for environment
files.

Signed-off-by: Lianhao Lu <lianhao.lu@...>
---
meta/classes/toolchain-scripts.bbclass | 32 ++++++++++
meta/recipes-core/meta/meta-environment.bb | 74 ++++++++++++++++++++++++
meta/recipes-core/tasks/task-cross-canadian.bb | 1 +
3 files changed, 107 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-core/meta/meta-environment.bb

diff --git a/meta/classes/toolchain-scripts.bbclass b/meta/classes/toolchain-scripts.bbclass
index c393d99..4093635 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -60,3 +60,35 @@ toolchain_create_tree_env_script () {
echo 'export POKY_NATIVE_SYSROOT="${STAGING_DIR_NATIVE}"' >> $script
echo 'export POKY_TARGET_SYSROOT="${STAGING_DIR_TARGET}"' >> $script
}
+
+# This function creates an environment-setup-script for use by the ADT installer
+toolchain_create_sdk_env_script_for_installer () {
+ # Create environment setup script
+ script=${SDK_OUTPUT}/${SDKPATH}/environment-setup-${OLD_MULTIMACH_TARGET_SYS}
+ rm -f $script
+ touch $script
+ echo 'export PATH=${SDKPATHNATIVE}${bindir_nativesdk}:${SDKPATHNATIVE}${bindir_nativesdk}/${OLD_MULTIMACH_TARGET_SYS}:$PATH' >> $script
+ echo 'export PKG_CONFIG_SYSROOT_DIR=##SDKTARGETSYSROOT##' >> $script
+ echo 'export PKG_CONFIG_PATH=##SDKTARGETSYSROOT##${libdir}/pkgconfig' >> $script
+ echo 'export CONFIG_SITE=${SDKPATH}/site-config-${OLD_MULTIMACH_TARGET_SYS}' >> $script
+ echo 'export CC=${TARGET_PREFIX}gcc' >> $script
+ echo 'export CXX=${TARGET_PREFIX}g++' >> $script
+ echo 'export GDB=${TARGET_PREFIX}gdb' >> $script
+ echo 'export TARGET_PREFIX=${TARGET_PREFIX}' >> $script
+ echo 'export CONFIGURE_FLAGS="--target=${TARGET_SYS} --host=${TARGET_SYS} --build=${SDK_ARCH}-linux"' >> $script
+ if [ "${TARGET_OS}" = "darwin8" ]; then
+ echo 'export TARGET_CFLAGS="-I##SDKTARGETSYSROOT##${includedir}"' >> $script
+ echo 'export TARGET_LDFLAGS="-L##SDKTARGETSYSROOT##{libdir}"' >> $script
+ # Workaround darwin toolchain sysroot path problems
+ cd ${SDK_OUTPUT}${SDKTARGETSYSROOT}/usr
+ ln -s /usr/local local
+ fi
+ echo 'export CFLAGS="${TARGET_CC_ARCH} --sysroot=##SDKTARGETSYSROOT##"' >> $script
+ echo 'export CXXFLAGS="${TARGET_CC_ARCH} --sysroot=##SDKTARGETSYSROOT## -I##SDKTARGETSYSROOT##${GXX_INCLUDEDIR}"' >> $script
+ echo "# alias opkg='LD_LIBRARY_PATH=${SDKPATHNATIVE}${libdir_nativesdk} ${SDKPATHNATIVE}${bindir_nativesdk}/opkg-cl -f ${SDKPATHNATIVE}/${sysconfdir}/opkg-sdk.conf -o ${SDKPATHNATIVE}'" >> $script
+ echo "# alias opkg-target='LD_LIBRARY_PATH=${SDKPATHNATIVE}${libdir_nativesdk} ${SDKPATHNATIVE}${bindir_nativesdk}/opkg-cl -f ##SDKTARGETSYSROOT##${sysconfdir}/opkg.conf -o ##SDKTARGETSYSROOT##'" >> $script
+ echo 'export POKY_NATIVE_SYSROOT="${SDKPATHNATIVE}"' >> $script
+ echo 'export POKY_TARGET_SYSROOT="##SDKTARGETSYSROOT##"' >> $script
+ echo 'export POKY_DISTRO_VERSION="${DISTRO_VERSION}"' >> $script
+ echo 'export POKY_SDK_VERSION="${SDK_VERSION}"' >> $script
+}
diff --git a/meta/recipes-core/meta/meta-environment.bb b/meta/recipes-core/meta/meta-environment.bb
new file mode 100644
index 0000000..e8d4a80
--- /dev/null
+++ b/meta/recipes-core/meta/meta-environment.bb
@@ -0,0 +1,74 @@
+DESCRIPTION = "Packge of environment files for SDK"
+LICENSE = "MIT"
+PR = "r0"
+
+inherit meta toolchain-scripts
+
+TRANSLATED_TARGET_ARCH ?= "${TARGET_ARCH}"
+
+EXCLUDE_FROM_WORLD = "1"
+
+SDK_DIR = "${WORKDIR}/sdk"
+SDK_OUTPUT = "${SDK_DIR}/image"
+SDK_DEPLOY = "${TMPDIR}/deploy/sdk"
+
+SDKTARGETSYSROOT = "${SDKPATH}/sysroots/${TARGET_SYS}"
+
+# Save MULTIMACH_TARGET_SYS
+OLD_MULTIMACH_TARGET_SYS := "${MULTIMACH_TARGET_SYS}"
+MULTIMACH_TARGET_SYS = "${MULTIMACH_ARCH}${SDK_VENDOR}-${SDK_OS}"
+
+# Save PACKAGE_ARCH
+OLD_PACKAGE_ARCH := ${BASE_PACKAGE_ARCH}
+BASE_PACKAGE_ARCH = "${SDK_ARCH}-nativesdk"
+
+#change SSTATE_PKGARCH due to the PACKAGE_ARCH change
+SSTATE_PKGARCH = "${SDK_ARCH}"
+
+CONFIG_SITE = "${@siteinfo_get_files(d)}"
+GXX_INCLUDEDIR := "${includedir}/c++"
+
+do_generate_content[nostamp] = "1"
+do_generate_content() {
+
+ rm -rf ${SDK_OUTPUT}
+ mkdir -p ${SDK_OUTPUT}/${SDKPATH}
+
+ siteconfig=${SDK_OUTPUT}/${SDKPATH}/site-config-${OLD_MULTIMACH_TARGET_SYS}
+
+ touch $siteconfig
+ for sitefile in ${CONFIG_SITE} ; do
+ cat $sitefile >> $siteconfig
+ done
+
+ toolchain_create_sdk_env_script_for_installer
+
+ # Add version information
+ versionfile=${SDK_OUTPUT}/${SDKPATH}/version-${OLD_MULTIMACH_TARGET_SYS}
+ touch $versionfile
+ echo 'Distro: ${DISTRO}' >> $versionfile
+ echo 'Distro Version: ${DISTRO_VERSION}' >> $versionfile
+ echo 'Metadata Revision: ${METADATA_REVISION}' >> $versionfile
+ echo 'Timestamp: ${DATETIME}' >> $versionfile
+}
+do_generate_content[recrdeptask] = "do_compile"
+addtask generate_content before do_install after do_compile
+
+do_install[nostamp] = "1"
+do_install() {
+ install -d ${D}/${SDKPATH}
+ install -m 0644 -t ${D}/${SDKPATH} ${SDK_OUTPUT}/${SDKPATH}/*
+}
+
+PN = "meta-environment-${TRANSLATED_TARGET_ARCH}"
+PACKAGES = "${PN}"
+FILES_${PN}= " \
+ ${SDKPATH}/* \
+ "
+
+do_fetch[noexec] = "1"
+do_unpack[noexec] = "1"
+do_patch[noexec] = "1"
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+do_populage_sysroot[noexec] = "1"
diff --git a/meta/recipes-core/tasks/task-cross-canadian.bb b/meta/recipes-core/tasks/task-cross-canadian.bb
index 7170faa..64e53fe 100644
--- a/meta/recipes-core/tasks/task-cross-canadian.bb
+++ b/meta/recipes-core/tasks/task-cross-canadian.bb
@@ -12,5 +12,6 @@ RDEPENDS_${PN} = "\
binutils-cross-canadian-${TRANSLATED_TARGET_ARCH} \
gdb-cross-canadian-${TRANSLATED_TARGET_ARCH} \
gcc-cross-canadian-${TRANSLATED_TARGET_ARCH} \
+ meta-environment-${TRANSLATED_TARGET_ARCH} \
"

--
1.7.0.4


Bug Verify

Yu, Ke <ke.yu@...>
 

Hi,

I hate to raise this question, but there is still bunch of bugs that is fixed but not verified. According to the process, it is reporter's responsibility to verify the bug, so could I ask the reporter's help on this? Process is sometime tedious but helpful to quality assurance. Thanks a lot for your effort.

ID Sev Pri Architecture Reporter Status Resolution Summary
530 nor Med All anna.dushistova@... RESO NOTA Preferences:clicking "restore defaults", then "OK" leads to the error dialog
534 nor Med All anna.dushistova@... RESO FIXE Target dropdown is not updated automatically and contains empty string as default
537 nor Med All anna.dushistova@... RESO NOTA cannot build the "Hello World" Yocto SDK project
527 nor Med x86_ barrett.heyneman@... RESO WONT Partial application of user contributed patch
373 nor Med All bruce.ashfield@... RESO FIXE kernel: allow BSP boostrapping
421 nor Med All bruce.ashfield@... RESO FIXE beagleboard: create a beagle board BSP
422 nor Med All bruce.ashfield@... RESO FIXE routerstation: create initial routerstation pro BSP
423 nor Med All bruce.ashfield@... RESO FIXE fsl-mpc8315e-rdb: create initial BSP
372 nor Und All bruce.ashfield@... RESO FIXE kernel: out of sync trees can cause opaque error messages when forcing branches
399 nor Und All bruce.ashfield@... RESO FIXE defconfig is not automatically included
500 nor Und All bruce.ashfield@... RESO FIXE mpc8315e-rdb: PACKAGE_EXTRA_ARCHS is mismatched
501 nor Und All bruce.ashfield@... RESO FIXE gst-ffmpeg: powerpc build errors
538 nor Med mips changhui.liu@... RESO FIXE Could not display mouse cursor on qemumips
155 maj Med All david.c.stewart@... RESO FIXE Need a 5-minute newbie user guide
96 maj Hig All david.c.stewart@... RESO FIXE References to purple on support page and Poky Handbook
236 nor Low x86 dongxiao.xu@... RESO WONT linux-libc-headers do_install task failed.
313 nor Med All dvhart@... RESO FIXE PDF orphans image captions
315 nor Med All dvhart@... RESO FIXE Additional package requirements
316 nor Med All dvhart@... RESO FIXE QuickStart claims 20 GB of space (I needed 49)
318 nor Med All dvhart@... RESO FIXE QuickStart: /dev/fb0 write permission required
532 nor Med All dvhart@... RESO FIXE INC_PR is not documented
317 nor Med All dvhart@... RESO FIXE Poky Tarball name doesn't match top level directory
582 nor Und All dvhart@... RESO FIXE Cleanup recipes using dead variables
361 nor Low All dvhart@... RESO DUPL 'bitbake -c listtasks' doesn't output to stdout
455 nor Med All edwin.zhai@... RESO FIXE Contacts doesn't work well on RC1 image
458 nor Med x86_ edwin.zhai@... RESO FIXE No shutdown icon on the desktop for qemux86-64 image
525 nor Und All elizabeth.flanagan@... RESO FIXE quilt: configure fails when using patch @ 2.6.1.81-5b68
544 nor Und All gary@... RESO FIXE package-index broken
85 nor Med All gary@... RESO OBSO Kernel modules not built with pstage packages
533 nor Und All gary@... RESO FIXE SSTATE_MIRRORS causes meta tree pollution
351 nor Med All gary@... RESO FIXE Can't build e2fsprogs-native
548 nor Med All gary@... RESO FIXE bitbake listtasks broken
88 nor Hig All gary@... RESO DUPL Which host/cross GDB to use?
554 nor Med All gary@... RESO FIXE Can't build meta-toolchain-sdk as libart-lgpl_2.3.21.bb fails on unpack
269 nor Med All jeff.polk@... RESO FIXE sstate manifests need to be ordered
162 maj Hig All jessica.zhang@... RESO FIXE finalize poky build tree sysroot directory structure
382 nor Med All jessica.zhang@... RESO FIXE oprofile-viewer connect to oprofile-server takes forever for PPC
493 nor Med All jessica.zhang@... RESO FIXE OProfileServer spawning of oprofilectl failure will show through OProfile-viewer
505 nor Med All jessica.zhang@... RESO WONT exit lttv-gui report error
190 enh Med All jessica.zhang@... RESO FIXE Setup update capability for Yocto Linux Eclipse Plug-in
518 nor Und All jessica.zhang@... RESO NOTA poky tree mode meta-ide-support lacking gtk+-2.0 support
129 maj Hig All jessica.zhang@... RESO FIXE Add TCF Remote agent to SDK images
137 nor Med x86 jiajun.xu@... RESO DUPL Icons broken with qemux86 poky-image-sato image
559 nor Und All josh@... RESO WONT Additional comments field should follow existing comments
82 nor Med All josh@... RESO FIXE Dismissing the dialog asking for sudo password breaks interaction
114 nor Med All josh@... RESO WORK Don't touch network interfaces while booting
116 nor Med All josh@... RESO FIXE NFS rootfs
454 nor Und All josh@... RESO FIXE Sanity test for 32bit libraries is incorrect on Ubuntu/Debian 64bit systems
68 nor Hig All josh@... RESO OBSO Use of uppercase characters in matchbox-keyboard doesn't work and results in matchbox-keyboard crashing in N800 image
108 nor Med All josh@... RESO FIXE Possible contention when multiple package outputs enable
254 nor Med All josh@... RESO WONT Should really use GIO
528 nor Med All josh@... RESO FIXE gcc-cross-canadian package names should include the target architecture
113 nor Med All josh@... RESO FIXE udev local rules references parent sysfs directory
121 nor Med All josh@... RESO FIXE undefined users during boot
83 nor Hig All josh@... RESO FIXE Remove experimental status from gdb integration
84 nor Hig All josh@... RESO WORK Deploy action cannot be cancelled
109 nor Hig All josh@... RESO FIXE Rootfs dependency failure does not cause error
122 nor Hig All josh@... RESO DUPL oprofile not being included in SDK images
496 nor Med All ke.yu@... RESO INVA [QT] I18N issue: qtdemo webbrowser can not display Chinese page correctly
475 nor Med x86 kunwei.tian@... RESO NOTA [qemux86]fail to reboot
367 nor Med x86_ kunwei.tian@... RESO NOTA [qemu-x86-64-sato]connection refused when run ssh command
514 nor Med All lei.mei@... RESO FIXE some packages were removed but also exist in distro_tracking_fields.inc
81 maj Med All levant.tinaz@... RESO FIXE SRC_URI with http or ftp path having "/download" at end fails to retrieve source
425 nor Med All lianhao.lu@... RESO FIXE libust is missing in meta-toolchain & meta-toolchain-sdk
556 nor Med ppc lianhao.lu@... RESO DUPL do_unpack failed for libart-lgpl_2.3.21.bb for MACHINE qemuppc
133 nor Med All liping.ke@... RESO FIXE tools (oprofile viewer/client) does not match with tools (oprofile) server
344 maj Hig All liping.ke@... RESO FIXE qemu command is often locked recently because tap0 still exists after successfully shutdown
230 nor Med All liping.ke@... RESO FIXE runqemu scripts break when more than one tun/tap device is created
232 nor Med All liping.ke@... RESO FIXE Give better error prompt when user don't use root privilege to run poky-qemu-ifup
460 enh Med All liping.ke@... RESO OBSO Include qemu images into sdk tar ball
546 nor Med All liping.ke@... RESO DUPL libreadlines clash when installing gdb cross ipk
345 maj Hig All liping.ke@... RESO FIXE rsync is missing in ppc qemu
419 maj Hig All liping.ke@... RESO FIXE Meet internal error when building c++ project sudoku in arm-qemu target
334 nor Med All liping.ke@... RESO FIXE qemu-arm fails whilst building locales (Ubuntu 10.04 )
341 nor Med All liping.ke@... RESO OBSO Two gtk libs are not found (arm)
343 maj Hig All liping.ke@... RESO FIXE unfs-qemu ppc fails to boot
39 nor Hig All manuel.teira@... RESO FIXE oh-puzzles owl menu doesn't show merged menus
70 nor med All manuel.teira@... RESO FIXE epdfview recipe for Poky
360 maj Hig All mark.hatle@... RESO FIXE When switching to the package_deb format, the system errors early
337 nor Med All mark.hatle@... RESO FIXE SUMMARY field is not automatically populated by the DESCRIPTION field
383 nor Med All mark.hatle@... RESO FIXE Log files are generated in the build.py exec_func
331 enh Low All mark.hatle@... RESO FIXE Ensure python output from tasks is always saved to log files
200 maj Und All mark.hatle@... RESO FIXE module-init-tools-cross version 3.12 segfaults in depmod.
240 maj Und All mark.hatle@... RESO FIXE libproxy fails to build on x86_64 host
482 nor Med All mark.hatle@... RESO FIXE syslog startup script is broken
483 nor Med All mark.hatle@... RESO FIXE NFS server initscript does not work
484 nor Med All mark.hatle@... RESO NOTA ps / dbus / hal uid problem
209 maj Hig All mark.hatle@... RESO FIXE prelink-native failures to build, due to missing libiberty from binutils
204 nor Med All mark.hatle@... RESO WORK gdb has apparently host-contamination
245 nor Med All mark.hatle@... RESO FIXE binutils missing the point host directories patch
385 nor Med All mark.hatle@... RESO FIXE python has host system contamination
404 cri Hig x86 mark.hatle@... RESO FIXE RPM segfaults on target
374 maj Hig All mark.hatle@... RESO FIXE binutils and gcc do not have the poison patch enabled
379 nor Med All mark.hatle@... RESO FIXE siteconfig can fail if the directory already exists
381 nor Med All mark.hatle@... RESO FIXE augeas package fails to build if readline is not present
375 enh Med All mark.hatle@... RESO FIXE It can be difficult to find the log files
376 enh Med All mark.hatle@... RESO FIXE Update the insane bbclass to search for bad include and library paths
356 nor Low All mark.hatle@... RESO FIXE upstream rpm location is changing
281 enh Low All mark.hatle@... RESO FIXE Cleanup userspace packages description/summary
403 nor Und All mark.hatle@... RESO FIXE the perform_packagecopy function is mangling file permissions
386 nor Med All mark.hatle@... RESO FIXE qemugl has host system contamination issues
219 nor Low All mark.hatle@... RESO FIXE dpkg does not build properly
34 nor Low x86 matt.hoosier@... RESO WORK String collation failing
292 nor Und All nitin.a.kamble@... RESO DUPL qemu-ppc is failing to execute properly
226 nor Med All nitin.a.kamble@... RESO FIXE qemu binaries break after this commit : 940c2b470af70b40fc6506823cd9c43e9b621075
214 nor Und arm nitin.a.kamble@... RESO FIXE oprofile recipe is failing to build on arm
218 nor Hig All nitin.a.kamble@... RESO FIXE qemu-native does not generate qemu-i386 binary
305 nor Med All nitin.a.kamble@... RESO FIXE qemu-native does not provide qemu-mipsel binary
53 nor Hig All pmiscml@... RESO FIXE psplash: Do correct math when centering logo
275 nor Low All pokybugbot@... RESO NOTA Bug Process Test Bug One
487 maj Hig All qing.he@... RESO FIXE fg/bg of bash not available
350 enh Med All Richard.Purdie@... RESO FIXE Clean up poky-doc-tools
400 nor Und All Richard.Purdie@... RESO FIXE qt4-tools-native compile failure
285 enh Low All Richard.Purdie@... RESO FIXE Improve overlay appending to FILESPATH syntax
217 nor Und ppc Richard.Purdie@... RESO FIXE prelink is failing at do_rootfs time for the qemuppc machine
123 nor Med All Richard.Purdie@... RESO FIXE Wrong qemu binary is used if qemu-native isn't built
221 enh Und All Richard.Purdie@... RESO FIXE opkg should use /var/lib/opkg, not /usr/lib/opkg
389 nor Med All scott.a.garman@... RESO FIXE Use a more common lockfile utility for poky's qemu scripts
391 nor Med All scott.a.garman@... RESO FIXE Create a script to generate a "bank" of tap devices for Poky QEMU sessions to use
392 nor Med All scott.a.garman@... RESO FIXE Add psuedo-native, qemu-helper-native, and unfs-server-native to qemu-native DEPENDS
393 nor Med All scott.a.garman@... RESO FIXE Allow running of multiple QEMU nfs instances
415 nor Med All scott.a.garman@... RESO FIXE poky-qemu does not accept a ROOTFS argument of poky-image-xyz
535 nor Med All scott.a.garman@... RESO FIXE poky-qemu does not detect MACHINE correctly from yocto 0.9 release images
536 nor Med All scott.a.garman@... RESO FIXE SDK install of poky-qemu will not run with yocto 0.9 release images unless filesystem type is explicitly given
568 nor Med All scott.a.garman@... RESO FIXE poky-qemu fails under common usage scenario
294 nor Low All scott.a.garman@... RESO FIXE runqemu script can fail to shut down tap devices
104 cri Hig All susie.li@... RESO FIXE Yocto Linux 0.9 feature list need be updated
396 nor Hig All tom.zanussi@... RESO FIXE Make linux-wrs the default kernel for emenlow
311 nor Med x86 tom.zanussi@... RESO FIXE fixes for perf
450 nor Med All tom.zanussi@... RESO FIXE [atom-pc] Undefined video mode message on boot
451 nor Med All tom.zanussi@... RESO NOTA poky-image-sdk-live-emenlow 'install' fails with nonsensical partition size
531 nor Med All tom_rini@... RESO FIXE 'rm_work' is run much later than expected, when INHERIT'ed
575 nor Med arm wd@... RESO DUPL mtd-utils_1.4.1 fails to build
473 nor Med All xianchao.zhang@... RESO DUPL shared libraries libtasn1.so loading error
359 nor Low x86 xianchao.zhang@... RESO INVA Some icons broken in qemux86 images
552 nor Med othe xianchao.zhang@... RESO FIXE autobuild missing the non-x86 realboard images
215 nor Low All yosoy@... RESO FIXE netbase 4.41 not available in Debian mirrors

Regards
Ke


Bug Scrub Result

Yu, Ke <ke.yu@...>
 

Hi distro team,

Saul, Jessica and I have a triage bug meeting to scrub the bugs, and here is the bug list ahead of us. Let's spent some time to reduce the bug number. Thanks for the great effort.

412 nor Med All dexuan.cui@... ACCE --- lttv can't be loaded in GUI mode
417 nor Med ppc dexuan.cui@... ACCE --- gcc compile in sdk image failed with qemuppc
555 nor Med All dexuan.cui@... NEW --- After untar sdk tarball to /opt/poky, My root folder's user info is changed!
239 enh Med All dexuan.cui@... NEW --- Toolchain bootstrapping process overwrites files in the sysroot
506 nor Med All dongxiao.xu@... ACCE --- connman-gnome installs a duplicate desktop file
110 nor Med All edwin.zhai@... ACCE --- Fix sato Gtk+ patches so we can upgrade to a recent gtk+ for DISTRO=poky
456 nor Med x86 edwin.zhai@... NEW --- matchbox desktop icons crash
509 nor Med All edwin.zhai@... NEW --- Xorg and matchbox-window will SegFault when there are too many windows
570 nor Med All edwin.zhai@... NEW --- LSB: Desktop Test
571 nor Med All edwin.zhai@... NEW --- LSB: Desktop-T2C Tests
488 enh Med All edwin.zhai@... NEW --- No audio on qemux86 machine
512 maj Med arm ke.yu@... NEW --- Very slow response after login the system on arm real hardware board
196 nor Med All ke.yu@... ACCE --- [All] No option to download file or set proxy via web browser in poky
336 nor Med x86 ke.yu@... NEW --- [QT] fotowall display abnormal on eMenlow
524 nor Med All ke.yu@... NEW --- Crazy Qt packaging
452 enh Med All ke.yu@... ACCE --- [Qt] qtdemo warning: missing Qt database driver
567 nor Med All ke.yu@... NEW --- LSB: Desktop Test - desktop-cairo
569 nor Med All ke.yu@... NEW --- LSB: Desktop Test - desktop-qt4
573 nor Med All ke.yu@... NEW --- http fetcher cannot handle ';' in the url
355 enh Med All ke.yu@... NEW --- Refactor fetch's go() method
529 nor Med All ke.yu@... NEW --- fetcher failback fails if trying to access CVS archive and not able to connect
480 nor Med All kevin.tian@... NEW --- soft lockup warnings pop up after idle for a while
485 nor Med arm kevin.tian@... NEW --- Some ltp test cases cause blocking
572 maj Hig ppc nitin.a.kamble@... NEW --- elfutils-native-0.148 build fails: ./ld: unrecognized option '--no-add-needed'
384 nor Med All nitin.a.kamble@... NEW --- perl has host system contamination
402 nor Med All nitin.a.kamble@... NEW --- Parallel build failures for gcc-cross-intermediate-4.5.0-r10
550 nor Med arm nitin.a.kamble@... NEW --- two machines armv4t and armv5te, toolchain problem.
574 nor Med ppc nitin.a.kamble@... NEW --- PPC: poky-image-sdk: gcc misses register save/restore routines
516 enh Med All nitin.a.kamble@... NEW --- Change Dynamic Shared Object (DSO) linking to be explicit
443 maj Hig ppc qing.he@... ACCE --- zypper encounter segfault when startup with qemuppc
280 nor Med All qing.he@... ACCE --- [QT] fail to start fotowall on qemux86-64
348 nor Med All qing.he@... ACCE --- [QT] fotowall segfaults with "Painter not active"
489 nor Med arm qing.he@... NEW --- [zypper] uname -m and repo arch difference
490 nor Med arm qing.he@... NEW --- [zypper] installation failure on arm
491 nor Med All qing.he@... ACCE --- [zypper] package removal failure
541 nor Med arm qing.he@... NEW --- On poky laverne-4.0, poky-image-sato for the igep0020 does not start X
547 nor Med All qing.he@... ACCE --- libmpfr4 clash when installing gdb cross ipk
439 nor Med x86 saul.wold@... NEW --- audio mixer on BlackSand is muted on boot
414 maj Hig ppc scott.a.garman@... ACCE --- [PPC] kernel panic when booting poky-image-sdk-qemuppc of nightly build 20101007-1 through UNFS
154 nor Med All scott.a.garman@... NEED --- libtool has incorrect paths embedded
378 nor Med All scott.a.garman@... ACCE --- Add openssh to task-poky-lsb
580 nor Med All scott.a.garman@... ACCE --- poky-qemu does not make proper use of CROSSPATH (breaking distcc)
353 enh Med All scott.a.garman@... ACCE --- Add libtool 2.4 sysroot support and remove libtool hacks/workarounds

Regards
Ke


Re: version problems about SDK

Zhang, Jessica
 

Tian, Kevin wrote:
From: Ke, Liping
Sent: Monday, December 13, 2010 2:53 PM

Hi, Jessica & Josh

When we are trying to run installer script on lianhao's x86_64
machine, we found if the images are build in two days, according to
current version naming convention, some of the packages will be
installed to /opt/poky/0.9+snapshot-20101210, some will be to
/opt/poky/0.9+snapshot-20101210.
It will cause problem since we need to know the exact version number
before installing and searching some files (environment script file,
etc). And the same releases of packages belong to different version
(just the build date is not in the same day) seems very strange and
hard to handle for us?
I think Josh has laid down the base for multiple version SDK support.
The only problem is:

SDKPATH = "/opt/${DISTRO}/${DISTRO_VERSION}"

which obviously is not what we want. We need a similar variable like
SDK_VERSION, which is incremented only when SDK team thinks there's a
need for a new version release or
else it keeps same in the life cycle of current version.

Liping, could you try to come up a new variable for your purpose?
As Kevin mentioned, can we derive SDK_VERSION from DISTRO_VERSION so only
contains 0.9?

Thanks
Kevin


Try latest yocto adt script installer

Ke, Liping <liping.ke@...>
 

Hi, Jessica

I have put the installer script tar ball in the below links: http://llu-piketon.sh.intel.com/installer.tar

You can have a try. Below is some key notes:

1. since now version has problems, we have submit bug 586 http://bugzilla.pokylinux.org/show_bug.cgi?id=586
So currently we have no available x86_64 repository. (same packages now belong to different version because they are built in two days). So currently only 32 bit host could run the script
2. after untar this installer, under adt_installer folder, directly running $ ./yocto_installer.
3. Build log are located @ adt_installer/yoctoadt_installer.log
4. User config ( install which targets) are defined/changed in Yocto_installer.conf. Note: now only i586 qemu rootfs are available in repository.

Any problem, just let me know.


Thanks& Regards,
criping


Re: version problems about SDK

Tian, Kevin <kevin.tian@...>
 

From: Ke, Liping
Sent: Monday, December 13, 2010 2:53 PM

Hi, Jessica & Josh

When we are trying to run installer script on lianhao's x86_64 machine, we found if the
images are build in two days, according to current version naming convention, some of the
packages will be installed to /opt/poky/0.9+snapshot-20101210, some will be to
/opt/poky/0.9+snapshot-20101210.
It will cause problem since we need to know the exact version number before installing and
searching some files (environment script file, etc). And the same releases of packages
belong to different version (just the build date is not in the same day) seems very strange
and hard to handle for us?
I think Josh has laid down the base for multiple version SDK support. The only problem is:

SDKPATH = "/opt/${DISTRO}/${DISTRO_VERSION}"

which obviously is not what we want. We need a similar variable like SDK_VERSION, which
is incremented only when SDK team thinks there's a need for a new version release or
else it keeps same in the life cycle of current version.

Liping, could you try to come up a new variable for your purpose?

Thanks
Kevin


version problems about SDK

Ke, Liping <liping.ke@...>
 

Hi, Jessica & Josh

When we are trying to run installer script on lianhao's x86_64 machine, we found if the images are build in two days, according to current version naming convention, some of the packages will be installed to /opt/poky/0.9+snapshot-20101210, some will be to /opt/poky/0.9+snapshot-20101210.
It will cause problem since we need to know the exact version number before installing and searching some files (environment script file, etc). And the same releases of packages belong to different version (just the build date is not in the same day) seems very strange and hard to handle for us?

Thanks& Regards,
criping