-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove native nasm #6263
base: master
Are you sure you want to change the base?
remove native nasm #6263
Conversation
- remove native nasm, it is a prerequisite in the dev. environment since update to debian 12 - remove native yasm - update related Makefiles
This reverts commit 2c4a9cb.
- change affected packages to trigger build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beside possible issue found with openh264
that your change brought to light, LGTM.
- update cross/dav1d - remove definitions for nasm, meson build completely auto detects nasm
- remove definitions for nasm, meson build completely auto detects nasm - create optimized code
- cmake builds completely auto detect nasm
Special NASM definitions for meson and cmake build systems are obsolete and removed now. further analysis for gcc builds (spksrc.cross-cc.mk) is WIP. |
- disable support for OLD_PPC_ARCHS - build with assembler, except for PPC_ARCHS - remove obsolete configure args --enable-pic is forced with --enable-shared --cross-prefix is not required - remove definition of GNU_CONFIGURE and define --host - simplify definition of gcc as assembler if not using x86asm
- define --as=auto to use yasmm (prefered over nasm) - document why we don't define GNU_CONFIGRE - remove concurring patch - avoid duplicate definition of --disable-neon
ifeq ($(findstring $(ARCH),$(i686_ARCHS)),$(ARCH)) | ||
CONFIGURE_ARGS += --target=x86-linux-gcc | ||
# --as=auto: prefers yasm over nasm | ||
CONFIGURE_ARGS += --as=auto | ||
CONFIGURE_ARGS += --disable-sse4_1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@th0ma7 can you remember why you disabled sse4_1 for intel archs?
it builds just fine without disabling it
@th0ma7 the libraries and *.mk files are ready for review. On the ffmpeg* packages there is some pending work...
|
and the third issue is with even we configure with |
Description
Fixes #
Affected Libraries
Direct dependencies
Further findings
Affected Packages
By direct dependencies
Checklist
all-supported
completed successfullyType of change