Re: gentoo qemu (was Re: Binary tarball of toolchain/build environment)
On Tuesday 17 July 2007 16:14, Al Johnson wrote: My typo - no mail client configured on that machine. The issue is that with gcc-3.4.6 configured mtn --version returns the not found errors above, so it never gets to build qemu. With 4.1.2 mtn works, but qemu fails to build even though it's configured to use gcc-3.4.6 by the mod to the makefile. My home machine is a reasonably up to date Gentoo. I guess I did an update of the about 2 weeks ago. I first did the mokomake at home. The make failed on the qemu-build step. I added the --cc=gcc-3.4.6 and the make still failed (unfortunately I can't remember on what). A remake of setup-devel-image solved the problem and the system is working at home. My work machine is also a reasonably new Gentoo install. I just migrated my work machine to Gentoo less than a week ago. I added --cc=gcc-3.4.6 to my mokomakefile, but that was it. For the rest the system compiled cleanly. without hickups. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
Am Montag, 16. Juli 11:32 schrieb Al Johnson: i'm agree --- a good (simple installing ) development envirement can be important for the whole neo projekt (think of an simple eclipse-plugin ... you just install is ... and have fun. (with sample basic hello-world neo example and a good documentation)) torsten ps: for a core-level programmer this is maybe not so important , but for all app-developer it can be very worthfull I was going to suggest this too. This is the approach taken for the Neuros OSD, another linux-based device. It would give a known-working build and test environment, rather than having potential developers spending time trying to put such an environment together. Mokomakefile is good, but I just can't get the qemu to build under gentoo. http://wiki.neurostechnology.com/index.php/OSD_Virtual_Machine_Development On Monday 16 July 2007 10:05, Mario Wewer wrote: Maybe anybody could build a vmware image with all development tools already installed? That would make it much easier for us..? (at least for me...) (Then it would be possible to develope even on a MS mashine *smile*) - Original Message - From: Hans van der Merwe [EMAIL PROTECTED] To: openmoko community@lists.openmoko.org Sent: Freitag, 13. Juli 2007 15.29 Uhr (GMT+0100) Europe/Berlin Subject: Re: Binary tarball of toolchain/build environment On Fri, 2007-07-13 at 15:00 +0200, Torfinn Ingolfsen wrote: On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. FWIW, the MokoMakefile worked great for me on Xubuntu 7.04. Just make sure you have installed the required packages first. I had to install gcc-3.4 and sdl (devel) in order for 'make qemu' to work. Well, on openSUSE 10.2 I get Can't install openembedded-essential_1.1-1: no package provides python = 2.3 When trying to install openembedded-essential via smart packagemanger pointing to http://www.openembedded.org/dl/ I have python 2.5 installed. Any ideas? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
Maybe anybody could build a vmware image with all development tools already installed? That would make it much easier for us..? (at least for me...) (Then it would be possible to develope even on a MS mashine *smile*) - Original Message - From: Hans van der Merwe [EMAIL PROTECTED] To: openmoko community@lists.openmoko.org Sent: Freitag, 13. Juli 2007 15.29 Uhr (GMT+0100) Europe/Berlin Subject: Re: Binary tarball of toolchain/build environment On Fri, 2007-07-13 at 15:00 +0200, Torfinn Ingolfsen wrote: On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. FWIW, the MokoMakefile worked great for me on Xubuntu 7.04. Just make sure you have installed the required packages first. I had to install gcc-3.4 and sdl (devel) in order for 'make qemu' to work. Well, on openSUSE 10.2 I get Can't install openembedded-essential_1.1-1: no package provides python = 2.3 When trying to install openembedded-essential via smart packagemanger pointing to http://www.openembedded.org/dl/ I have python 2.5 installed. Any ideas? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
I was going to suggest this too. This is the approach taken for the Neuros OSD, another linux-based device. It would give a known-working build and test environment, rather than having potential developers spending time trying to put such an environment together. Mokomakefile is good, but I just can't get the qemu to build under gentoo. http://wiki.neurostechnology.com/index.php/OSD_Virtual_Machine_Development On Monday 16 July 2007 10:05, Mario Wewer wrote: Maybe anybody could build a vmware image with all development tools already installed? That would make it much easier for us..? (at least for me...) (Then it would be possible to develope even on a MS mashine *smile*) - Original Message - From: Hans van der Merwe [EMAIL PROTECTED] To: openmoko community@lists.openmoko.org Sent: Freitag, 13. Juli 2007 15.29 Uhr (GMT+0100) Europe/Berlin Subject: Re: Binary tarball of toolchain/build environment On Fri, 2007-07-13 at 15:00 +0200, Torfinn Ingolfsen wrote: On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. FWIW, the MokoMakefile worked great for me on Xubuntu 7.04. Just make sure you have installed the required packages first. I had to install gcc-3.4 and sdl (devel) in order for 'make qemu' to work. Well, on openSUSE 10.2 I get Can't install openembedded-essential_1.1-1: no package provides python = 2.3 When trying to install openembedded-essential via smart packagemanger pointing to http://www.openembedded.org/dl/ I have python 2.5 installed. Any ideas? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Fwd: Re: Binary tarball of toolchain/build environment
i'm agree --- a good (simple installing ) development envirement can be important for the whole neo projekt (think of an simple eclipse-plugin ... you just install is ... and have fun. (with sample basic hello-world neo example and a good documentation)) torsten ps: for a core-level programmer this is maybe not so important , but for all app-developer it can be very worthfull I was going to suggest this too. This is the approach taken for the Neuros OSD, another linux-based device. It would give a known-working build and test environment, rather than having potential developers spending time trying to put such an environment together. Mokomakefile is good, but I just can't get the qemu to build under gentoo. http://wiki.neurostechnology.com/index.php/OSD_Virtual_Machine_Development On Monday 16 July 2007 10:05, Mario Wewer wrote: Maybe anybody could build a vmware image with all development tools already installed? That would make it much easier for us..? (at least for me...) (Then it would be possible to develope even on a MS mashine *smile*) - Original Message - From: Hans van der Merwe [EMAIL PROTECTED] To: openmoko community@lists.openmoko.org Sent: Freitag, 13. Juli 2007 15.29 Uhr (GMT+0100) Europe/Berlin Subject: Re: Binary tarball of toolchain/build environment On Fri, 2007-07-13 at 15:00 +0200, Torfinn Ingolfsen wrote: On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. FWIW, the MokoMakefile worked great for me on Xubuntu 7.04. Just make sure you have installed the required packages first. I had to install gcc-3.4 and sdl (devel) in order for 'make qemu' to work. Well, on openSUSE 10.2 I get Can't install openembedded-essential_1.1-1: no package provides python = 2.3 When trying to install openembedded-essential via smart packagemanger pointing to http://www.openembedded.org/dl/ I have python 2.5 installed. Any ideas? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community --- ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
Al Johnson wrote: I was going to suggest this too. This is the approach taken for the Neuros OSD, another linux-based device. It would give a known-working build and test environment, rather than having potential developers spending time trying to put such an environment together. Mokomakefile is good, but I just can't get the qemu to build under gentoo. A good idea re providing a VM. BTW, I run Gentoo also and QEMU using Mokomakefile built with no problems here. Are you trying to do it with GCC 4.x? It supposedly is a known bug and you need to use GCC 3.x. Fortunately you can have both installed at the same time and use them where needed. I have GCC 3.x set as the default compiler. # equery list gcc [I--] [ -] sys-devel/gcc-3.4.6-r2 (3.4) [I--] [ -] sys-devel/gcc-4.1.2 (4.1) -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
gentoo qemu (was Re: Binary tarball of toolchain/build environment)
On Monday 16 July 2007 11:38, Jeff Rush wrote: Al Johnson wrote: I was going to suggest this too. This is the approach taken for the Neuros OSD, another linux-based device. It would give a known-working build and test environment, rather than having potential developers spending time trying to put such an environment together. Mokomakefile is good, but I just can't get the qemu to build under gentoo. A good idea re providing a VM. BTW, I run Gentoo also and QEMU using Mokomakefile built with no problems here. Are you trying to do it with GCC 4.x? It supposedly is a known bug and you need to use GCC 3.x. Fortunately you can have both installed at the same time and use them where needed. I have GCC 3.x set as the default compiler. # equery list gcc [I--] [ -] sys-devel/gcc-3.4.6-r2 (3.4) [I--] [ -] sys-devel/gcc-4.1.2 (4.1) I have both too, and use gcc-config to switch when emerging qemu. If I select 3.4.6 with gcc-config then run 'make qemu' mtn complains: mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version 'GLIBCXX_3.4.6' not found (required by mtn) mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version 'CXXABI_1.3.1' not found (required by mtn) Makefile: 28: *** Cannot determine version for monotone using mtn -version. Stop. Keeping gcc-config with 4.1.2 and tweaking Makefile setup-qemu to include --cc=gcc-3.4.6 after --target-list=arm-softmmu gets further, but dies after a bunch of errors in usb-linux-gadget.c I have linux-headers-2.6.21 as suggested elsewhere, but it seems not to have made any difference. This is on x86 - I've had even less luck on amd64. -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gentoo qemu (was Re: Binary tarball of toolchain/build environment)
Al Johnson wrote:
On Monday 16 July 2007 11:38, Jeff Rush wrote:
Al Johnson wrote:
I was going to suggest this too. This is the approach taken for the
Neuros OSD, another linux-based device. It would give a known-working
build and test environment, rather than having potential developers
spending time trying to put such an environment together. Mokomakefile is
good, but I just can't get the qemu to build under gentoo.
A good idea re providing a VM. BTW, I run Gentoo also and QEMU using
Mokomakefile built with no problems here. Are you trying to do it with GCC
4.x? It supposedly is a known bug and you need to use GCC 3.x.
Fortunately you can have both installed at the same time and use them where
needed. I have GCC 3.x set as the default compiler.
# equery list gcc
[I--] [ -] sys-devel/gcc-3.4.6-r2 (3.4)
[I--] [ -] sys-devel/gcc-4.1.2 (4.1)
I have both too, and use gcc-config to switch when emerging qemu. If I select
3.4.6 with gcc-config then run 'make qemu' mtn complains:
mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6:
version 'GLIBCXX_3.4.6' not found (required by mtn)
mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6:
version 'CXXABI_1.3.1' not found (required by mtn)
Makefile: 28: *** Cannot determine version for monotone using mtn -version.
Stop.
Hmm, the interesting thing there is that monotone requires a *double* dash for
long options, so manually doing mtn -version will indeed fail. In my
Makefile re the MokoMakefile, I have it with a double dash:
MTN_VERSION := $(shell mtn --version | awk '{ print $$2; }')
... in case this helps at all. I don't see any way to determine the version
of Makefile I have.
-Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: gentoo qemu (was Re: Binary tarball of toolchain/build environment)
On Mon, 2007-07-16 at 09:09 -0500, Jeff Rush wrote:
I have both too, and use gcc-config to switch when emerging qemu. If I
select
3.4.6 with gcc-config then run 'make qemu' mtn complains:
mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6:
version 'GLIBCXX_3.4.6' not found (required by mtn)
mtn: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6:
version 'CXXABI_1.3.1' not found (required by mtn)
Makefile: 28: *** Cannot determine version for monotone using mtn
-version.
Stop.
Hmm, the interesting thing there is that monotone requires a *double* dash
for
long options, so manually doing mtn -version will indeed fail. In my
Makefile re the MokoMakefile, I have it with a double dash:
MTN_VERSION := $(shell mtn --version | awk '{ print $$2; }')
... in case this helps at all. I don't see any way to determine the version
of Makefile I have.
-Jeff
Hi all,
Running gentoo here, I worked around this issue by re-emerging monotone
with gcc 3.4.6, I am not sure if its the right solution. But atleast it
solves the problem at hand
Regards
Sudharshan S
P.S: To the list maintainer, can you configure a reply-to munging such
that when i hit reply the mail gets sent to the lists instead of the OP.
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
On Fri, 2007-07-13 at 13:34 +0200, Shakthi Kannan wrote: Hi, Can someone provide a link to a binary tarball for the openmoko toolchain/build environment? (similar to CodeSourcery's GNU toolchains): http://www.codesourcery.com/gnu_toolchains/arm/download.html Something that I can simply download, extract and use it to build packages, and test it on qemu? Or, do I need to follow the 'build from scratch' procedure: http://wiki.openmoko.org/wiki/Building_OpenMoko_from_scratch I don't have a direct (firewall-free) connection to the Internet. Thanks, SK I want that to - seeing that building from scratch doesn't want to work on my openSUSE 10.2 distro.?? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. FWIW, the MokoMakefile worked great for me on Xubuntu 7.04. Just make sure you have installed the required packages first. I had to install gcc-3.4 and sdl (devel) in order for 'make qemu' to work. -- Regards, Torfinn Ingolfsen ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
A tarball would be really great, because I have several problems on my amd64-gentoo, too. Starting at gcc3 (gentoo uses gcc4 per default and switching to 3 sucks) to several amd64 problems. 2007/7/13, Shakthi Kannan [EMAIL PROTECTED]: Hi, On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. ... and you thought I didn't know that? I cannot connect any machine to _this_ network. I don't have any other Internet connectivity, either. Hence, the need for the tarball. Regards, SK -- Shakthi Kannan http://www.shakthimaan.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
On 7/13/07, Shakthi Kannan [EMAIL PROTECTED] wrote: I don't have a direct (firewall-free) connection to the Internet. You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. regards VK ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Binary tarball of toolchain/build environment
On Fri, 2007-07-13 at 15:00 +0200, Torfinn Ingolfsen wrote: On 7/13/07, vivek khurana [EMAIL PROTECTED] wrote: You can try mokomake file. It has target for compiling qemu and running qemu. As for direct connection, try setting proxy variable in shell to connect a machine behind firewalled proxy server. FWIW, the MokoMakefile worked great for me on Xubuntu 7.04. Just make sure you have installed the required packages first. I had to install gcc-3.4 and sdl (devel) in order for 'make qemu' to work. Well, on openSUSE 10.2 I get Can't install openembedded-essential_1.1-1: no package provides python = 2.3 When trying to install openembedded-essential via smart packagemanger pointing to http://www.openembedded.org/dl/ I have python 2.5 installed. Any ideas? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Binary tarball of toolchain/build environment
Hi, Can someone provide a link to a binary tarball for the openmoko toolchain/build environment? (similar to CodeSourcery's GNU toolchains): http://www.codesourcery.com/gnu_toolchains/arm/download.html Something that I can simply download, extract and use it to build packages, and test it on qemu? Or, do I need to follow the 'build from scratch' procedure: http://wiki.openmoko.org/wiki/Building_OpenMoko_from_scratch I don't have a direct (firewall-free) connection to the Internet. Thanks, SK -- Shakthi Kannan http://www.shakthimaan.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
