740132 – >=sys-cluster/singularity-3: build failure with 'V=1' present in MAKEOPTS

Bug 740132 - >=sys-cluster/singularity-3: build failure with 'V=1' present in MAKEOPTS

Summary: >=sys-cluster/singularity-3: build failure with 'V=1' present in MAKEOPTS

Status:	RESOLVED CANTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Marek Szuba (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2020-09-03 05:56 UTC by Agostino Sarubbo
Modified:	2020-09-03 14:36 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
build.log (build.log,11.81 KB, text/plain) 2020-09-03 05:56 UTC, Agostino Sarubbo	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Agostino Sarubbo gentoo-dev

2020-09-03 05:56:49 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sys-cluster/singularity-3.6.1 fails to compile.
Discovered on: amd64 (internal ref: ci)

NOTE:
This machine uses GLIBC-2.32. If you think that this issue is strictly related to GLIBC please block bug 736174.

Comment 1 Agostino Sarubbo gentoo-dev

2020-09-03 05:56:52 UTC

Created attachment 657998 [details]
build.log

build log and emerge --info

Comment 2 Marek Szuba (RETIRED) archtester

2020-09-03 14:36:59 UTC

This is because the Tinderbox value of MAKEOPTS sets V=1, which conflicts with upstream use of that variable (empty for verbose mode, '@' for terse mode). Documentation explicitly states about MAKEOPTS "Use  this variable if you want to use parallel make", therefore it is my opinion that using this variable to pass arbitrary arguments to make is done at one's own risk.