Skip to contentSkip to conversation

meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

PATCH Applied Robert Yang 3 participants 8 messages Apr 9, 2012 – Apr 10, 2012

lore
Share & tools
lore
#0 lore raw

cover meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64
* Ubuntu 10.04

* The testing commands are:

  $ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target.

// Robert

The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:

runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)

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

Robert Yang (1):
meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

 meta/conf/distro/include/tcmode-default.inc |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
#1 lore raw

PATCH 1/1 meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

runqemu can't launch a target image on Fedora 16 64bit or Opensuse 12.1 64bit, this is because runqemu needs the host's libGL.so, which requires GLIBC_2.14 which is defined in libc.so.6, but our default libc.so.6 is version 2.13, here is the message from Richard:

The easiest solution would be to change the nativesdk libc to 2.15. I don't think we plan to do this for the target libc for 1.2 but we could change nativesdk's version if its well tested

[YOCTO #1968]

---
 meta/conf/distro/include/tcmode-default.inc |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
meta/conf/distro/include/tcmode-default.inc +2 -2
index b481163..3dc0932 100644
@@ -44,9 +44,9 @@ PREFERRED_VERSION_linux-libc-headers ?= "${LINUXLIBCVERSION}"
 PREFERRED_VERSION_linux-libc-headers-nativesdk ?= "${LINUXLIBCVERSION}"
 PREFERRED_VERSION_eglibc                   ?= "${EGLIBCVERSION}"
 PREFERRED_VERSION_eglibc-locale            ?= "${EGLIBCVERSION}"
-PREFERRED_VERSION_eglibc-nativesdk         ?= "${EGLIBCVERSION}"
+PREFERRED_VERSION_eglibc-nativesdk         ?= "2.15"
 PREFERRED_VERSION_eglibc-initial           ?= "${EGLIBCVERSION}"
-PREFERRED_VERSION_eglibc-initial-nativesdk ?= "${EGLIBCVERSION}"
+PREFERRED_VERSION_eglibc-initial-nativesdk ?= "2.15"
 PREFERRED_VERSION_cross-localedef-native   ?= "${EGLIBCVERSION}"
 PREFERRED_VERSION_uclibc                   ?= "${UCLIBCVERSION}"
 PREFERRED_VERSION_uclibc-initial           ?= "${UCLIBCVERSION}"
Signature · 1 line
1.7.1
#2 lore raw
In reply to Robert Yang

Robert Yang wrote on 2012-04-09:

Quoted 4 lines

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64

Robert,
Hongna just found a qemu launch error on openSuse x86_64 using the 2.15 eglibc-nativesdk, something about the SDL initialization error. Did your platform work well?

Quoted 15 lines

* Ubuntu 10.04
* The testing commands are:

  $ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target.
// Robert

The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:

runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/tc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/tc
Robert Yang (1):
meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

Quoted 6 lines
 meta/conf/distro/include/tcmode-default.inc |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

_______________________________________________ Openembedded-core mailing list [email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Best Regards,
Lianhao

#3 lore raw
Quoted 10 lines · Lianhao

Robert Yang wrote on 2012-04-09:

Quoted 4 lines

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64

Robert,
Hongna just found a qemu launch error on openSuse x86_64 using the 2.15 eglibc-nativesdk, something about the SDL initialization error. Did your platform work well?

Maybe he just used "ssh" without "-X" or "-Y" ? There would be an SDL initialization error when ssh without "-X" or "-Y". It worked well for me.

// Robert

Quoted 32 lines
Quoted 15 lines

* Ubuntu 10.04
* The testing commands are:

   $ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target.
// Robert

The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:

   runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/tc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/tc
Robert Yang (1):
meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

Quoted 6 lines
  meta/conf/distro/include/tcmode-default.inc |    4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)

_______________________________________________ Openembedded-core mailing list [email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Best Regards,
Lianhao

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#4 lore raw
Quoted 10 lines · Robert Yang
Quoted 7 lines · Lianhao

Robert Yang wrote on 2012-04-09:

Quoted 4 lines

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64

Quoted 6 lines
Quoted 5 lines

Robert,
Hongna just found a qemu launch error on openSuse x86_64 using the 2.15 eglibc-nativesdk, something about the SDL initialization error. Did your platform work well?

Here is the update information from Hongna:

I have finished the test on opensuse x86-64, both qemuarm and qemux86 do cross debug pass using 2.15 toolchain.

// Robert

Quoted 44 lines

Maybe he just used "ssh" without "-X" or "-Y" ? There would be an SDL initialization error when ssh without "-X" or "-Y". It worked well for me.

// Robert

Quoted 28 lines
Quoted 17 lines

* Ubuntu 10.04
* The testing commands are:

$ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target. // Robert

The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:

runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/tc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/tc
Robert Yang (1):
meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64 meta/conf/distro/include/tcmode-default.inc | 4 ++--

Quoted 5 lines
1 files changed, 2 insertions(+), 2 deletions(-)

_______________________________________________ Openembedded-core mailing list [email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Best Regards,
Lianhao

Quoted 5 lines

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#5 lore raw

Robert Yang wrote on 2012-04-10:

Quoted 20 lines · Robert Yang
Quoted 10 lines · Lianhao
Quoted 7 lines

Robert Yang wrote on 2012-04-09:

Quoted 4 lines

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64

Quoted 6 lines
Quoted 5 lines

Robert,
Hongna just found a qemu launch error on openSuse x86_64 using the 2.15 eglibc-nativesdk, something about the SDL initialization error. Did your platform work well?

Quoted 11 lines

Here is the update information from Hongna:

I have finished the test on opensuse x86-64, both qemuarm and qemux86 do cross debug pass using 2.15 toolchain.

// Robert

Quoted 4 lines

Maybe he just used "ssh" without "-X" or "-Y" ? There would be an SDL initialization error when ssh without "-X" or "-Y". It worked well for me.

// Robert

It just popped into my mind that when ssh with X forwarding, does the SDL initialization happen on the Xserver, which is NOT openSuse x86-64, while the xclient(qemu) is running on openSue? Could you try launching the qemu directly on the openSuse? Thanks!

-Lianhao

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

* Ubuntu 10.04
* The testing commands are:

$ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target. // Robert

#6 lore raw
Quoted 27 lines · Lianhao

Robert Yang wrote on 2012-04-10:

Quoted 25 lines · Robert Yang
Quoted 10 lines · Lianhao
Quoted 7 lines

Robert Yang wrote on 2012-04-09:

Quoted 4 lines

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64

Quoted 6 lines
Quoted 5 lines

Robert,
Hongna just found a qemu launch error on openSuse x86_64 using the 2.15 eglibc-nativesdk, something about the SDL initialization error. Did your platform work well?

Here is the update information from Hongna:

I have finished the test on opensuse x86-64, both qemuarm and qemux86 do cross debug pass using 2.15 toolchain.

Quoted 9 lines
Quoted 6 lines

// Robert

Quoted 4 lines

Maybe he just used "ssh" without "-X" or "-Y" ? There would be an SDL initialization error when ssh without "-X" or "-Y". It worked well for me.

// Robert

It just popped into my mind that when ssh with X forwarding, does the SDL initialization happen on the Xserver, which is NOT openSuse x86-64, while the xclient(qemu) is running on openSue? Could you try launching the qemu directly on the openSuse? Thanks!

Launching the qemu directly on the openSuse worked well, the ssh client is only for displaying the result from the server(opensuse 12.1 x86-64).

I usually use ssh -X or -Y to launch runqemu.

// Robert

Quoted 16 lines

-Lianhao

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

* Ubuntu 10.04
* The testing commands are:

$ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target. // Robert

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Applied
#7 lore raw
In reply to Robert Yang
Quoted 24 lines · Robert Yang

Test info:
* Have tested on:
* Fedora 16 x86_64
* Opensuse 12.1 x86_64
* Ubuntu 10.04

* The testing commands are:

   $ bitbake core-image-sato meta-toolchain meta-toolchain-sdk

And untar the sdk, then runqemu from the sdk to start the target.

// Robert

The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:

   runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)

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

Robert Yang (1):
meta-toolchain: runqemu falied on FC16/Opensuse12.1 x86_64

Quoted 9 lines
  meta/conf/distro/include/tcmode-default.inc |    4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Merged into OE-Core

Thanks
Sau!