The following packages have been uploaded to the Cygwin distribution:
* ffmpeg-6.0-1
* libavutil58-6.0-1
* libavcodec60-6.0-1
* libavformat60-6.0-1
* libavdevice60-6.0-1
* libavfilter9-6.0-1
* libswscale7-6.0-1
* libswresample4-6.0-1
* libpostproc57-6.0-1
* libavutil-devel-6.0-1
* libavcodec
On 19/06/16 22:51, Brian Mathis wrote:
Is there any reason not to use the native Windows build instead? What
does the cygwin port gain you over that?
Other that the obvious difference of Windows and POSIX paths, there will
be differences in the way the two versions of ffmpeg are built. This
tools to understand
POSIX paths.
>
>
> On Thu, Jun 16, 2016 at 12:02 PM, David Stacey wrote:
>> On 16/06/16 13:49, Marco Atzeri wrote:
>>>
>>> On 16/06/2016 14:44, Václav Haisman wrote:
>>>>
>>>> Hi.
>>>>
>>>> I have
> Hi.
>>>
>>> I have noticed a lack of ffmpeg and/or libav and associated tools on
>>> Cygwin. It would be nice to have them.
>>>
>>> But I am not going to try and package them, sorry. :)
>>>
>>
>> same reason as fedora...
>>
&g
On 16/06/16 13:49, Marco Atzeri wrote:
On 16/06/2016 14:44, Václav Haisman wrote:
Hi.
I have noticed a lack of ffmpeg and/or libav and associated tools on
Cygwin. It would be nice to have them.
But I am not going to try and package them, sorry. :)
same reason as fedora...
http
On 16/06/2016 14:44, Václav Haisman wrote:
Hi.
I have noticed a lack of ffmpeg and/or libav and associated tools on
Cygwin. It would be nice to have them.
But I am not going to try and package them, sorry. :)
same reason as fedora...
http://rpmfusion.org/FAQ#Why_doesn
Hi.
I have noticed a lack of ffmpeg and/or libav and associated tools on
Cygwin. It would be nice to have them.
But I am not going to try and package them, sorry. :)
--
VH
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
On Wed, Apr 17, 2013 at 11:06 AM, wrote:
>
> HOW CAN CYGWIN capture W32 Programs WinSTD out as minty and putty do?
>
> I am use several programs that are native windows compiled, such as
> ffmpeg. I am writing a sheel script to get video clip information
> provided by ffmpeg, b
HOW CAN CYGWIN capture W32 Programs WinSTD out as minty and putty do?
I am use several programs that are native windows compiled, such as
ffmpeg. I am writing a sheel script to get video clip information
provided by ffmpeg, but I can't capture the screen output which
(probably isn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've tried a number of variations wrt configure, the latest is a
near-copy of the one used for the cygport version (which I can't use,
missing libvpx support), but I can't get past an early compilation
failure:
CC libavformat/4xm.o
In file includ
On 15/10/2009 11:38, Dave Korn wrote:
Do you have a STC using just qmake itself so that I only have to build a
single package to try and track this down? e.g. does it fault just on
startup, can I just run "qmake --help" and reproduce the problem?
Yes, even qmake --help segfaults.
If you do
t on libstdc++6 is segfaulting. Not just
>>> MPlayer/FFmpeg (which dep libdirac, a C++ library), but anything based
>>> on Qt/KDE, WebKit, Poppler, etc.
>>
>> Not only that, but rebuilding Qt3 from scratch, qmake still segfaults
>> (and qmake itself depends onl
Ping?
On 06/10/2009 19:34, Yaakov (Cygwin/X) wrote:
On 05/10/2009 23:03, Yaakov (Cygwin/X) wrote:
Just updated to cygwin-1.7.0-62 and gcc4-4.3.4-1 tonight, and it appears
*anything* (sub-)dependent on libstdc++6 is segfaulting. Not just
MPlayer/FFmpeg (which dep libdirac, a C++ library), but
On 05/10/2009 23:03, Yaakov (Cygwin/X) wrote:
Just updated to cygwin-1.7.0-62 and gcc4-4.3.4-1 tonight, and it appears
*anything* (sub-)dependent on libstdc++6 is segfaulting. Not just
MPlayer/FFmpeg (which dep libdirac, a C++ library), but anything based
on Qt/KDE, WebKit, Poppler, etc.
Not
. (There appears to be something else buggy on head that was
confounding my efforts to test a fix.)
Just updated to cygwin-1.7.0-62 and gcc4-4.3.4-1 tonight, and it appears
*anything* (sub-)dependent on libstdc++6 is segfaulting. Not just
MPlayer/FFmpeg (which dep libdirac, a C++ library), but
On Thu, Oct 01, 2009 at 11:01:03PM -0500, Yaakov (Cygwin/X) wrote:
>On 01/10/2009 19:52, Dave Korn wrote:
>>Correction: the fixes in the snapshot are sufficient for now, and will
>> allow
>> mplayer to work. (There appears to be something else buggy on head that was
>> confounding my efforts
On 01/10/2009 19:52, Dave Korn wrote:
Correction: the fixes in the snapshot are sufficient for now, and will allow
mplayer to work. (There appears to be something else buggy on head that was
confounding my efforts to test a fix.)
There is still I think a potential loophole that we just ha
Dave Korn wrote:
> Yaakov (Cygwin/X) wrote:
>> On 01/10/2009 17:06, Dave Korn wrote:
>
>> Do you mean more back-compat fixes are necessary beyond that in the
>> 2009-09-20 snapshot?
>
> Yep, fraid so.
Correction: the fixes in the snapshot are sufficient for now, and will allow
mplayer to wor
Yaakov (Cygwin/X) wrote:
> On 01/10/2009 17:06, Dave Korn wrote:
> Do you mean more back-compat fixes are necessary beyond that in the
> 2009-09-20 snapshot?
Yep, fraid so.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.c
Cygwin. The DLLs it links against are not affected
by this problem, so only the actual mplayer package needs a rebuild.
>
(I can't say whether or not that also applies to ffmpeg; it might need some
of its DLLs updated as well, or you can hang on until I've got the back-compat
fix
Nathan Thern wrote:
> On Wed, Sep 30, 2009 at 12:23 PM, Dave Korn wrote:
>> Nathan Thern wrote:
>>> Yaakov-
>>> I thought I would bring this to your attention ...
>> Compiler problems are always worth reporting on the main list too!
>>
>>> I just di
Nathan Thern wrote:
> On Wed, Sep 30, 2009 at 12:23 PM, Dave Korn
> wrote:
>> Nathan Thern wrote:
>>> Yaakov-
>>> I thought I would bring this to your attention ...
>> Compiler problems are always worth reporting on the main list too!
>>
>>
On Wed, Sep 30, 2009 at 12:23 PM, Dave Korn
wrote:
> Nathan Thern wrote:
>> Yaakov-
>> I thought I would bring this to your attention ...
>
> Compiler problems are always worth reporting on the main list too!
>
>> I just discovered that ffmpeg and mplayer are segfa
On 14/07/2009 11:47, Dave Korn wrote:
ffmpeg is one thing that's likely to suffer from the COMMON alignment
problem very badly, to the extent that I used it as a testcase when I
developed the support for the new feature, and I have a nicely working version
on my PC:
Without suppor
Yaakov (Cygwin/X) wrote:
> Dave,
Hi Yaakov,
> I have been having some difficulties building the latest ffmpeg with
> gcc-4.3.2-2; the build would complete but the resulting binaries
> wouldn't launch due to the dreaded, ever-so-helpful C005
> initialization error. B
Dave,
I have been having some difficulties building the latest ffmpeg with
gcc-4.3.2-2; the build would complete but the resulting binaries
wouldn't launch due to the dreaded, ever-so-helpful C005
initialization error. Building with gcc-3.4 worked just fine, as it has
for some ti
26 matches
Mail list logo
