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
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
]
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
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
@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
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
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
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
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
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
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
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
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
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
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
15 matches
Mail list logo
