-
---
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.n
On 15-Dec-2007, at 03:01 , Pedro Alves wrote:
Jack Jansen wrote:
Aha!
Now I think I start to understand why I had a lot of problems
building ffmpeg with cegcc: the assembly files didn't compile. So
apparently the ffmpeg developers used a different gcc-based
toolchain which h
the iPod/iPhone: here
the assembler also gave me errors, but they were completely different
from the errors I got when building for CE. So after reading this
message I wonder whether the assemblers come from completely
different heritage...
Is anyone else having similar problems? And, eve
On 15-nov-2007, at 12:00, Jack Jansen wrote:
> I'm not near the machine right now, but I wouldn't be surprised if a
> simple
> printf("%lld %d %lld", (long long)42, 43, 44);
> shows the problem.
Make that
printf("%lld %d %lld", (long long)42
t now, but I wouldn't be surprised if a
simple
printf("%lld %d %lld", (long long)42, 43, 44);
shows the problem.
--
Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part
tput of Dependency Walker 100%
correct, in stead of 98% as it is now: if something is available on
your windows desktop machine but not on Windows Mobile it won't
complain.
Does anyone know of a way to make Dependency Walker do this?
--
Jack Jansen, <[EMAIL PROTECTED]>, http:/
the symbol table, so I'm off in
never-never land.
Hence the question: has anyone else built for armv5te or xscale, with
or without success?
--
Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack
If I can't dance I do
nked them into our
Ambulant multimedia playback engine (built with VS2005) and it has
succeeded in playing back the first frame of a video (from local file).
After that I run out of memory, but until proven differently I'll
assume that's my problem:-)
--
Jack Jansen, <[EMAIL PROT
options (for other platforms) that mean things like "strictly adhere
to the ABI for ", something like that would be good. That is,
assuming there's a reason for the 4-byte alignment in stead of 8-byte
alignment.
Here's my original message, as google-bait:
From: Jack Jans
