public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/28242]  New: running the testsuite with -fstack-protector does fail
@ 2006-07-04  7:17 debian-gcc at lists dot debian dot org
  2006-07-04 14:41 ` [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp) pinskia at gcc dot gnu dot org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: debian-gcc at lists dot debian dot org @ 2006-07-04  7:17 UTC (permalink / raw)
  To: gcc-bugs

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


-- 
           Summary: running the testsuite with -fstack-protector does fail
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: debian-gcc at lists dot debian dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28242


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp)
  2006-07-04  7:17 [Bug testsuite/28242] New: running the testsuite with -fstack-protector does fail debian-gcc at lists dot debian dot org
@ 2006-07-04 14:41 ` pinskia at gcc dot gnu dot org
  2010-05-20 18:27 ` ro at gcc dot gnu dot org
  2010-05-21  1:53 ` hjl dot tools at gmail dot com
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-07-04 14:41 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2006-07-04 14:40 -------
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. 


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-07-04 14:40:54
               date|                            |
            Summary|running the testsuite with -|running the testsuite with -
                   |fstack-protector does fail  |fstack-protector fail (not
                   |                            |finding libssp)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28242


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp)
  2006-07-04  7:17 [Bug testsuite/28242] New: running the testsuite with -fstack-protector does fail debian-gcc at lists dot debian dot org
  2006-07-04 14:41 ` [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp) pinskia at gcc dot gnu dot org
@ 2010-05-20 18:27 ` ro at gcc dot gnu dot org
  2010-05-21  1:53 ` hjl dot tools at gmail dot com
  2 siblings, 0 replies; 4+ messages in thread
From: ro at gcc dot gnu dot org @ 2010-05-20 18:27 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from ro at gcc dot gnu dot org  2010-05-20 18:26 -------
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.


-- 

ro at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ro at gcc dot gnu dot org
           Severity|enhancement                 |normal
      Known to fail|                            |4.6.0
   Last reconfirmed|2006-07-04 14:40:54         |2010-05-20 18:26:55
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28242


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp)
  2006-07-04  7:17 [Bug testsuite/28242] New: running the testsuite with -fstack-protector does fail debian-gcc at lists dot debian dot org
  2006-07-04 14:41 ` [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp) pinskia at gcc dot gnu dot org
  2010-05-20 18:27 ` ro at gcc dot gnu dot org
@ 2010-05-21  1:53 ` hjl dot tools at gmail dot com
  2 siblings, 0 replies; 4+ messages in thread
From: hjl dot tools at gmail dot com @ 2010-05-21  1:53 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from hjl dot tools at gmail dot com  2010-05-21 01:53 -------


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


-- 

hjl dot tools at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28242


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-05-21  1:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-07-04  7:17 [Bug testsuite/28242] New: running the testsuite with -fstack-protector does fail debian-gcc at lists dot debian dot org
2006-07-04 14:41 ` [Bug testsuite/28242] running the testsuite with -fstack-protector fail (not finding libssp) pinskia at gcc dot gnu dot org
2010-05-20 18:27 ` ro at gcc dot gnu dot org
2010-05-21  1:53 ` hjl dot tools at gmail dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).