Re: [yocto] RFC: Web UI design for bitbake

[Yury Bushmelev]

2011/12/20 Wang, Shane :
> Hi all,
>
> Web UI interface is the next what we are going to do. Uriel drafted the first 
> iteration of the architecture design and I posted it onto 
> https://wiki.yoctoproject.org/wiki/Web_UI.
>
> Looking forward to your feedbacks.

I would prefer to remove PHP from there and re-use python (django
framework e.g.) just because we already have python as bitbake runtime
dependency. We may even use builtin python-based web-server because
control interface requires no high perfomance solutions.

I remember some ideas about splitting bitbake to client/server
processes like e.g. transmission or quassel.
Then one may run bitbake server on headless machine and control it
with bitbake client from desktop/notebook/tablet. So one may control
it with any bitbake client - HOB, WebUI, command-line.

-- 
Yury Bushmelev
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Web UI design for bitbake

[Samuel Stirtzel]

2011/12/20 Wang, Shane :
> Hi all,
>
> Web UI interface is the next what we are going to do. Uriel drafted the first 
> iteration of the architecture design and I posted it onto 
> https://wiki.yoctoproject.org/wiki/Web_UI.
>
> Looking forward to your feedbacks.
>
> --
> Shane
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

It sounds like you want to build it all from scratch, quite a lot of
work to build a fully featured web build system,
in this case compatibility to other systems would be nice.


For web builds with bitbake, Jenkins-CI (a fork of the continuous
integration system Hudson) [1] could be worth a look,
it is more than just a build tool.

There is also Autobuilder, but I guess for end users it is too much
configuration effort?
Jenkins-CI was very easy to setup and with a plug-in it could be as
simple as pointing the web-UI to the Bitbake path,
managing cluster/cloud/slave-pc entities is easy too.

Just my 0.02 cents in the case that you didn't already cast it in concrete.
IMHO it looks like Jenkins and the concept-pdf are very similar,
only difference seems to be: you want to invent it all by yourself?


[1] Jenkins-CI : http://jenkins-ci.org/

-- 
Regards
Samuel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Poky-Build error

[Navani Kamal Srivastava]

Hi,

We are facing the problem when we are compiling poky-bernard5.0 -(  bitbake -v 
-b poky-image-eb.bb )


NOTE: package poky-image-eb-1.0-r0: task do_install: Started
NOTE: package poky-image-eb-1.0-r0: task do_install: Succeeded
NOTE: Running noexec task 13 of 15 (ID: 10, 
/home/prashanth/yocto/poky-bernard-5.0/meta/recipes-eb/images/poky-image-eb.bb, 
do_package_write)
NOTE: Running task 14 of 15 (ID: 9, 
/home/prashanth/yocto/poky-bernard-5.0/meta/recipes-eb/images/poky-image-eb.bb, 
do_rootfs)
ERROR: 
'/home/prashanth/yocto/poky-bernard-5.0/meta/recipes-eb/images/poky-image-eb.bb'
 failed
NOTE: package poky-image-eb-1.0-r0: task do_rootfs: Started
ERROR: Function 'do_rootfs' failed (see 
/home/prashanth/yocto/poky-bernard-5.0/build/tmp/work/mx35pdk-poky-linux-gnueabi/poky-image-eb-1.0-r0/temp/log.do_rootfs.9800
 for further information)
ERROR: Logfile of failure stored in: 
/home/prashanth/yocto/poky-bernard-5.0/build/tmp/work/mx35pdk-poky-linux-gnueabi/poky-image-eb-1.0-r0/temp/log.do_rootfs.9800
Log data follows:
| 
/home/prashanth/yocto/poky-bernard-5.0/build/tmp/work/mx35pdk-poky-linux-gnueabi/poky-image-eb-1.0-r0/temp/run.do_rootfs.9800:
 line 91: makedevs: command not found
| ERROR: Function 'do_rootfs' failed (see 
/home/prashanth/yocto/poky-bernard-5.0/build/tmp/work/mx35pdk-poky-linux-gnueabi/poky-image-eb-1.0-r0/temp/log.do_rootfs.9800
 for further information)
NOTE: package poky-image-eb-1.0-r0: task do_rootfs: Failed
ERROR: Task 9 
(/home/prashanth/yocto/poky-bernard-5.0/meta/recipes-eb/images/poky-image-eb.bb,
 do_rootfs) failed with exit code '1'
prashanth@eb-vmc-desktop:~/yocto/poky-bernard-5.0/build$

Any help related to resolving this error is appreciable.


Thanks & Regards,
Navani Kamal Srivastava


Larsen & Toubro Limited

www.larsentoubro.com

This mail is classified as: ( ) L&T Proprietary ( ) L&T Confidential (X) L&T 
Internal Use ( ) L&T General Business
This email may contain confidential or privileged information for the intended 
recipient(s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.



Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended 
recipient (s) If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Web UI design for bitbake

[Uriel Liu]

Hi Samuel,

Thanks for your precious comment which is much more valuable than 0.02 cents 
(lol) . I'll take a look at Jenkins and Hudson to see how could we save our 
effort with these.


Sincerely yours,
Uriel Liu



-Original Message-
From: Samuel Stirtzel [mailto:s.stirt...@googlemail.com] 
Sent: 2011年12月20日 16:29
To: Wang, Shane
Cc: yocto@yoctoproject.org; Uriel Liu
Subject: Re: [yocto] RFC: Web UI design for bitbake

2011/12/20 Wang, Shane :
> Hi all,
>
> Web UI interface is the next what we are going to do. Uriel drafted the first 
> iteration of the architecture design and I posted it onto 
> https://wiki.yoctoproject.org/wiki/Web_UI.
>
> Looking forward to your feedbacks.
>
> --
> Shane
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

It sounds like you want to build it all from scratch, quite a lot of work to 
build a fully featured web build system, in this case compatibility to other 
systems would be nice.


For web builds with bitbake, Jenkins-CI (a fork of the continuous integration 
system Hudson) [1] could be worth a look, it is more than just a build tool.

There is also Autobuilder, but I guess for end users it is too much 
configuration effort?
Jenkins-CI was very easy to setup and with a plug-in it could be as simple as 
pointing the web-UI to the Bitbake path, managing cluster/cloud/slave-pc 
entities is easy too.

Just my 0.02 cents in the case that you didn't already cast it in concrete.
IMHO it looks like Jenkins and the concept-pdf are very similar, only 
difference seems to be: you want to invent it all by yourself?


[1] Jenkins-CI : http://jenkins-ci.org/

--
Regards
Samuel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Web UI design for bitbake

[Wang, Shane]

Samuel Stirtzel wrote on 2011-12-20:

> 2011/12/20 Wang, Shane :
>
> It sounds like you want to build it all from scratch, quite a lot of
> work to build a fully featured web build system,
> in this case compatibility to other systems would be nice.
> 
> 
> For web builds with bitbake, Jenkins-CI (a fork of the continuous
> integration system Hudson) [1] could be worth a look,
> it is more than just a build tool.
> 
> There is also Autobuilder, but I guess for end users it is too much
> configuration effort?
> Jenkins-CI was very easy to setup and with a plug-in it could be as
> simple as pointing the web-UI to the Bitbake path,
> managing cluster/cloud/slave-pc entities is easy too.
> 
> Just my 0.02 cents in the case that you didn't already cast it in concrete.
> IMHO it looks like Jenkins and the concept-pdf are very similar,
> only difference seems to be: you want to invent it all by yourself?
> 
> 
> [1] Jenkins-CI : http://jenkins-ci.org/
>

Thanks for the feedbacks. We considered autobuilder previously. But they are 
similar but different.
Web HOB is going to provide a tool to deeply customize images from browsers.
At this point, autobuilder is weaker.

We will have a look at your suggestions first.

--
Shane
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Web UI design for bitbake

[Wang, Shane]

Luo Zhenhua-B19537 wrote on 2011-12-20:

> Hello,
> 
> "hob" and website UI work in X env, is there a plan to support the
> Kernel configure manner GUI within Yocto to support UI configuration in
> console env?
> 
> 
> Best Regards,
> 
> Zhenhua
> 

AFAIK, so far no plan to provide UI in console like kernel's "menu config"?
But it is good because you raised that requirement ;-)

--
Shane
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Poky-Build error

[Mark Hatle]

On 12/20/11 2:33 AM, Navani Kamal Srivastava wrote:

Hi,

We are facing the problem when we are compiling poky-bernard5.0 –( bitbake –v –b
poky-image-eb.bb )




Log data follows:

|
/home/prashanth/yocto/poky-bernard-5.0/build/tmp/work/mx35pdk-poky-linux-gnueabi/poky-image-eb-1.0-r0/temp/run.do_rootfs.9800:
line 91: makedevs: command not found

| ERROR: Function 'do_rootfs' failed (see
/home/prashanth/yocto/poky-bernard-5.0/build/tmp/work/mx35pdk-poky-linux-gnueabi/poky-image-eb-1.0-r0/temp/log.do_rootfs.9800
for further information)


Your "poky-image-eb.bb" is attempting to run the makedevs command, but 
apparently it hasn't been built.  Check your logs for a makedevs-native.  If 
that hasn't been built, then it appears something is wrong with your 
configuration.  makedevs-native should be a dependency inherited by the 
image.bbclass.


Note on mailing list etiquette, please stop putting the trailing lines in your 
email.  This is a public mailing list, it is not for your companies "Internal 
Use", not is it reasonable to consider email send to a public list confidential 
in any way.



*This mail is classified as: ( ) L&T Proprietary ( ) L&T Confidential (X) L&T
Internal Use ( ) L&T General Business
This email may contain confidential or privileged information for the intended
recipient(s). If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.



*Larsen & Toubro Limited

www.larsentoubro.com

*This Email may contain confidential or privileged information for the intended
recipient (s) If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.


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


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

Re: [yocto] RFC: Web UI design for bitbake

[Samuel Stirtzel]

2011/12/20 Wang, Shane :
> Samuel Stirtzel wrote on 2011-12-20:
>
>> 2011/12/20 Wang, Shane :
>>
>> It sounds like you want to build it all from scratch, quite a lot of
>> work to build a fully featured web build system,
>> in this case compatibility to other systems would be nice.
>>
>>
>> For web builds with bitbake, Jenkins-CI (a fork of the continuous
>> integration system Hudson) [1] could be worth a look,
>> it is more than just a build tool.
>>
>> There is also Autobuilder, but I guess for end users it is too much
>> configuration effort?
>> Jenkins-CI was very easy to setup and with a plug-in it could be as
>> simple as pointing the web-UI to the Bitbake path,
>> managing cluster/cloud/slave-pc entities is easy too.
>>
>> Just my 0.02 cents in the case that you didn't already cast it in concrete.
>> IMHO it looks like Jenkins and the concept-pdf are very similar,
>> only difference seems to be: you want to invent it all by yourself?
>>
>>
>> [1] Jenkins-CI : http://jenkins-ci.org/
>>
>
> Thanks for the feedbacks. We considered autobuilder previously. But they are 
> similar but different.
> Web HOB is going to provide a tool to deeply customize images from browsers.
> At this point, autobuilder is weaker.

In the current state it is possible to use a so called parameterized
build for this purpose.
Here the user could choose between machines and images that where
configured in a selection and add a text based package list.

The architecture would make it possible to create a plug-in which
shows available machines, images and packages (with additional
informations).


The build result (rootfs or ipk/rpm) can be preserved for each build,
and it is possible to send them via e-mail, ftp, ssh+scp or any other way.


>
> We will have a look at your suggestions first.

For me the additional statistics of builds, like graphs that shows the
build time (file-size and whatever else) and easily customizable
functions,
give me the freedom of how I can build things and track the status of
my project in the way I want to do.


>
> --
> Shane


-- 
Regards
Samuel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Next week's (12/27/11) Yocto technical team meeting has been cancelled due to US/UK holiday

[Liu, Song]

Please let me know if you have any topics or issues you would like to address 
before our first Jan. meeting.

Thanks,
Song

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

[yocto] Minutes: Yocto Technical Team Meeting - Tuesday, December 20, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

[Liu, Song]

Attendees:
Paul, Beth, Saul, Josh, John Cherry, ScottR, Richard, Tom, Jessica, Jeff, Sean, 
Song
 
New action item list:
  - Mark will review unsorted features from Wind River team and try to have 
them scheduled (WIP, finalizing it.)
  - Song and Saul to follow on Scott Garmen's M2 schedule conflict.
 
Agenda:
* Opens collection - 5 min (Song)
 
* Yocto 1.1.1 point release update - 10 min (Josh)
  1.0.2 released? Any progress for 1.1.1? Targeting the end of Jan.? 
  - Branch together, some issues, most are fixed. You are targeting Mid-Jan.
 
* Yocto 1.2 M1 release readiness - 10 min (Team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status 
  - Wait for Jiajun's full test report for release readiness.
 
  - All P1 features are completed. Many P2/P3 features made into M1. Review 
incomplete M1 features (Current status? Anything depend on them? How to fit 
into the rest of milestones? What's the impact)
 
  - Many M2 features have been started. About half of the release development 
effort is in progress. Hopefully in the remaining milestones, the flow of pull 
requests will be relatively steady.
 
  - HOB2 made great progress. Even M2 features for HOB2 have been completed. 
Most of the features can be demonstrated under the current UI. There are still 
work to be done under the re-designed UI. Re-planning is in progress. Promising 
to complete HOB2 with re-designed UI. Bugzilla will be updated with the new 
plan. 
 
  - We got more medium+ bugs in the last 2 weeks. At the same time, we also 
fixed quite some. So the remaining med+ bugs are pretty much unchanged. Nitin 
has fixed a lot of bugs (24), He's leading on the number of bugs fixed. 
 
  - 3 high bugs: 
. multi-lib (1835), Richard has tested a fix and it works. 
. 1841: M1 build related testing with latest fix, already fixed in master. 
. 1807: FRI 2 related. Darren is working with ota...@ossystems.com.br on it
 
  - Package update exceeding our M1 target. Need Saul's data to update the 
chart.
 
  - Master status: green across the board. Fantastic! Thanks to Richard, Saul, 
Beth and the team
 
* Yocto 1.2 M2 planning status check and action plan - 10 min (Song)
  - Meta core team: done most last week, will complete this week. Song will 
follow up with Saul. Scott Garmen's M2 feature may be at risk since he has some 
work from Dave on training.  Richard has concerns on this. 1.2 is focused on 
usability. Error handling and removing warning messages are important. We will 
work out a solution for this. Need to wait after new year when Dave comes back. 
Options include taking other work off ScottG's shoulder or ask someone else to 
help. Song and Saul will follow up on this one.
  - Kernel team: Tom does not see any change for his M2 schedule. Will follow 
up with Darren and Bruce.
  - ADT: Jessica? BSP kernel tool needs to be moved to M3, Jessica will send 
Song email.
  - Paul: M2 schedule looks ok. No change
 
* Opens - 10 min
 - Bernard, 1.0.2: releasing Berbard today, release note ready, tarball set, 
made it to the mirror already. It's Bernard 5.0.2 ScottR will follow up with 
Beth on  any possible manual changes? Seems nothing so far.
 
* Action item Review - 5 min
 - Mark will review unsorted features from Wind River team and try to have 
them scheduled (WIP, finalizing it.)
 
* Weekly team sharing (20 min)
 - Sean: no major plan. Looking for some down time.
 - Jeff: Mark is making progress. 
 - Jessica: just came back from vacation. Looked at M2, done planning. Working 
on ADT.
 - Tom: worked on Yocto BSPs, usability, posted for review. Bugs and internal 
BSPs. Next week mainly focusing internal BSPs.
 - Richard: Spent time dealing with package bugs, clean installs and 
autobuilder issues. Pushed patches in, making sure we have green build for 
autobuilder. Some long standing bugs remaining, will be working on them. 
 - Scott R: working on some bugs, 3 done. A couple new ones in, working on 
them. working on remote system, so he can work remotely for a while. Windows 
users doc is done, it's a new page on the website. But need to wait for Jefro's 
website rework to be done to make it public.
 - John: looking for some downtime. 
 - Josh: working on release, trying to get 1.1.1 build ready for QA before 
Christmas break.
 - Saul: follow bugs, updates, pull requests, planning M2, avoiding the 
shopping crowd. 
 - Beth: Intel stuff, worked liecensing issues, trying to get some standard in 
order. There was work for M1, 1.1.1, 1.0.2. 
 - Paul: been doing host ditro testing. Update QT, hit a snag with recipes 
(linking with libs), still not sure about the fix. Will comtinue with that next 
week. Only taking UK holiday. 26/27 and 01/02/2012 

Special note: Our team sharing uncovered that we have less snow so far for this 
winter across US cities and UK. But it does not mean it's not cold. Still need 
to pay heating bill :(. 

Happy holidays everyone! :)


___
yocto mailing list

[yocto] [Announcement] Poky Bernard 5.0.2

[Flanagan, Elizabeth]

All,

We are pleased to announce the release of Poky Bernard 5.0.2

This release of poky is available at:
http://downloads.yoctoproject.org/releases/poky/poky-bernard-5.0.2.tar.bz2
or
http://mirrors.kernel.org/yocto/poky/poky-bernard-5.0.2.tar.bz2

Thank you everyone for all the hard work. For more info, please see:
http://www.yoctoproject.org/download/yocto/yocto-project-1.0.2-release-notes-poky-5.0.2

--
Elizabeth Flanagan
Yocto Project
Build and Release


POKY 5.0.2 RELEASE NOTES

Version: 5.0.2 "Bernard"
Location: 
http://downloads.yoctoproject.org/releases/poky/poky-bernard-5.0.2.tar.bz2
Mirror: http://mirrors.kernel.org/yocto/poky/poky-bernard-5.0.2.tar.bz2
QA Test Results: https://wiki.yoctoproject.org/wiki/Yocto_1.0.2_Test_Report


RELEASE INFO

   * poky
     - Git location: git://git.yoctoproject.org/poky.git
     - Git branch: bernard
     - Git tag: bernard-5.0+docs
     - Git rev: c0060446113f4418e2b5bf9c23143b5fe9bc95c0
     - Download:
http://downloads.yoctoproject.org/releases/poky/poky-bernard-5.0.2.tar.bz2
     - Mirror: http://mirrors.kernel.org/yocto/poky/poky-bernard-5.0.2.tar.bz2
     - md5sum: 8bce9755b3dce9f67ff96c5311d89554

NOTES

The purpose of this release is to provide support for building Bernard
on newer distributions such as Fedora 16 and Ubuntu 11.10.

This support consists of several patches related to:
* cross compilation on hosts with a Linux 3.x kernel
* host libraries changing location (i.e. Debian based systems have moved
libgl to a new location which affects the build of qemu-native)
* Fixing Makefiles to work with the stricter parser shipped with newer
versions of GNU Make

Further we have included security patches from various upstreams including:
* the Linux kernel
* libpng
* Python

Known issues

We are unable to fully support openSUSE 11.4 with this release of Poky.
We've discovered an issue where building binutils for a target machine
of the same architecture as the build host can result in nasty host
infection issues which cause the build to fail.
For more details see the bugzilla entry:
http://bugzilla.pokylinux.org/show_bug.cgi?id=1833
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [bernard 0/1] fix for bernard

[nitin . a . kamble]

From: Nitin A Kamble 

This commit fixes the binutils build issue on a perticular suse host.

Thanks,
Nitin

The following changes since commit 4f5622fb01bef25b121f293533cbfdd0067329ae:

  poky.conf: DISTRO bump (2011-12-19 14:35:40 -0800)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/bugfix
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfix

Nitin Kamble (1):
  binutils-2.21: fix building on suse 11.4

 .../binutils/binutils-cross-canadian_2.21.bb   |2 +-
 .../binutils/binutils-crosssdk_2.21.bb |2 +-
 meta/recipes-devtools/binutils/binutils.inc|2 +-
 meta/recipes-devtools/binutils/binutils_2.21.bb|2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

-- 
1.7.6.4

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

[yocto] [bernard 1/1] binutils-2.21: fix building on suse 11.4

[nitin . a . kamble]

From: Nitin Kamble 

x86_64 opensuse 11.4 has bintuils version 2.21, and when this
binutils_2.21 recipe is built for x86_64 target then, the invocation
of distro gcc fails with errors like this:

| /usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/as: 
symbol lookup error: 
/usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/as: 
undefined symbol: concat
| make[2]: *** [sysinfo.o] Error 1

The issue rootcaused as incompatible LD_LIBRARY_PATH while running the distro 
gcc.

This commit fixes the issue by clearing the LD_LIBRARY_PATH for distro gcc 
(CC_FOR_BUILD)

This Fixes bug: [YOCTO #1833]

Signed-off-by: Nitin A Kamble 
---
 .../binutils/binutils-cross-canadian_2.21.bb   |2 +-
 .../binutils/binutils-crosssdk_2.21.bb |2 +-
 meta/recipes-devtools/binutils/binutils.inc|2 +-
 meta/recipes-devtools/binutils/binutils_2.21.bb|2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb 
b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
index 7dad2a6..e91e7dc 100644
--- a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
+++ b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
@@ -1,3 +1,3 @@
 require binutils_${PV}.bb
 require binutils-cross-canadian.inc
-PR = "r0"
+PR = "r1"
diff --git a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb 
b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
index 0d6efff..21289cd 100644
--- a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
+++ b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
@@ -4,7 +4,7 @@ inherit crosssdk
 
 PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk"
 
-PR = "r0"
+PR = "r1"
 
 do_configure_prepend () {
sed -i 's#/usr/local/lib /lib /usr/lib#${SDKPATHNATIVE}/lib 
${SDKPATHNATIVE}/usr/lib /usr/local/lib /lib /usr/lib#' ${S}/ld/configure.tgt
diff --git a/meta/recipes-devtools/binutils/binutils.inc 
b/meta/recipes-devtools/binutils/binutils.inc
index d9e859e..1178e0c 100644
--- a/meta/recipes-devtools/binutils/binutils.inc
+++ b/meta/recipes-devtools/binutils/binutils.inc
@@ -71,7 +71,7 @@ export RANLIB_FOR_TARGET = "${TARGET_PREFIX}ranlib"
 export CC_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
 export CXX_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
 
-export CC_FOR_BUILD = "${BUILD_CC}"
+export CC_FOR_BUILD = "LD_LIBRARY_PATH= ${BUILD_CC}"
 export CPP_FOR_BUILD = "${BUILD_CPP}"
 export CFLAGS_FOR_BUILD = "${BUILD_CFLAGS}"
 
diff --git a/meta/recipes-devtools/binutils/binutils_2.21.bb 
b/meta/recipes-devtools/binutils/binutils_2.21.bb
index 270c720..f34b69d 100644
--- a/meta/recipes-devtools/binutils/binutils_2.21.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.21.bb
@@ -1,6 +1,6 @@
 require binutils.inc
 
-PR = "r0"
+PR = "r1"
 
 LIC_FILES_CHKSUM="\
 file://src-release;endline=17;md5=4830a9ef968f3b18dd5e9f2c00db2d35\
-- 
1.7.6.4

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

Re: [yocto] [bernard 1/1] binutils-2.21: fix building on suse 11.4

[Martin Jansa]

On Tue, Dec 20, 2011 at 11:37:03PM -0800, nitin.a.kam...@intel.com wrote:
> From: Nitin Kamble 
> 
> x86_64 opensuse 11.4 has bintuils version 2.21, and when this
> binutils_2.21 recipe is built for x86_64 target then, the invocation
> of distro gcc fails with errors like this:
> 
> | /usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/as: 
> symbol lookup error: 
> /usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/as: 
> undefined symbol: concat
> | make[2]: *** [sysinfo.o] Error 1
> 
> The issue rootcaused as incompatible LD_LIBRARY_PATH while running the distro 
> gcc.
> 
> This commit fixes the issue by clearing the LD_LIBRARY_PATH for distro gcc 
> (CC_FOR_BUILD)
> 
> This Fixes bug: [YOCTO #1833]

FWIW: I see the same issue with binutils-2.22 and oe-core master when
building qemux86-64 on gentoo.

> Signed-off-by: Nitin A Kamble 
> ---
>  .../binutils/binutils-cross-canadian_2.21.bb   |2 +-
>  .../binutils/binutils-crosssdk_2.21.bb |2 +-
>  meta/recipes-devtools/binutils/binutils.inc|2 +-
>  meta/recipes-devtools/binutils/binutils_2.21.bb|2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb 
> b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> index 7dad2a6..e91e7dc 100644
> --- a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> +++ b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> @@ -1,3 +1,3 @@
>  require binutils_${PV}.bb
>  require binutils-cross-canadian.inc
> -PR = "r0"
> +PR = "r1"
> diff --git a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb 
> b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> index 0d6efff..21289cd 100644
> --- a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> +++ b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> @@ -4,7 +4,7 @@ inherit crosssdk
>  
>  PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk"
>  
> -PR = "r0"
> +PR = "r1"
>  
>  do_configure_prepend () {
>   sed -i 's#/usr/local/lib /lib /usr/lib#${SDKPATHNATIVE}/lib 
> ${SDKPATHNATIVE}/usr/lib /usr/local/lib /lib /usr/lib#' ${S}/ld/configure.tgt
> diff --git a/meta/recipes-devtools/binutils/binutils.inc 
> b/meta/recipes-devtools/binutils/binutils.inc
> index d9e859e..1178e0c 100644
> --- a/meta/recipes-devtools/binutils/binutils.inc
> +++ b/meta/recipes-devtools/binutils/binutils.inc
> @@ -71,7 +71,7 @@ export RANLIB_FOR_TARGET = "${TARGET_PREFIX}ranlib"
>  export CC_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
>  export CXX_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
>  
> -export CC_FOR_BUILD = "${BUILD_CC}"
> +export CC_FOR_BUILD = "LD_LIBRARY_PATH= ${BUILD_CC}"
>  export CPP_FOR_BUILD = "${BUILD_CPP}"
>  export CFLAGS_FOR_BUILD = "${BUILD_CFLAGS}"
>  
> diff --git a/meta/recipes-devtools/binutils/binutils_2.21.bb 
> b/meta/recipes-devtools/binutils/binutils_2.21.bb
> index 270c720..f34b69d 100644
> --- a/meta/recipes-devtools/binutils/binutils_2.21.bb
> +++ b/meta/recipes-devtools/binutils/binutils_2.21.bb
> @@ -1,6 +1,6 @@
>  require binutils.inc
>  
> -PR = "r0"
> +PR = "r1"
>  
>  LIC_FILES_CHKSUM="\
>  file://src-release;endline=17;md5=4830a9ef968f3b18dd5e9f2c00db2d35\
> -- 
> 1.7.6.4
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto