31790 – Compiling gradm failed when hardened-gcc was not installed

Bug 31790 - Compiling gradm failed when hardened-gcc was not installed

Summary: Compiling gradm failed when hardened-gcc was not installed

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Unspecified (show other bugs)
Hardware:	All Linux

Importance:	High normal
Assignee:	solar (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-10-22 21:10 UTC by Stephen Cook
Modified:	2003-11-08 22:49 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 Stephen Cook 2003-10-22 21:10:14 UTC

Compiling gradm (1.9.12) failed when hardened-gcc was not installed.  But when
hardened-gcc is installed then it compiles perfectly

Reproducible: Always
Steps to Reproduce:
1. make sure hardened-gcc is not installed
2. install gradm
3.

Actual Results:  
did not compile

Expected Results:  
There needs to be dep in gradm for hardened-gcc

Comment 1 solar (RETIRED) gentoo-dev

2003-10-23 08:42:46 UTC

I don't think that's right.

gradm should never have to depend on hardened-gcc, infact the two are not
even compatible as gradm will link as static no matter what.
I've been told that linking static is a requirement of gradm by (Brad spender@grsecurity.net)

I've unmerged hardened-gcc over here and rebuilt gradm-1.9.12 four times
here with various set of CFLAGS without a single error.

Now what is very possible here is there might be some underlying gcc bugs
(gcc-3.3.x) with static linking that get fixed by pappy's hgcc specs.

What version of gcc are you running with?

I'll keep this bug open for a few days, but I think the end resolution will
be marked as INVALID.

Comment 2 solar (RETIRED) gentoo-dev

2003-11-08 22:49:06 UTC

changing resolution to INVALID