Summary: | replace nasm with yasm+nasm_symlink | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mr. Bones. (RETIRED) <mr_bones_> |
Component: | [OLD] Development | Assignee: | Mr. Bones. (RETIRED) <mr_bones_> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | ansla80, binki, gentoo, vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mr. Bones. (RETIRED)
![]() I came across this bug randomly. It seems all upstream bugs but #125 and #126 are fixed, and Yasm 0.7.0 has just been released. But since NASM is once again maintained and active, is this necessary? Well, if nasm continues to be maintained then maybe not, but so far yasm seems to be where the mind share has gone. We'll see. (In reply to comment #1) > I came across this bug randomly. It seems all upstream bugs but #125 and #126 > are fixed, and Yasm 0.7.0 has just been released. Update: It seems only #126 is open now (checked only #125 and #126 as per your comment). meh. nasm development seems viable. status quo it is. |