46697 – sys-devel/gcc-3.3.3 has faulty glibc_have_ssp() on amd64

Bug 46697 - sys-devel/gcc-3.3.3 has faulty glibc_have_ssp() on amd64

Summary: sys-devel/gcc-3.3.3 has faulty glibc_have_ssp() on amd64

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal (vote)
Assignee:	AMD64 Project

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-04-03 09:30 UTC by Danny van Dyk (RETIRED)
Modified:	2004-04-03 17:37 UTC (History)
CC List:	1 user (show)

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

Attachments
Patch for sys-devel/gcc-3.3.3.ebuild to allow proper check whether __guard and __stack_smash_handler reside in libc.so.6 (gcc-3.3.3-amd64-ssp-borkage.diff,265 bytes, patch) 2004-04-03 09:32 UTC, Danny van Dyk (RETIRED)	Details \| Diff
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 Danny van Dyk (RETIRED) gentoo-dev

2004-04-03 09:30:03 UTC

The current implementation of glibc_have_ssp() on amd64 is borked. It seems to be only a typo. Patch attached that solves compilation problems with CFLAGS containing "-fstack-protector" for me. BTW: Can't that conditional construct for amd64 inside this subroutine be wiped out ? libc.so.6 resides in /lib/ on amd64 as well because /lib is a symlink to /lib64 on amd64...

Comment 1 Danny van Dyk (RETIRED) gentoo-dev

2004-04-03 09:32:09 UTC

Created attachment 28624 [details, diff]
Patch for sys-devel/gcc-3.3.3.ebuild to allow proper check whether __guard and __stack_smash_handler reside in libc.so.6

Comment 2 Jon Portnoy (RETIRED) gentoo-dev

2004-04-03 17:37:34 UTC

Killed that construct, thanks.