350527 – sys-apps/memtest86+-4.10 gets compiled with CFLAGS="-Wall -march=i486 -m32 -O2 -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC -fno-stack-protector -m32"

Bug 350527 - sys-apps/memtest86+-4.10 gets compiled with CFLAGS="-Wall -march=i486 -m32 -O2 -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC -fno-stack-protector -m32"

Summary: sys-apps/memtest86+-4.10 gets compiled with CFLAGS="-Wall -march=i486 -m32 -O...

Status:	RESOLVED WONTFIX

Alias:	None

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

Importance:	High normal
Assignee:	Michal Januszewski (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-01-04 11:55 UTC by Justin Lecher (RETIRED)
Modified:	2011-01-06 20:19 UTC (History)
CC List:	1 user (show)

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 Justin Lecher (RETIRED) gentoo-dev

2011-01-04 11:55:51 UTC

The Makefile hardcodes these CFLAGS. Is there a reason not to replace them by users choice?

Comment 1 Michal Januszewski (RETIRED) gentoo-dev

2011-01-06 20:19:03 UTC

The short answer is "yes". memtest86 provides a standalone binary that is executed instead of the standard kernel in order to test the RAM.  The priority there is to make sure the tests are executed reliably, and allowing user-defined CFLAGS will not bring any more stability.

Due to the specific nature of the binary being built, there is a higher than usual potential of breaking things if other CFLAGS are used.  Note for example the -m32 flag -- the memtest code is designed to be compiled in 32-bit mode.