Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Reiner Sombrowsky <test@somby.de>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Compiling Error within MSYS2-mingw32-environment
Date: Mon, 27 Feb 2023 09:20:45 +0100
Message-ID: <f5a89fb3-a13f-d67a-cb88-7dc223460448@somby.de> (raw)

Hello *ffmpeg* developers,
I compile *ffmpeg* sources within a *Windows 11 MSYS2*
*mingw64* and *mingw32* environment for using in my
applications that can be downloaded for free
on my homepage***www.somby.de <https://www.somby.de>*.
Since the last 2 months I have problems with compiling
within *mingw32* environment. The compiling within *mingw64*
environment is ok.
I use the *git repository* of *ffmpeg*. My last checked
*HEAD -> master* revision was *ac6eec1fc2*.
Following *MSYS2* packets are installed:
*pacman -S --needed base-devel \**
**          mingw-w64-i686-gcc \**
**          mingw-w64-x86_64-gcc \**
**          mingw-w64-i686-toolchain \**
**          mingw-w64-x86_64-toolchain \**
**          git \**
**          subversion \**
**          mercurial \**
**          mingw-w64-i686-cmake \**
**          mingw-w64-x86_64-cmake \**
**          autoconf \**
**          mingw-w64-i686-gtk3 \**
**          mingw-w64-x86_64-gtk3 \**
**          yasm \**
**          nasm \**
**          perl \**
**          diffutils \**
**          make \**
**          pkgconf \**
**          mingw-w64-i686-SDL2 \**
**          mingw-w64-x86_64-SDL2 \**
**          mingw-w64-i686-ffmpeg \**
**          mingw-w64-x86_64-ffmpeg *


The current versions of
*mingw-w64-i686-gcc* and *mingw-w64-x86_64-gcc* are
*12.2.0-10*.

My current *ffmpeg-configuration* is:
*./configure --enable-gpl \**
**     --enable-libmp3lame \**
**     --enable-libxvid \**
**     --enable-libx264 \**
**     --enable-libx265 \**
**     --enable-libvorbis \**
**     --disable-static \**
**     --enable-shared \**
**     --enable-ffplay \**
**     --disable-debug \**
**     --enable-vulkan \**
**     --enable-version3 \**
**     --enable-opengl \**
**     --prefix="$HOME/ffmpeg_build"*

If I compile within the *mingw32* environment
the following error occurs during *make*:
*...**
**CC      libavcodec/h2645_sei.o**
**CC      libavcodec/h2645_vui.o**
**CC      libavcodec/h2645data.o**
**CC      libavcodec/h264_cabac.o**
**In file included from libavcodec/cabac_functions.h:49,**
**                 from libavcodec/h264_cabac.c:36:**
**In function 'get_cabac_inline_x86',**
**    inlined from 'get_cabac' at libavcodec/cabac_functions.h:145:12,**
**    inlined from 'decode_cabac_mb_intra4x4_pred_mode' at 
libavcodec/h264_cabac.c:1377:9,**
**    inlined from 'ff_h264_decode_mb_cabac' at 
libavcodec/h264_cabac.c:2081:32:**
**libavcodec/x86/cabac.h:199:5: error: 'asm' operand has impossible 
constraints**
**  199 |     __asm__ volatile(**
**      |     ^~~~~~~**
**libavcodec/x86/cabac.h:199:5: error: 'asm' operand has impossible 
constraints**
**libavcodec/x86/cabac.h:199:5: error: 'asm' operand has impossible 
constraints**
**libavcodec/x86/cabac.h:199:5: error: 'asm' operand has impossible 
constraints**
**make: *** [ffbuild/common.mak:81: libavcodec/h264_cabac.o] Error 1*

Perhaps you can fix this error in the
next revisions.

Best regards
Reiner Sombrowsky
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

                 reply	other threads:[~2023-02-27  8:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5a89fb3-a13f-d67a-cb88-7dc223460448@somby.de \
    --to=test@somby.de \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git