Date   

Re: LIC_FILES_CHKSUM issue

Richard Purdie <rpurdie@...>
 

On Sun, 2010-12-05 at 20:44 +0000, Richard Purdie wrote:
On Sun, 2010-12-05 at 00:22 +0100, Frans Meulenbroeks wrote:
Hi,

I was porting a recipe from OE to yocto and bumped into a
LIC_FILES_CHKSUM error.
I get a message about LIC_FILES_CHKSUM

Checked the ref man
(http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-specifying-LIC_FILES_CHKSUM)
added this:
LIC_FILES_CHKSUM = "file://COPYING; md5=xxxx"
in the hope to get the checksum.
However I don't get one, so I run md5sum on the COPYING file myself
and replace xxxx with that value.

No success though, I still get:

| NOTE: Checking autotools environment for common misconfiguration
| FATAL: Gettext required but not in DEPENDS for file
/home/frans/poky/poky/build/tmp/work/armv5te-poky-linux-gnueabi/libcddb-1.3.2-r0/libcddb-1.3.2/configure.ac.
| Missing inherit gettext?
| ERROR: Error in executing python function in:
/home/frans/poky/poky/meta-private/recipes/libcddb/libcddb_1.3.2.bb
Let me just cut your error down to the above. Its saying you need to add
gettext to DEPENDS.

The rest of the python traceback looks corrupt and is just confusing the
issue.

We have some things in planned in Poky to start trying to address error
handling and making it easier to work out whats wrong.
Its not the complete solution but I thought the traceback you saw was
very confusing. The same error now would give:

| NOTE: Checking autotools environment for common misconfiguration
| FATAL: Gettext required but not in DEPENDS for file /media/data1/builds/poky2/tmp/work/i586-poky-linux/coreutils-8.5-r0/coreutils-8.5/configure.ac.
| Missing inherit gettext?
| ERROR: There was an error when executing a python function in: /rphome/poky/meta/recipes-core/coreutils/coreutils_8.5.bb
| ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
| ERROR: The stack trace of python calls that resulted in thie exception/failure was:
| ERROR: File "do_qa_configure", line 36, in <module>
| ERROR:
| ERROR: File "do_qa_configure", line 31, in do_qa_configure
| ERROR:
| ERROR: File "/rphome/poky/scripts/..//bitbake/lib/bb/__init__.py", line 56, in fatal
| ERROR: bb.msg.fatal(None, ''.join(args))
| ERROR:
| ERROR: File "/rphome/poky/scripts/..//bitbake/lib/bb/msg.py", line 139, in fatal
| ERROR: sys.exit(1)
| ERROR:
| ERROR: The code that was being executed was:
| ERROR: 0032:
| ERROR: 0033: if not package_qa_check_license(workdir, d):
| ERROR: 0034: bb.fatal("Licensing warning: LIC_FILES_CHKSUM does not match, please fix")
| ERROR: 0035:
| ERROR: *** 0036:do_qa_configure(d)
| ERROR: (file: 'do_qa_configure', lineno: 36, function: <module>)
| ERROR: 0027: for config in configs:
| ERROR: 0028: gnu = "grep \"^[[:space:]]*AM_GNU_GETTEXT\" %s >/dev/null" % config
| ERROR: 0029: if os.system(gnu) == 0:
| ERROR: 0030: bb.fatal("""Gettext required but not in DEPENDS for file %s.
| ERROR: *** 0031:Missing inherit gettext?""" % config)
| ERROR: 0032:
| ERROR: 0033: if not package_qa_check_license(workdir, d):
| ERROR: 0034: bb.fatal("Licensing warning: LIC_FILES_CHKSUM does not match, please fix")
| ERROR: 0035:
| ERROR: (file: 'do_qa_configure', lineno: 31, function: do_qa_configure)
| ERROR: Task failed: ('Function do_qa_configure failed', '/media/data1/builds/poky2/tmp/work/i586-poky-linux/coreutils-8.5-r0/temp/log.do_configure.22891')
NOTE: package coreutils-8.5-r0: task do_configure: Failed

which is I hope slightly clearer and has the bug fixed where it wasn't
showing the line that actually failed if it was the last line (line 36).

In future I'd not like this to show a traceback at all if a sensible
error has been given to a user as in this case but at least this makes
the tracebacks more usable.

Cheers,

Richard


Re: LIC_FILES_CHKSUM issue

Richard Purdie <rpurdie@...>
 

On Sun, 2010-12-05 at 00:22 +0100, Frans Meulenbroeks wrote:
Hi,

I was porting a recipe from OE to yocto and bumped into a
LIC_FILES_CHKSUM error.
I get a message about LIC_FILES_CHKSUM

Checked the ref man
(http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-specifying-LIC_FILES_CHKSUM)
added this:
LIC_FILES_CHKSUM = "file://COPYING; md5=xxxx"
in the hope to get the checksum.
However I don't get one, so I run md5sum on the COPYING file myself
and replace xxxx with that value.

No success though, I still get:

| NOTE: Checking autotools environment for common misconfiguration
| FATAL: Gettext required but not in DEPENDS for file
/home/frans/poky/poky/build/tmp/work/armv5te-poky-linux-gnueabi/libcddb-1.3.2-r0/libcddb-1.3.2/configure.ac.
| Missing inherit gettext?
| ERROR: Error in executing python function in:
/home/frans/poky/poky/meta-private/recipes/libcddb/libcddb_1.3.2.bb
Let me just cut your error down to the above. Its saying you need to add
gettext to DEPENDS.

The rest of the python traceback looks corrupt and is just confusing the
issue.

We have some things in planned in Poky to start trying to address error
handling and making it easier to work out whats wrong.

Cheers,

Richard


Re: AUTOTOOLS_STAGE_PKGCONFIG still used?

Richard Purdie <rpurdie@...>
 

On Sun, 2010-12-05 at 00:31 +0100, Frans Meulenbroeks wrote:
Is AUTOTOOLS_STAGE_PKGCONFIG still of any use?
No, it used to do something but hasn't for over a year in either OE or
Poky.

I was trying to fidn out what I did, I ran a grep on both my
openembedded dir (results see below) and my yocto tree, both trees at
git head.
I see a lot of places where it is set but no place where it is used.

Anyone who can confirm that this is a stale var? Or otherwise anyone
who can explain how this is used. (and no, bitbake does not know the
var either, not that I had expected it)
Its not needed and can be removed. I've pushed a patch to poky removing
the references and acked your patch for OE.

Cheers,

Richard


AUTOTOOLS_STAGE_PKGCONFIG still used?

Frans Meulenbroeks <fransmeulenbroeks@...>
 

Dear all.

Is AUTOTOOLS_STAGE_PKGCONFIG still of any use?
I was trying to fidn out what I did, I ran a grep on both my
openembedded dir (results see below) and my yocto tree, both trees at
git head.
I see a lot of places where it is set but no place where it is used.

Anyone who can confirm that this is a stale var? Or otherwise anyone
who can explain how this is used. (and no, bitbake does not know the
var either, not that I had expected it)

frans@linux-suse:~/oe/openembedded> grep -r AUTOTOOLS_STAGE_PKGCONFIG .
./recipes/gnome/libsoup_2.2.100.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/gnome/gnome-python-extras_2.25.3.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/gnome/hippo-canvas_0.3.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/openmax/libomxil-bellagio_0.9.2.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/openmax/libomxil-bellagio_0.9.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/openmax/libomxil-bellagio_0.9.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/openmax/libomxil-bellagio_0.9.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/musicpd/libmpd_0.17.96.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/musicpd/libmpd_0.20.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/libexif/libexif.inc:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/obsolete/pixman/pixman_0.17.6.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/mml-widget/gtkmathview_0.8.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = 1
./recipes/ggz/libggz_0.0.14.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/vlc/libdvdcss_1.2.10.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/gnutls/libtasn1_1.7.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/gstreamer/gst-common.inc:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/mythtv/gmyth_0.7.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/mythtv/gmyth-upnp_0.7.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/lcms/lcms_1.17.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/jpeg/jasper_1.900.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/redland/redland_1.0.8.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/telepathy/telepathy-gabble_0.7.27.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/telepathy/telepathy-farsight_0.0.7.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/telepathy/telepathy-mission-control_4.67.bb:AUTOTOOLS_STAGE_PKGCONFIG
= "1"
./recipes/telepathy/telepathy-glib_0.7.29.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/kde4/gmm_3.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/kde4/kde4.inc:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/kde4/strigi_0.5.10.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/device-mapper/device-mapper_1.02.28.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sdr/hamlib_1.2.10.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/libusb/libusb-compat_0.1.3.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/libusb/libusb-compat_0.1.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/libusb/libusb1_1.0.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/bluez/bluez4-libs.inc:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/bluez/bluez4.inc:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/boxee/tre_0.7.5.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/fann/fann_2.0.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/pango/pangomm_2.26.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/icon-slicer/icon-slicer-native_0.3.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar_0.83.4.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-datastore_0.82.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-artwork_0.84.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-toolkit_0.82.11.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-datastore_0.84.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-base_0.82.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-artwork_0.82.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar_0.82.9.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-toolkit_0.84.4.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-toolkit_0.83.3.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-presence-service_0.82.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-base_0.84.1.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-presence-service_0.84.0.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar_0.84.6.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/sugar/sugar-base_0.83.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/schroedinger/schroedinger_1.0.9.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/devicekit/devicekit-disks_004.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/upnp/gupnp-av_0.2.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/upnp/libupnp_1.6.5.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/libdlo/libdlo_git.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/obexftp/obexftp_0.23.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/pulseaudio/libcanberra_0.17.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/pulseaudio/libcanberra_0.14.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/pulseaudio/libcanberra_0.12.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/farsight/farsight2_0.0.9.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/farsight/libnice_0.0.13.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/farsight/farsight2_0.0.22.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./recipes/farsight/libnice_0.0.6.bb:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./classes/xfce.bbclass:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./classes/gnomebase.bbclass:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./classes/xfce46.bbclass:AUTOTOOLS_STAGE_PKGCONFIG = "1"
./classes/efl.bbclass:AUTOTOOLS_STAGE_PKGCONFIG = "1"
frans@linux-suse:~/oe/openembedded>


LIC_FILES_CHKSUM issue

Frans Meulenbroeks <fransmeulenbroeks@...>
 

Hi,

I was porting a recipe from OE to yocto and bumped into a
LIC_FILES_CHKSUM error.
I get a message about LIC_FILES_CHKSUM

Checked the ref man
(http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-specifying-LIC_FILES_CHKSUM)
added this:
LIC_FILES_CHKSUM = "file://COPYING; md5=xxxx"
in the hope to get the checksum.
However I don't get one, so I run md5sum on the COPYING file myself
and replace xxxx with that value.

No success though, I still get:

| NOTE: Checking autotools environment for common misconfiguration
| FATAL: Gettext required but not in DEPENDS for file
/home/frans/poky/poky/build/tmp/work/armv5te-poky-linux-gnueabi/libcddb-1.3.2-r0/libcddb-1.3.2/configure.ac.
| Missing inherit gettext?
| ERROR: Error in executing python function in:
/home/frans/poky/poky/meta-private/recipes/libcddb/libcddb_1.3.2.bb
| ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
| ERROR: Traceback:
| ERROR: File "do_qa_configure", line 36, in <module>
| ERROR:
| ERROR: File "do_qa_configure", line 31, in do_qa_configure
| ERROR:
| ERROR: File
"/home/frans/poky/poky/scripts/..//bitbake/lib/bb/__init__.py", line
56, in fatal
| ERROR: bb.msg.fatal(None, ''.join(args))
| ERROR:
| ERROR: File
"/home/frans/poky/poky/scripts/..//bitbake/lib/bb/msg.py", line 139,
in fatal
| ERROR: sys.exit(1)
| ERROR:
| ERROR: The lines leading to this error were:
| ERROR: 0032:
| ERROR: 0033: if not package_qa_check_license(workdir, d):
| ERROR: 0034: bb.fatal("Licensing warning: LIC_FILES_CHKSUM
does not match, please fix")
| ERROR: 0035:
| ERROR: Task failed: ('Function do_qa_configure failed',
'/home/frans/poky/poky/build/tmp/work/armv5te-poky-linux-gnueabi/libcddb-1.3.2-r0/temp/log.do_configure.12827')
NOTE: package libcddb-1.3.2-r0: task do_configure: Failed

No idea on how to resolve this.

Frans


Re: [beagleboard] Yocto

Xianghua Xiao <xiaoxianghua@...>
 

On Fri, Dec 3, 2010 at 1:15 PM, Bruce Ashfield
<bruce.ashfield@...> wrote:
On 10-12-03 02:11 PM, Xianghua Xiao wrote:

On Fri, Dec 3, 2010 at 12:46 PM, Petr Štetiar<ynezz@...>  wrote:

Michael J. Hammel<mjhammel@...>  [2010-12-03 11:01:27]:

Hi,

I've heard of Yocto only in passing.  I'm assuming it's another
bitbake-based metabuild system?  Is there some reasoning why
Meego/Linaro/OpenEmbedded/Angstrom/Custom Builds cannot fill the
requirements of Yocto?  I don't mean that harshly at all - I'm just
curious about the evolution and true target audiences of these projects.
It's nice to have choices, but developers should have some idea of the
differences so they can choose wisely when just starting.
Richard wrote nice summary[1], it's worth reading and it might answer
your
questions as well :-)

1.
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-November/026598.html

-- ynezz

--
You received this message because you are subscribed to the Google Groups
"Beagle Board" group.
To post to this group, send email to beagleboard@....
To unsubscribe from this group, send email to
beagleboard+unsubscribe@....
For more options, visit this group at
http://groups.google.com/group/beagleboard?hl=en.

May we know roughly how many paid resources are behind Yocto?

Which arch will be first officially supported? Will it be ATOM as Poky
is really part of Intel? Beagle/ARM will be done by the community
instead?
I can provide some answers for this part of the query.

In the 0.9 release, we already support the following arches:

 - x86(64), mips, arm and powerpc

These are all based on a 2.6.34 kernel base (with an option
for 2.6.37-rcX shortly). There are simulated targets for
each arch, and a hardware reference for each as well
(for ARM the reference hardware is the beagleboard).

Hope that helps,

Bruce


Thanks,
Xianghua
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Will try it on my beagle.
I failed to find info on other hardware reference platform. And I
found 0.9 has an ATOM download as
well(http://autobuilder.yoctoproject.org/downloads/yocto-0.9/).

Additionally, http://autobuilder.pokylinux.org:8010/ is not working.

Thanks,
Xianghua


Re: [beagleboard] Yocto

Bruce Ashfield <bruce.ashfield@...>
 

On 10-12-03 02:11 PM, Xianghua Xiao wrote:
On Fri, Dec 3, 2010 at 12:46 PM, Petr Štetiar<ynezz@...> wrote:
Michael J. Hammel<mjhammel@...> [2010-12-03 11:01:27]:

Hi,

I've heard of Yocto only in passing. I'm assuming it's another
bitbake-based metabuild system? Is there some reasoning why
Meego/Linaro/OpenEmbedded/Angstrom/Custom Builds cannot fill the
requirements of Yocto? I don't mean that harshly at all - I'm just
curious about the evolution and true target audiences of these projects.
It's nice to have choices, but developers should have some idea of the
differences so they can choose wisely when just starting.
Richard wrote nice summary[1], it's worth reading and it might answer your
questions as well :-)

1. http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-November/026598.html

-- ynezz

--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagleboard@....
To unsubscribe from this group, send email to beagleboard+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

May we know roughly how many paid resources are behind Yocto?

Which arch will be first officially supported? Will it be ATOM as Poky
is really part of Intel? Beagle/ARM will be done by the community
instead?
I can provide some answers for this part of the query.

In the 0.9 release, we already support the following arches:

- x86(64), mips, arm and powerpc

These are all based on a 2.6.34 kernel base (with an option
for 2.6.37-rcX shortly). There are simulated targets for
each arch, and a hardware reference for each as well
(for ARM the reference hardware is the beagleboard).

Hope that helps,

Bruce


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


Re: [beagleboard] Yocto

Xianghua Xiao <xiaoxianghua@...>
 

On Fri, Dec 3, 2010 at 12:46 PM, Petr Štetiar <ynezz@...> wrote:
Michael J. Hammel <mjhammel@...> [2010-12-03 11:01:27]:

Hi,

I've heard of Yocto only in passing.  I'm assuming it's another
bitbake-based metabuild system?  Is there some reasoning why
Meego/Linaro/OpenEmbedded/Angstrom/Custom Builds cannot fill the
requirements of Yocto?  I don't mean that harshly at all - I'm just
curious about the evolution and true target audiences of these projects.
It's nice to have choices, but developers should have some idea of the
differences so they can choose wisely when just starting.
Richard wrote nice summary[1], it's worth reading and it might answer your
questions as well :-)

1. http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-November/026598.html

-- ynezz

--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagleboard@....
To unsubscribe from this group, send email to beagleboard+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

May we know roughly how many paid resources are behind Yocto?

Which arch will be first officially supported? Will it be ATOM as Poky
is really part of Intel? Beagle/ARM will be done by the community
instead?

Thanks,
Xianghua


Re: yocto_installer test script update

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

Hi, Jessica

Since I got a high fever yesterday so did not come to office in the morning...

Please see my reply below...

Thanks& Regards,
criping

-----Original Message-----
From: Zhang, Jessica
Sent: Friday, December 03, 2010 8:23 AM
To: Ke, Liping; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: RE: yocto_installer test script update

Liping,

I ran into error right away, and it's a very valid situation that we
need to be able to handle. So in the terminal that I test the
installer, I happened to already have /opt/poky and source the
environment-setup-i586 script which alter all my host sysroot to be
under /opt/poky/sysroot/i586-pokysdk-linux/,
etc...which triggered your opkg autotool project configure failed,
please see the attached config.log file for details.
I can detect whether some configurations are set in the environment, but such detection is something like a hack. If user like to set some CC, CFLAGS, seems we need not bother with it. This is the common case of failure. Eg: for normal project in open source world, make/make install is the normal installation process. We will meet the same error. Seems nobody will deal with it. But if you like, I will add a guard to detect the settings of specific environment setup. But Lianhao said such detection is strange.


Also, yesterday, I spent quite some time re-wrote lots of prompt
messages in the yocto_main, can you merge them into the new code?
No problem

In the installation terminal I saw the following prompt:
Check User Configuration For Arch Type x86
Check User Configuration For Arch Type arm
Check User Configuration For Arch Type powerpc
Check User Configuration For Arch Type mips
Check architecture type x86 whether it needs to download images
Check architecture type arm whether it needs to download images
Check architecture type powerpc whether it needs to download
images
Check architecture type mips whether it needs to download images
Do you want to go on installing, please enter Y/N:Y

Beginning installation process...

Begin to install selected native ADT!
make dir ///var/lib/opkg successfully!
Downloading http://llu-piketon.sh.intel.com/ipk_sdk/Packages.
Downloading http://llu-piketon.sh.intel.com/ipk_sdk/all/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-nativesdk/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-i586-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-arm-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-powerpc-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-mips-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-x86_64-canadian/Packages.

And by looking at your yocto_config file, which as following Host Area
YOCTOADT_TARGETS="powerpc"
YOCTOADT_QEMU="Y"
YOCTOADT_NFS_UTIL="Y"
YOCTOADT_BITBAKE="Y"
YOCTOADT_METADATA="Y"

#Target Area
YOCTOADT_TARGET_arm="N"
YOCTOADT_ROOTFS_arm="sato sdk"
YOCTOADT_TARGET_SYSROOT_IMAGE_arm="sato"
YOCTOADT_TARGET_SYSROOT_arm="$HOME/test-yocto/arm"

YOCTOADT_TARGET_x86="Y"
YOCTOADT_ROOTFS_x86="sdk minimal"
YOCTOADT_TARGET_SYSROOT_IMAGE_x86="sdk"
YOCTOADT_TARGET_SYSROOT_x86="$HOME/test-yocto/x86"

YOCTOADT_TARGET_powerpc="N"
YOCTOADT_ROOTFS_powerpc="sdk sato minimal"
YOCTOADT_TARGET_SYSROOT_IMAGE_powerpc="minimal"
YOCTOADT_TARGET_SYSROOT_powerpc="$HOME/test-yocto/mips"

YOCTOADT_TARGET_mips="N"
YOCTOADT_ROOTFS_mips="sdk"
YOCTOADT_TARGET_SYSROOT_IMAGE_mips="sdk"
YOCTOADT_TARGET_SYSROOT_mips="$HOME/test-yocto/mips"

Questions/comments
1. I'm assuming the "Check user configuration" and "Check architecture
type"
messages are just for debugging and the in the final code they'll be
gone right?
Yes. The code is not finished yet. It needs further processing.


2. Why I'm seeing so many downloading for all the cross-canadian for
all arches? According to your configure file, shouldn't just i586-
powerpc-canadian? Also, don't know where the "Downloading http://..."
message from, are they from the opkg install?
Yes. This information is given by opkg update. It's package information.
When updating, it will fetch all those available repository information.
It has nothing to do with opkg install powerpc related materials.


Thanks,
Jessica
Ke, Liping wrote:
Hi, Jessica
I have update the installer on http://llu-piketon.sh.intel.com/. I
have tested in your machine roughly, downloading should work if you
use wget -Y off to turn off all your proxy settings for testing.
Since there're dangling folders in your machine, I can't rudely
delete it. You can download the new package and test.

There're some other prompt problems I need to adjust. Today is not
the
final code, only for your reviewing and testing.

Any problem, just let me know.

Thanks& Regards,
criping



-----Original Message-----
From: Zhang, Jessica
Sent: Thursday, December 02, 2010 8:19 AM
To: Ke, Liping; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: RE: yocto_installer test script update

Liping,

I've modified couple files mainly for the messaging, styling, etc.
Also, globaly changed SDK to ADT (Application Development Tools,
which is the new name that came out refering to the toolchains,
etc.). Please see attachment.

Other comments:
1. I'd expect after your do the code clean up, the code logic flow
should be more clearer, now the functions and main installation
code
are mingled together 2. There're couple places that I commented off
with my initial JZ which I don't think there're the needs for the
code, we can walk through them tonight...
3. For target sysroot setup, I'd expect similar prompt to the user
about the specified configuration and confirmation 4. Also for
target
sysroot setup, in the yocto_config file, you specify
ROOTFS_powerpc="sdk" TARGET_SYSROOT_IMAGE_powerpc="sato"
I'd expect the installer will run into error since the download
images only contain SDK no sato, sysroot can't be setup using sato,
which I think it's missing from the current code...

In general it looks good and main flow that needs to be covered are
there...

Thanks,
Jessica


-----Original Message-----
From: Ke, Liping
Sent: Wednesday, December 01, 2010 2:06 AM
To: Zhang, Jessica; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: yocto_installer test script update

Hi, Jessica

The newer version of the installer is in lianhao's location. You can
directly run ./yocto_installer http://llu-piketon.sh.intel.com/
Today
we tested both on 32 bit and 64 bit ubuntu host.

It's very initial and rough, I will move many non-root required ops
into the outer wrapper script later.

Any early comments are welcomed, just let me know.

Thanks& Regards,
criping


Re: yocto_installer test script update

Zhang, Jessica
 

Liping,

I ran into error right away, and it's a very valid situation that we need to
be able to handle. So in the terminal that I test the installer, I happened
to already have /opt/poky and source the environment-setup-i586 script which
alter all my host sysroot to be under /opt/poky/sysroot/i586-pokysdk-linux/,
etc...which triggered your opkg autotool project configure failed, please
see the attached config.log file for details.

Also, yesterday, I spent quite some time re-wrote lots of prompt messages in
the yocto_main, can you merge them into the new code?

In the installation terminal I saw the following prompt:
Check User Configuration For Arch Type x86
Check User Configuration For Arch Type arm
Check User Configuration For Arch Type powerpc
Check User Configuration For Arch Type mips
Check architecture type x86 whether it needs to download images
Check architecture type arm whether it needs to download images
Check architecture type powerpc whether it needs to download images
Check architecture type mips whether it needs to download images
Do you want to go on installing, please enter Y/N:Y

Beginning installation process...

Begin to install selected native ADT!
make dir ///var/lib/opkg successfully!
Downloading http://llu-piketon.sh.intel.com/ipk_sdk/Packages.
Downloading http://llu-piketon.sh.intel.com/ipk_sdk/all/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-nativesdk/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-i586-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-arm-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-powerpc-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-mips-canadian/Packages.
Downloading
http://llu-piketon.sh.intel.com/ipk_sdk/i586-x86_64-canadian/Packages.

And by looking at your yocto_config file, which as following
Host Area
YOCTOADT_TARGETS="powerpc"
YOCTOADT_QEMU="Y"
YOCTOADT_NFS_UTIL="Y"
YOCTOADT_BITBAKE="Y"
YOCTOADT_METADATA="Y"

#Target Area
YOCTOADT_TARGET_arm="N"
YOCTOADT_ROOTFS_arm="sato sdk"
YOCTOADT_TARGET_SYSROOT_IMAGE_arm="sato"
YOCTOADT_TARGET_SYSROOT_arm="$HOME/test-yocto/arm"

YOCTOADT_TARGET_x86="Y"
YOCTOADT_ROOTFS_x86="sdk minimal"
YOCTOADT_TARGET_SYSROOT_IMAGE_x86="sdk"
YOCTOADT_TARGET_SYSROOT_x86="$HOME/test-yocto/x86"

YOCTOADT_TARGET_powerpc="N"
YOCTOADT_ROOTFS_powerpc="sdk sato minimal"
YOCTOADT_TARGET_SYSROOT_IMAGE_powerpc="minimal"
YOCTOADT_TARGET_SYSROOT_powerpc="$HOME/test-yocto/mips"

YOCTOADT_TARGET_mips="N"
YOCTOADT_ROOTFS_mips="sdk"
YOCTOADT_TARGET_SYSROOT_IMAGE_mips="sdk"
YOCTOADT_TARGET_SYSROOT_mips="$HOME/test-yocto/mips"

Questions/comments
1. I'm assuming the "Check user configuration" and "Check architecture type"
messages are just for debugging and the in the final code they'll be gone
right?

2. Why I'm seeing so many downloading for all the cross-canadian for all
arches? According to your configure file, shouldn't just
i586-powerpc-canadian? Also, don't know where the "Downloading http://..."
message from, are they from the opkg install?

Thanks,
Jessica
Ke, Liping wrote:

Hi, Jessica
I have update the installer on http://llu-piketon.sh.intel.com/. I
have tested in your machine roughly, downloading should work if you
use wget -Y off to turn off all your proxy settings for testing.
Since there're dangling folders in your machine, I can't rudely
delete it. You can download the new package and test.

There're some other prompt problems I need to adjust. Today is not
the final code, only for your reviewing and testing.

Any problem, just let me know.

Thanks& Regards,
criping



-----Original Message-----
From: Zhang, Jessica
Sent: Thursday, December 02, 2010 8:19 AM
To: Ke, Liping; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: RE: yocto_installer test script update

Liping,

I've modified couple files mainly for the messaging, styling, etc.
Also, globaly changed SDK to ADT (Application Development Tools,
which is the new name that came out refering to the toolchains,
etc.). Please see attachment.

Other comments:
1. I'd expect after your do the code clean up, the code logic flow
should be more clearer, now the functions and main installation code
are mingled together 2. There're couple places that I commented off
with my initial JZ which I don't think there're the needs for the
code, we can walk through them tonight...
3. For target sysroot setup, I'd expect similar prompt to the user
about the specified configuration and confirmation 4. Also for target
sysroot setup, in the yocto_config file, you specify
ROOTFS_powerpc="sdk" TARGET_SYSROOT_IMAGE_powerpc="sato"
I'd expect the installer will run into error since the download
images only contain SDK no sato, sysroot can't be setup using sato,
which I think it's missing from the current code...

In general it looks good and main flow that needs to be covered are
there...

Thanks,
Jessica


-----Original Message-----
From: Ke, Liping
Sent: Wednesday, December 01, 2010 2:06 AM
To: Zhang, Jessica; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: yocto_installer test script update

Hi, Jessica

The newer version of the installer is in lianhao's location. You can
directly run ./yocto_installer http://llu-piketon.sh.intel.com/ Today
we tested both on 32 bit and 64 bit ubuntu host.

It's very initial and rough, I will move many non-root required ops
into the outer wrapper script later.

Any early comments are welcomed, just let me know.

Thanks& Regards,
criping


Re: Still having build problems - what version of python is required?

Joshua Lock <josh@...>
 

On Thu, 2010-12-02 at 10:54 -0800, Tim Bird wrote:
So I gave up, for the time being, trying to build behind
my firewall.

I tried to set up a machine outside my firewall to do a build.
Unfortunately, this machine is a bit dated. It is running
Fedora 8, with python version 2.5.1.

Here's what I get when I run bitbake:

[tbird@tree poky-4.0-build]$ bitbake poky-image-minimal
File "/a/home/tbird/work/yocto/poky-laverne-4.0/scripts/..//bitbake//bin/bitbake", line 207
except Exception as e:
^
SyntaxError: invalid syntax
[tbird@tree poky-4.0-build]$ python --version
Python 2.5.1
[tbird@tree poky-4.0-build]$ cat /etc/issue
Fedora release 8 (Werewolf)1

What version of python is required?

Note also that I couldn't find a prce package for this distro, despite
there being an prce-devel page available. I don't know how important
that will be for building stuff.

Is it a dead end trying to get a host distro this old to build
poky?
Possibly not, poky can build a standalone Python for people without
Python 2.6 on their host system. If you've any will left it could be
enough, I've used this Python version to do Poky builds on CentOS 5.5.

You need the appropriate version from
http://autobuilder.yoctoproject.org/downloads/miscsupport/

It will need extracting at / and will inflate
to /opt/poky/sysroots/$ARCH-pokysdk-linux/usr/bin/python you'll probably
want to update your PATH.

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


Re: Still having build problems - what version of python is required?

Gary Thomas
 

On 12/02/2010 11:54 AM, Tim Bird wrote:
So I gave up, for the time being, trying to build behind
my firewall.

I tried to set up a machine outside my firewall to do a build.
Unfortunately, this machine is a bit dated. It is running
Fedora 8, with python version 2.5.1.
You need at least 2.6

Here's what I get when I run bitbake:

[tbird@tree poky-4.0-build]$ bitbake poky-image-minimal
File "/a/home/tbird/work/yocto/poky-laverne-4.0/scripts/..//bitbake//bin/bitbake", line 207
except Exception as e:
^
SyntaxError: invalid syntax
[tbird@tree poky-4.0-build]$ python --version
Python 2.5.1
[tbird@tree poky-4.0-build]$ cat /etc/issue
Fedora release 8 (Werewolf)1

What version of python is required?

Note also that I couldn't find a prce package for this distro, despite
there being an prce-devel page available. I don't know how important
that will be for building stuff.

Is it a dead end trying to get a host distro this old to build
poky?
Probably yes. Can't you upgrade? Fedora 8 is really old now...

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------


Still having build problems - what version of python is required?

Tim Bird <tim.bird@...>
 

So I gave up, for the time being, trying to build behind
my firewall.

I tried to set up a machine outside my firewall to do a build.
Unfortunately, this machine is a bit dated. It is running
Fedora 8, with python version 2.5.1.

Here's what I get when I run bitbake:

[tbird@tree poky-4.0-build]$ bitbake poky-image-minimal
File "/a/home/tbird/work/yocto/poky-laverne-4.0/scripts/..//bitbake//bin/bitbake", line 207
except Exception as e:
^
SyntaxError: invalid syntax
[tbird@tree poky-4.0-build]$ python --version
Python 2.5.1
[tbird@tree poky-4.0-build]$ cat /etc/issue
Fedora release 8 (Werewolf)1

What version of python is required?

Note also that I couldn't find a prce package for this distro, despite
there being an prce-devel page available. I don't know how important
that will be for building stuff.

Is it a dead end trying to get a host distro this old to build
poky?
-- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Network Entertainment
=============================


Re: why cp in do_install() change file permission mode?

Hatle, Mark <mark.hatle@...>
 

Sorry for the brief response, but...

Do_install is performed under 'pseudo'. Pseudo is a ld_preload that intercepts calls and captures permissions, users and groups settings to allow root-like actions to occur.

In order for the sstate components to be easily copied and manipulated outside of pseudo control, permissions are modified.

If you look at the produced package/filesystem image the permissions/owner/group will be as expected. If you don't see that behavior then we should investigate.

Note pseudo only captures the attributes as set. So if cp, install, etc doesn't set it -- pseudo won't capture it.

----- Original Message -----
From: Lu, Lianhao [mailto:lianhao.lu@...]
Sent: Thursday, December 02, 2010 02:16 AM
To: yocto@... <yocto@...>
Subject: [yocto] why cp in do_install() change file permission mode?

Hi fellows,

Could anyone tell me why does the cp in do_install() change the file permission mode? Thanks!

do_install () {
rm -rf ${D}${installed_dir}
install -d ${D}${installed_dir}
cp -rp ${S}/* ${D}${installed_dir}
}

After "bitbake xxx -c install", I found the file under ${D}${installed_dir} had the permission mode of 0744 while the corresponding file under directory ${S} had the mode of 0644. Why did this happen? How to avoid this kind of mode change? Thanks!

Best Regards
-Lianhao Lu
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: The patch_2.5.9.bb download another version source file

Kamble, Nitin A <nitin.a.kamble@...>
 

I Mei Lei,
I have also noticed it. The patch recipe has customizations which I have not seen in other recipes. Like instead of getting the version, it gets older version, and adds a patch to update it to the later version. I also have some issues to upgrade it to latest version. I am working on sorting these out with Richard.

Thanks,
Nitin

-----Original Message-----
From: Mei, Lei
Sent: Thursday, December 02, 2010 5:54 AM
To: Kamble, Nitin A
Cc: yocto@...
Subject: RE: [yocto] The patch_2.5.9.bb download another version source
file

Hi Nitin,
This issue still exists. Can you help me to have a look?

Thanks
Lei

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-
bounces@...] On Behalf Of Mei, Lei
Sent: Thursday, November 25, 2010 11:05 AM
To: Kamble, Nitin A
Cc: yocto@...
Subject: [yocto] The patch_2.5.9.bb download another version source
file

Hi Nitin,
I am adding the license file MD5sum information to recipe, but I
find the recipe "patch_2.5.9.bb" downloaded the source file from
"patch-2.5.4.tar.gz", this will result in the COPYING file MD5sum is
not match with the bitbake calculate. I find you are the maintainer ,so
can you tell me the reason?

Thanks
Lei


---
Mei, Lei
Email: lei.mei@...


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


Re: [PATCH] meta-bsp-kirkwood: created layer for Marvellkirkwood

Darren Hart <dvhart@...>
 

On 11/29/2010 01:07 PM, Frans Meulenbroeks wrote:
Actually wanted my reply to Bruce to go to the list too (and guess his
reply should also have gone to the list so added that too).

Issue is that most of the other lists I'm on (including openembedded)
use reply to reply to the list, not to the original author.
Guess I'll make this mistake every once in a while).
Best practice is to use reply-to-all. That ensures you get the list as well as the CC'd parties. Many people will miss messages sent only to the list, so it is a good idea to keep the participants in a thread on CC.

--
Darren Hart
Yocto Linux Kernel


Re: why cp in do_install() change file permission mode?

Bruce Ashfield <bruce.ashfield@...>
 

On 10-12-02 05:16 AM, Lu, Lianhao wrote:
Hi fellows,

Could anyone tell me why does the cp in do_install() change the file permission mode? Thanks!

do_install () {
rm -rf ${D}${installed_dir}
install -d ${D}${installed_dir}
cp -rp ${S}/* ${D}${installed_dir}
}

After "bitbake xxx -c install", I found the file under ${D}${installed_dir} had the permission mode of 0744 while the corresponding file under directory ${S} had the mode of 0644. Why did this happen? How to avoid this kind of mode change? Thanks!
What's the umask of the your uid ? .. or maybe this is
one of those settings that is controlled by bitbake/poky.
But either way, it should just be that the cp is taking
the current umask which is changing the mode to 0744.

One option is to use install to copy the files, since it
allows a specific set of permissions to be set on its
command line.

I haven't looked into this at all, just some thoughts
off the top of my head.

Cheers,

Bruce


Best Regards
-Lianhao Lu
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: The patch_2.5.9.bb download another version source file

Mei, Lei <lei.mei@...>
 

Hi Nitin,
This issue still exists. Can you help me to have a look?

Thanks
Lei

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Mei, Lei
Sent: Thursday, November 25, 2010 11:05 AM
To: Kamble, Nitin A
Cc: yocto@...
Subject: [yocto] The patch_2.5.9.bb download another version source file

Hi Nitin,
I am adding the license file MD5sum information to recipe, but I find the recipe "patch_2.5.9.bb" downloaded the source file from "patch-2.5.4.tar.gz", this will result in the COPYING file MD5sum is not match with the bitbake calculate. I find you are the maintainer ,so can you tell me the reason?

Thanks
Lei


---
Mei, Lei
Email: lei.mei@...


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


why cp in do_install() change file permission mode?

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

Hi fellows,

Could anyone tell me why does the cp in do_install() change the file permission mode? Thanks!

do_install () {
rm -rf ${D}${installed_dir}
install -d ${D}${installed_dir}
cp -rp ${S}/* ${D}${installed_dir}
}

After "bitbake xxx -c install", I found the file under ${D}${installed_dir} had the permission mode of 0744 while the corresponding file under directory ${S} had the mode of 0644. Why did this happen? How to avoid this kind of mode change? Thanks!

Best Regards
-Lianhao Lu


Re: yocto_installer test script update

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

Hi, Jessica
I have update the installer on http://llu-piketon.sh.intel.com/. I have tested in your machine roughly, downloading should work if you use wget -Y off to turn off all your proxy settings for testing. Since there're dangling folders in your machine, I can't rudely delete it. You can download the new package and test.

There're some other prompt problems I need to adjust. Today is not the final code, only for your reviewing and testing.

Any problem, just let me know.

Thanks& Regards,
criping

-----Original Message-----
From: Zhang, Jessica
Sent: Thursday, December 02, 2010 8:19 AM
To: Ke, Liping; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: RE: yocto_installer test script update

Liping,

I've modified couple files mainly for the messaging, styling, etc.
Also, globaly changed SDK to ADT (Application Development Tools, which
is the new name that came out refering to the toolchains, etc.).
Please see attachment.

Other comments:
1. I'd expect after your do the code clean up, the code logic flow
should be more clearer, now the functions and main installation code
are mingled together 2. There're couple places that I commented off
with my initial JZ which I don't think there're the needs for the code,
we can walk through them tonight...
3. For target sysroot setup, I'd expect similar prompt to the user
about the specified configuration and confirmation 4. Also for target
sysroot setup, in the yocto_config file, you specify
ROOTFS_powerpc="sdk"
TARGET_SYSROOT_IMAGE_powerpc="sato"
I'd expect the installer will run into error since the download images
only contain SDK no sato, sysroot can't be setup using sato, which I
think it's missing from the current code...

In general it looks good and main flow that needs to be covered are
there...

Thanks,
Jessica


-----Original Message-----
From: Ke, Liping
Sent: Wednesday, December 01, 2010 2:06 AM
To: Zhang, Jessica; Lu, Lianhao; Tian, Kevin
Cc: yocto@...
Subject: yocto_installer test script update

Hi, Jessica

The newer version of the installer is in lianhao's location. You can
directly run ./yocto_installer http://llu-piketon.sh.intel.com/ Today
we tested both on 32 bit and 64 bit ubuntu host.

It's very initial and rough, I will move many non-root required ops
into the outer wrapper script later.

Any early comments are welcomed, just let me know.

Thanks& Regards,
criping