Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 842666

Summary: media-video/ffmpeg-4.4.1-r5 build failure: 1sed command not found
Product: Gentoo Linux Reporter: Luca Santarelli <luca.santarelli>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED INVALID    
Severity: normal CC: floppym
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: complete build log
emerge --info
emerge -pqv

Description Luca Santarelli 2022-05-05 06:56:42 UTC
Created attachment 776828 [details]
complete build log

Upgrading media-video/ffmpeg to 4.4.1-r5 fails during build with a weird error: "1sed: command not found".

The failing command happens during the build and seems to be setting the MAJOR version in a .ver file that will be used later in the build:

1sed 's/MAJOR//' /var/tmp/portage/media-video/ffmpeg-4.4.1-r5/work/ffmpeg-4.4.1/libavutil/libavutil.v | cat > libavutil/libavutil.ver

I have tried to understand the error by looking at the makefiles, but I have been unable to determine its cause.
Comment 1 Luca Santarelli 2022-05-05 06:57:47 UTC
Created attachment 776831 [details]
emerge --info
Comment 2 Luca Santarelli 2022-05-05 06:59:18 UTC
Created attachment 776834 [details]
emerge -pqv
Comment 3 Mike Gilbert gentoo-dev 2022-05-08 00:22:02 UTC
Do you have a variable called "M" set to "1" in your environment?

https://github.com/FFmpeg/FFmpeg/blob/n4.4.1/ffbuild/library.mak#L46
Comment 4 Luca Santarelli 2022-05-08 10:03:01 UTC
Thank you, that was it.

argo-2 ~ # grep "^M" -r /etc/portage/
/etc/portage/env/no-distcc.conf:M=1
/etc/portage/env/no-distcc.conf:MAKEOPTS="-j${N} -l${M}"
/etc/portage/make.conf:MAKEOPTS="-j2"
argo-2 ~ # 

This came from an old Handbook which recommented setting N-jobs and M-load. I see the current handbook has no more mention of N and M variables, I'll adapt my configuration.

Thank you for suggesting it was an environment variable. The bug can be marked as resolved, I don't know if it should be marked as INVALID or something else.