Will Price wprice@... writes:
On Fri, May 10, 2013 at 11:46 PM, Carl Eugen Hoyos writes:
If you have a compilation problem, please provide the
following information:
Your configure line, (your FFmpeg version,) if (and only
if) compilation fails completely: Run make several times,
always
After a lot of work, I have arrived at the same issue last posted to this
list by Lars on April 5. That is the following warnings on link:
ld: warning: ARM function not 4-byte aligned: __b_evaluation from
ffmpeg/lib/libavcodec.a(simple_idct_arm.o)
ld: warning: ARM function not 4-byte aligned:
Will Price wprice@... writes:
The gas linked below
[...]
Allow me to repeat:
The only supported version of gas-preprocessor.pl is the
one mentioned on http://ffmpeg.org/platform.html
You are on your own with any other version.
If you have a compilation problem, please provide the
following
The gas linked below from the mansr github fork did not resolve this error
that occurs throughout the build process for ffmpeg for iOS:
Unable to identify target architecture at /usr/bin/gas-preprocessor.pl line
82.
AS libavcodec/arm/dsputil_arm.o
[and hundreds more like that afterwards...]
Yet,
2013/4/10 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
1) Distribute a prepackaged version of gas-processor.pl
that works, together with ffmpeg.
Very, very definitely:
No.
Ok, I take that as a No ;-) May I ask why? Another alternative solution
could
Lars Hammarstrand lars.hammarstrand@... writes:
3) Write a mail to yuvi and ask him to merge the
changes.
Mailed an update to ffmpeg-devel regarding the docs
that David Conrad intercepted and the repo is now
refreshed with Mans changes.
(Sorry: I had written a mail to him several days
2013/4/11 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
Like a git submodule or what do you suggest?
A link to github as on
http://ffmpeg.org/platform.html#Darwin-_0028Mac-OS-X_002c-iPhone_0029
Well, I'm not sure a that just a link would make it more
Lars Hammarstrand lars.hammarstrand@... writes:
One idea could be to add an gas option to configure,
like --gas=/abosolute/path/to/gas-preprocessor
This does already exist afaik.
(pls note that this does not work:
--as=/absolute/path/to/gas-preprocessor.pl /path/to/as... ).
Please test
Btw, think about the following not entirely impossible scenario:
Picture an legacy installation of ffmpeg with an old version of
gas-preprocessor
installed in /usr/local/bin. We would now like to configure a new
application embedded version of ffmpeg that requires a new
but incompatible version
2013/4/11 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
2.2. The basic problem lies in configure, line 3247 which is the line
that is commented out by the xbmc patch:
3246:darwin)
3247:gas=gas-preprocessor.pl $cc
|
2013/4/4 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
--as='/Users/Shared/xbmc-depends/buildtools-native/bin/
gas-preprocessor.pl
Which version of gas-preprocessor.pl is this?
A version prior to October 2012 would likely
explain the crashes you are
2013/4/5 Lars Hammarstrand lars.hammarstr...@gmail.com
Didn't find any gas-preprocessor.pl in the ffmpeg repo thus where do you
find one which is supported by ffmpeg?
Never mind, found this ref (in
github.com/FFmpeg/FFmpeg/blob/master/doc/platform.texi):
2013/4/5 Lars Hammarstrand lars.hammarstr...@gmail.com
2013/4/5 Lars Hammarstrand lars.hammarstr...@gmail.com
Didn't find any gas-preprocessor.pl in the ffmpeg repo thus where do you
find one which is supported by ffmpeg?
Never mind, found this ref (in
On Friday, April 5, 2013 at 4:26 PM, Lars Hammarstrand wrote:
Got some new errors with the new gas-preprocessor. Full log at:
http://pastebin.com/wF4aZGis. Brief summary:
Version info - ffmpeg e820e3a (n1.2), gas-preprocessor f4a42dc077 (Oct 03,
2012)
1. LD ffmpeg_g
ld: warning: ARM
2013/4/5 Alexey Belkevich belkev...@mlsdev.com
On Friday, April 5, 2013 at 4:26 PM, Lars Hammarstrand wrote:
Got some new errors with the new gas-preprocessor. Full log at:
http://pastebin.com/wF4aZGis. Brief summary:
Version info - ffmpeg e820e3a (n1.2), gas-preprocessor f4a42dc077 (Oct
Lars Hammarstrand lars.hammarstrand@... writes:
--as='/Users/Shared/xbmc-depends/buildtools-native/bin/gas-preprocessor.pl
Which version of gas-preprocessor.pl is this?
A version prior to October 2012 would likely
explain the crashes you are seeing.
Carl Eugen
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
Exactly 14 iterations, please trust me, I am doing
this quite often.
Ok, I'll trust you completely
(I was actually wrong: 14 iterations == 15 compiles)
That will take roughly 7,5 hours (give
2013/4/3 Michael Niedermayer michae...@gmx.at
On Tue, Apr 02, 2013 at 08:38:18PM +0200, Lars Hammarstrand wrote:
2013/4/2 Carl Eugen Hoyos ceho...@ag.or.at
(gdb) *disass $pc-32,$pc+32*
Dump of assembler code for function ff_pred8x8_top_dc_neon:
0x00398b74 ff_pred8x8_top_dc_neon+0:
Lars Hammarstrand lars.hammarstrand@... writes:
Success, --disable-neon and -cpuflags -neon did the trick!
I hoped you would first test -cpuflags -neon on
a build with --enable-neon and then --disable-neon
without any cpuflags - sorry for being unclear!
Ok, I'll test that too!
Lars Hammarstrand lars.hammarstrand@... writes:
Initially I want to run the fully automated git
bisect run.
It appears that you know much more about
bisecting FFmpeg than I do. If you report
the first failing commit here on this
mailing list I will forward it to the
bug tracker / the
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
It appears that you know much more about
bisecting FFmpeg than I do. If you report
the first failing commit here on this
mailing list I will forward it to the
bug tracker / the relevant developers.
Lars Hammarstrand lars.hammarstrand@... writes:
Ok, can you please confirm I'm at the correct starting point:
$ git bisect good 3c5fe5b
Only you can answer if 3c5fe5b works ok, if it does,
please test a1bcc76.
(In case this is not obvious: Because of the
peculiarities of the FFmpeg
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
Ok, can you please confirm I'm at the correct starting point:
$ git bisect good 3c5fe5b
Only you can answer if 3c5fe5b works ok, if it does,
please test a1bcc76.
My fault, sorry I was unclear:
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
For the bisect, please confirm first that 3c5fe5b
does indeed work fine (this corresponds to 0.10
and is the first of 14 compiles).
Then please test a1bcc76.
If it works ok, test 3860e34, if not try 35894eb
(These are compiles two and three.)
0.
I'll start a bisect run now just for testing...
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
Result from bisect run where bad=n2.1 and good=3c5fe5b:
Run Status: ffmpeg-bec180e: OK.
Run Status: ffmpeg-3860e34: OK.
Run Status: ffmpeg-353dbaa: Failed. (rc=132)
Run Status: ffmpeg-230bef0: Failed. (rc=132)
Run Status: ffmpeg-f2c49da: Failed. (rc=132)
Run Status: ffmpeg-e98fab1: Failed.
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
Please test 353dbaa now.
If 353dbaa works ok, please test 6b2e650
If 353dbaa does not work, please test 230bef0
If you tested 6b2e650 and if works ok please test 6b8f211
If you tested 6b2e650 and if does not work, test 5361f49
Only if you tested
2013/4/3 Lars Hammarstrand lars.hammarstr...@gmail.com
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
Please test 353dbaa now.
If 353dbaa works ok, please test 6b2e650
If 353dbaa does not work, please test 230bef0
If you tested 6b2e650 and if works ok please test 6b8f211
If you tested 6b2e650
2013/4/3 Lars Hammarstrand lars.hammarstr...@gmail.com
Result from bisect run where bad=n2.1 and good=3c5fe5b:
Run Status: ffmpeg-bec180e: OK.
Run Status: ffmpeg-3860e34: OK.
Run Status: ffmpeg-353dbaa: Failed. (rc=132)
Run Status: ffmpeg-230bef0: Failed. (rc=132)
Run Status:
Lars Hammarstrand lars.hammarstrand@... writes:
Run Status: ffmpeg-d0b7e83: Failed. (rc=132)
Run Status: ffmpeg-8bee8f7: OK.
Does --disable-thumb fix the crashes?
(Or --enable-thumb?)
In any case: Please run your configure line for
both above versions and post the diff for the
following two
2013/4/3 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
Run Status: ffmpeg-d0b7e83: Failed. (rc=132)
Run Status: ffmpeg-8bee8f7: OK.
Does --disable-thumb fix the crashes?
(Or --enable-thumb?)
In any case: Please run your configure line for
both
Lars Hammarstrand lars.hammarstrand@... writes:
(gdb) disass $pc-32,$pc+32
Please add the register dump, some developers can
see the problem if it is present.
Thank you, Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
2013/4/2 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
Tested to run ffmpeg (the tool) and it crashes every
time exactly on the same spot as xbmc!
Thank you for testing!
You are welcome! :-)
Has n1.2 ever been tested on IOS?
Did you test it
2013/4/2 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
(gdb) disass $pc-32,$pc+32
Please add the register dump, some developers can
see the problem if it is present.
http://pastebin.com/vCBCJ719
___
Lars Hammarstrand lars.hammarstrand@... writes:
Could you run the testsuite (make SAMPLES=path fate) on the
iPhone? This would allow to verify if only H264 is affected
or also other codecs.
4. Sorry, you have to be a bit more specific on this one
since I'm not a ffmpeg core developer.
2013/4/2 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
Could you run the testsuite (make SAMPLES=path fate) on the
iPhone? This would allow to verify if only H264 is affected
or also other codecs.
4. Sorry, you have to be a bit more specific on
Lars Hammarstrand lars.hammarstrand@... writes:
(I will open a ticket if all information is available,
Great, here are some additional configure flags.
Please tell me if you need anything else to open a ticket!
Please test if --disable-neon and -cpuflags -neon fix
the problem.
I've no
Lars Hammarstrand lars.hammarstrand@... writes:
but please test if -cpuflags -neon
or --disable-neon helps.
Forgot to ask. Do any of these flags replace any
other flags or should they be used in conjunction
with existing configure flags as below?
--enable-neon
I suspect it is not a
On Tue, Apr 02, 2013 at 08:38:18PM +0200, Lars Hammarstrand wrote:
2013/4/2 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
(gdb) disass $pc-32,$pc+32
Please add the register dump, some developers can
see the problem if it is present.
2013/3/30 Alex Cohn alexc...@netvision.net.il
On 30 Mar 2013 02:32, Lars Hammarstrand lars.hammarstr...@gmail.com
wrote:
1. XBMC is stopping at:
ff_pred8x8_128_dc_neon: (libavcodec/arm/h264pred_neon.S)
0x5bc84: cdpeq p15, #5, c15, c0, c0, #4 -- Thread 3:
EXC_BAD_INSTRUCTION
Lars Hammarstrand lars.hammarstrand@... writes:
Not all iOS devices are born equal in terms of
their ARM core. Which device crashed for you with
bad instruction at
vmov.i8 q0, #128
This function has been unchanged for three years.
If this really is a regression,
Does anyone knows if there is a working version of VLC for iOS
(iphone/ipad) based on ffmpeg v1.1 or later? (googled quite a bit but
couldn't find any useful info...) . /Lars.
___
Libav-user mailing list
Libav-user@ffmpeg.org
Lars Hammarstrand lars.hammarstrand@... writes:
If this really is a regression, please consider
using git bisect to find the version introducing
it. (This isn't trivial with FFmpeg, but I will
support you.)
Ok, thanks - although I believe it will be a quite
lengthy and cumbersome
2013/3/30 Carl Eugen Hoyos ceho...@ag.or.at
Lars Hammarstrand lars.hammarstrand@... writes:
If this really is a regression, please consider
using git bisect to find the version introducing
it. (This isn't trivial with FFmpeg, but I will
support you.)
Ok, thanks - although I
On 30 Mar 2013 20:35, Lars Hammarstrand lars.hammarstr...@gmail.com
wrote:
If the crash is reproducible with FFmpeg, you don't need xbmc to test.
Sounds very good, but how? With the ffmpeg tools (ffplay, etc) as a
stand alone package directly on ios?
Exactly. This makes search for the
On Sat, Mar 30, 2013 at 10:55 PM, Lars Hammarstrand
lars.hammarstr...@gmail.com wrote:
Bad news, it seems that ffplay is not supported on ios, just ffprobe ffmpeg
and ffserver
I would say that ffmpeg that takes your h264 input file and converts
to image2 should be just fine, as long as the
Hi!
We (at xbmc) are having problems with the new ffmpeg n1.2 libs on IOS
(ref: XBMC
work in Progress FFmpeg v1.1
...http://forum.xbmc.org/showthread.php?tid=156303pid=1380678#pid1380678
).
I did a test drive with https://github.com/kolyvan/kxmovie but it seems to
suffer from the same problem. I
On 30 Mar 2013 02:32, Lars Hammarstrand lars.hammarstr...@gmail.com
wrote:
1. XBMC is stopping at:
ff_pred8x8_128_dc_neon: (libavcodec/arm/h264pred_neon.S)
0x5bc84: cdpeq p15, #5, c15, c0, c0, #4 -- Thread 3:
EXC_BAD_INSTRUCTION (code=EXC_ARM_UNDEFINED, subcode=0xe50ff80)
0x5bc88: svclt
48 matches
Mail list logo
