879259 – net-libs/nodejs[pax-kernel]: PaX marking is broken since at least 15.11.0

Bug 879259 - net-libs/nodejs[pax-kernel]: PaX marking is broken since at least 15.11.0

Summary: net-libs/nodejs[pax-kernel]: PaX marking is broken since at least 15.11.0

Status:	RESOLVED INVALID

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	William Hubbs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2022-11-03 06:10 UTC by Tom Li
Modified:	2022-11-13 16:50 UTC (History)
CC List:	0 users

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

Attachments
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 Tom Li 2022-11-03 06:10:20 UTC

On a PaX-enabled system, when I was trying to upgrade to 15.11.0 years ago, I noticed the pax_kernel flag was broken and caused build failure due to incomplete PaX marking. After troubleshooting, the required markings were:

out/Release/mksnapshot_u            m
out/Release/mkcodecache_u           m
out/Release/node_mksnapshot_u       m
out/Release/genccode                m

Today I was attempting to upgrade to net-libs/nodejs-18.11.0 (now with pax-kernel instead of pax_kernel flag), and I noticed the same problem still exists. Thus, the "pax-kernel" flag in almost all currently available nodejs ebuilds are broken.

Comment 1 Tom Li 2022-11-13 16:50:08 UTC

Mysteriously, this problem went away after another attempt to reinstall net-libs/nodejs-18.11.0 for reproducing the problem... Perhaps my system's paxmark.sh was simply broken? Apologize for the noise. Close as INVALID.