From: Cyrill G. <gor...@gm...> - 2018-06-24 16:43:07
|
On Sun, Jun 17, 2018 at 7:19 PM Cyrill Gorcunov <gor...@gm...> wrote: > > On Sun, Jun 17, 2018 at 05:43:26PM +0200, bal...@un... wrote: > > hello > > > > I don't know if this is actually a problem with nasm or ffmpeg: so > > apologies if I am reporting to the wrong list > > > > The problem is with the current nasm rc version 2.14rc5 (so something > > which is still to be officially released); I'm sending this just as a > > possible heads up for the nasm developers... > > > > While building the latest official ffmpeg release (ffmpeg-4.0.1), > > using nasm-2.14rc5 I get: > > > > Thanks a lot for report! Better to file a bug of course but I'll > take a look on the week. Sorry for delay. I finally spotted the bad commit (98578071b9d71ecaa2344dd9c185237c1765041e). Gonna figure out what exactly is happening. Thanks again for report! |