On 12/20/12 17:19, Scott Wood wrote:
On 12/20/2012 12:59:05 AM, Gerd Hoffmann wrote:
Hi,
Why do you need this? Any tools not picked up correctly if you don't
set the PATH? Which ones?
If I don't set the PATH for configure then I get this:
ERROR: powerpc-linux-gnu-gcc either does
On Fri, Dec 21, 2012 at 9:56 AM, Gerd Hoffmann kra...@redhat.com wrote:
I mean with --cross-prefix specifying the absolute location (so you
don't have to mess with PATH), why does that not work?
He actually wrote already previously: The name is thrown into
config.sub, which obviously is
On 12/21/2012 04:56:05 AM, Robert Schiele wrote:
On Fri, Dec 21, 2012 at 9:56 AM, Gerd Hoffmann kra...@redhat.com
wrote:
I mean with --cross-prefix specifying the absolute location (so you
don't have to mess with PATH), why does that not work?
He actually wrote already previously: The name
On 12/20/2012 12:59:05 AM, Gerd Hoffmann wrote:
Hi,
Why do you need this? Any tools not picked up correctly if you
don't
set the PATH? Which ones?
If I don't set the PATH for configure then I get this:
ERROR: powerpc-linux-gnu-gcc either does not exist or does not
work
Any hints
On 12/14/12 19:51, Scott Wood wrote:
On 12/14/2012 02:13:53 AM, Gerd Hoffmann wrote:
Hi,
Yes, I could manually install it, though then I get to deal with
telling
the pixman build exactly where to install itself, and repeating the
process for each toolchain and multilib-variant thereof.
Hi,
# ls -l /usr/bin/*-gcc
-rwxr-xr-x. 2 root root 264112 Aug 23 2011 /usr/bin/i686-pc-mingw32-gcc
-rwxr-xr-x. 2 root root 268216 Oct 18 18:24
/usr/bin/x86_64-redhat-linux-gcc
I think the second part (pc / redhat) can be choosen pretty freely
when building gcc, so you could name your
On 12/19/2012 03:02:13 AM, Gerd Hoffmann wrote:
On 12/14/12 19:51, Scott Wood wrote:
On 12/14/2012 02:13:53 AM, Gerd Hoffmann wrote:
Hi,
Yes, I could manually install it, though then I get to deal with
telling
the pixman build exactly where to install itself, and repeating
the
On 12/19/2012 03:13:34 AM, Gerd Hoffmann wrote:
./configure
--cross-prefix=/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu-
make ?
A few more options than that, but basically yes.
I can get past this particular obstacle by doing something like:
Hi,
Why do you need this? Any tools not picked up correctly if you don't
set the PATH? Which ones?
If I don't set the PATH for configure then I get this:
ERROR: powerpc-linux-gnu-gcc either does not exist or does not work
Any hints in config.log what exactly failed?
...but then I
Hi,
No, they are with prefix, just not in $PATH. I have more than one
powerpc-linux-gnu toolchain and I don't want to mess with my $PATH
constantly to choose between them.
# ls -l /usr/bin/*-gcc
-rwxr-xr-x. 2 root root 264112 Aug 23 2011 /usr/bin/i686-pc-mingw32-gcc
-rwxr-xr-x. 2 root root
Hi,
Yes, I could manually install it, though then I get to deal with telling
the pixman build exactly where to install itself, and repeating the
process for each toolchain and multilib-variant thereof.
That part is easy too. You just need ${cross_prefix}-pkg-config.
A simple two-liner
On 12/14/2012 02:07:23 AM, Gerd Hoffmann wrote:
Hi,
No, they are with prefix, just not in $PATH. I have more than one
powerpc-linux-gnu toolchain and I don't want to mess with my $PATH
constantly to choose between them.
# ls -l /usr/bin/*-gcc
-rwxr-xr-x. 2 root root 264112 Aug 23 2011
On 12/14/2012 02:13:53 AM, Gerd Hoffmann wrote:
Hi,
Yes, I could manually install it, though then I get to deal with
telling
the pixman build exactly where to install itself, and repeating the
process for each toolchain and multilib-variant thereof.
That part is easy too. You just
On 13.12.2012, at 08:16, Gerd Hoffmann wrote:
On 12/13/12 01:57, Scott Wood wrote:
On 12/12/2012 01:52:29 AM, Gerd Hoffmann wrote:
On 12/12/12 04:18, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics
On 13 December 2012 14:44, Alexander Graf ag...@suse.de wrote:
That doesn't help for the full system load. We're talking of flash
chips in the MB range with an embedded initrd here
This is an edge case, and I think our approach here ought to
be to say we welcome patches which provide a coherent
On 13.12.2012, at 16:16, Gerd Hoffmann wrote:
Hi,
A pretty central data structure in qemu (DisplayState /
DisplaySurface) carries a pixman image, not some module which can
easily be made optional. Just look at the tons of #ifdef'ery you
have to do to get this going.
His point is that
On 12/13/2012 12:31:14 AM, Stefan Weil wrote:
Am 13.12.2012 01:48, schrieb Scott Wood:
It doesn't seem to like my --cross-prefix being a full path rather
than being a recognized target pattern:
checking host system type... Invalid configuration
On 12/13/2012 09:16:58 AM, Gerd Hoffmann wrote:
Hi,
A pretty central data structure in qemu (DisplayState /
DisplaySurface) carries a pixman image, not some module which can
easily be made optional. Just look at the tons of #ifdef'ery you
have to do to get this going.
His point is that
Hi,
A pretty central data structure in qemu (DisplayState /
DisplaySurface) carries a pixman image, not some module which can
easily be made optional. Just look at the tons of #ifdef'ery you
have to do to get this going.
His point is that anything related to DisplayState should be
Am 13.12.2012 16:53, schrieb Scott Wood:
On 12/13/2012 12:31:14 AM, Stefan Weil wrote:
Am 13.12.2012 01:48, schrieb Scott Wood:
It doesn't seem to like my --cross-prefix being a full path rather
than being a recognized target pattern:
checking host system type... Invalid configuration
On 12/13/2012 12:58:19 PM, Stefan Weil wrote:
Am 13.12.2012 16:53, schrieb Scott Wood:
On 12/13/2012 12:31:14 AM, Stefan Weil wrote:
Indeed, --cross-prefixdoes not support absolute path names.
I assume that the executables in
On 12/13/2012 01:16:48 PM, Scott Wood wrote:
On 12/13/2012 12:58:19 PM, Stefan Weil wrote:
A cross prefix which starts with an absolute path (like in your
scenario) justs
requires adding `dirname ${cross_prefix}` to PATH and passing
`basename ${cross_prefix%-} to the pixman configure.
On 12/12/2012 04:18 AM, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
Signed-off-by: Scott Woodscottw...@freescale.com
---
On 12 December 2012 03:18, Scott Wood scottw...@freescale.com wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
I would expect that we'd
Am 12.12.2012 17:28, schrieb John Spencer:
On 12/12/2012 04:18 AM, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
Am 12.12.2012 17:47, schrieb Peter Maydell:
On 12 December 2012 03:18, Scott Wood scottw...@freescale.com wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the
On 12 December 2012 17:09, Andreas Färber andreas.faer...@web.de wrote:
I already reported that the submodule does not configure on OSX/ppc
v10.5.8 - apparently due to some PKG_ macros not getting resolved. I
suspected aclocal not picking up pkg.m4 file but setting ACLOCAL_FLAGS
did not help.
Il 12/12/2012 18:09, Andreas Färber ha scritto:
Problems with cross compilation should be reported as bugs
so we can fix them -- we need to fix them anyway for the more
common case where there is host graphics support.
I already reported that the submodule does not configure on OSX/ppc
On 12/12/2012 12:46:44 AM, Stefan Weil wrote:
Am 12.12.2012 04:18, schrieb Scott Wood:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
On 12/12/2012 10:47:04 AM, Peter Maydell wrote:
On 12 December 2012 03:18, Scott Wood scottw...@freescale.com wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the
On 12/12/2012 10:54:04 AM, Andreas Färber wrote:
Am 12.12.2012 17:28, schrieb John Spencer:
On 12/12/2012 04:18 AM, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical
support
is unnecessary. The ability to turn off graphics support not only
saves some space,
On 12/12/2012 01:52:29 AM, Gerd Hoffmann wrote:
On 12/12/12 04:18, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
We have
Am 13.12.2012 01:48, schrieb Scott Wood:
On 12/12/2012 12:46:44 AM, Stefan Weil wrote:
Am 12.12.2012 04:18, schrieb Scott Wood:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it
On 12/13/12 01:57, Scott Wood wrote:
On 12/12/2012 01:52:29 AM, Gerd Hoffmann wrote:
On 12/12/12 04:18, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
Signed-off-by: Scott Wood scottw...@freescale.com
---
There are undoubtedly some rough edges that
Am 12.12.2012 04:18, schrieb Scott Wood:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
Signed-off-by: Scott Wood scottw...@freescale.com
---
On 12/12/12 04:18, Scott Wood wrote:
QEMU is sometimes used in embedded contexts, where graphical support
is unnecessary. The ability to turn off graphics support not only
saves some space, but it eliminates the dependency on pixman.
We have tons of hand-crafted pixel shuffeling code all over
37 matches
Mail list logo
