Bug 28242 - running the testsuite with -fstack-protector fail (not finding libssp)
Summary: running the testsuite with -fstack-protector fail (not finding libssp)
Status: RESOLVED DUPLICATE of bug 32064
Alias: None
Product: gcc
Classification: Unclassified
Component: testsuite (show other bugs)
Version: 4.1.2
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks: 17464
  Show dependency tree / graph
 
Reported: 2006-07-04 07:17 UTC by Debian GCC Maintainers
Modified: 2010-05-21 01:53 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail: 4.6.0
Last reconfirmed: 2010-05-20 18:26:55

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 Debian GCC Maintainers 2006-07-04 07:17:23 UTC 
running the testsuite with -fstack-protector fails if no libssp.* is installed in a system path, or the ssp libraries from the system path are used, if they are found.

  Matthias
Comment 1 Andrew Pinski 2006-07-04 14:40:54 UTC 
Confirmed, what should happen is we should add the build library directory to the library path if -fstack-protector is supplied.  I think adding  -lmudflap -fmudflap has the same issue.
Comment 2 Rainer Orth 2010-05-20 18:26:55 UTC 
This is not an enhancement, but simply a bug: the testsuite should use the built
libraries, not some version that happens (or not) to be installed on the system.
Comment 3 H.J. Lu 2010-05-21 01:53:20 UTC 

*** This bug has been marked as a duplicate of 32064 ***