When I look at the g++ and gcc man pages, I don’t see how the GNU compilers would accept arguments like »–as-needed« or what appears to be libraries seperated by semicolons (»-lavcodec;-lavfilter;-lavformat;-lavutil;-lswscale;-lswresample;-lpostproc« just looks out of place to me).
My usual gcc/g++ invocations are admittedly far simpler than your build, for example:
… so I may be missing the finer points of what may be possible with gcc command-line params, but I suspect there might be some prior magic in your build process (a ./configure or pkgconfig run) that went arwry. Do you have any log files lying around of prior successful builds for reference?
[Edited to add: I just learned that »-Wl,–as-needed« is a linker flag, nevermind…]
I am building the same was as the other binary addons in the project. It was building fine until 7 days ago, but I cannot find a commit in the GIT that is causing this error. But as I am no developer I think I am overseeing something. That is why I opened this thread.
IMO your problem is the part O highlighted in red …
I assume it’s not one of those others that are listed immediately after what I highlighted.
You have to determine if your codec is there or if not why (assuming you don’t have a permissions problem).
Hi
This is on OBS, building and any permissions issues are not a problem (abuild/abuild), it maybe on install if no buildroot is specified, but not build…
As pointed out, the user has not read the upstream build instructions/requirements which may be part of the issue.
I understand,
But was just trying to cover all bases for the type of error whenever it occurs.
Permissions would never be an issue in any dedicated build environment, it only happens for instance building on a private machine that might need to set permissions for different uses.