[FFmpeg-user] I need your help again.

Jimmy Asher jasher at safarimontage.com
Fri Nov 13 14:18:55 CET 2015


for clarity:

About ffmpeg-user	

"This list is for regular user questions like compilation troubles, command-line issues and similar. Please provide your ffmpeg command(s) and complete, uncut, unscripted console output(s) when possible."


________________________________________
From: ffmpeg-user [ffmpeg-user-bounces at ffmpeg.org] on behalf of Moritz Barsnick [barsnick at gmx.net]
Sent: Friday, November 13, 2015 8:15 AM
To: FFmpeg user discussions
Subject: Re: [FFmpeg-user] I need your help again.

On Fri, Nov 13, 2015 at 13:47:55 +0100, Reindl Harald wrote:
> honestly i find the "this and that is not supported here" arrogant
> because this is a *users-list* and so it's not a matter what you or any
> ffmpeg developer supports just because there may be another ordinary
> user with expierience how to solve a problem you don't care about

While I often agree, I find it amusing that you tell that into my face
and not someone else's. ;-)

Okay, so let me add the description of why I came to this conclusion
(in this case):
I tried to have a look at what this log file says, and a lot of it
looks bogus to me. clang is complaining about a lot of things, such as
trying to build for two architectures at the same time.

I had to go find the upstream of this script (the user didn't mention
it, so he could have used some arbitrary github branch of it), find the
script which probably created this configure line, and wonder why it's
using these flags and iPhoneOS9.1.sdk to build for x86 (just because
I'm not yet aware of iOS on x86, though Apple is certainly always
looking at second-sourcing its mobile processors). There may be a
reason for that, but we would have to ask both the user and the author
of the script about their intentions. Likely the former didn't have
any.

But I have a hard time telling it to someone who a) was not responsible
for this script, and b) doesn't understand it (the script, or the
scenario) anyway.

As I didn't see ANYTHING caused by ffmpeg's ./configure (IMO) which may
have led to this mess, I think the script's authors are much better in
helping to explain and resolve. But feel free to offer your help if you
can make sense of it. ;-)

Again, I too don't like the way things are put off on this list, or
answered very briefly where a few lines more would have given a more
concise explanation. I try to do the latter.

Moritz :)
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user at ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user


More information about the ffmpeg-user mailing list