public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/55083] New: failure while configuring libatomic is not cleaned up
@ 2012-10-26 14:53 pedzsan at gmail dot com
  2012-10-26 15:14 ` [Bug bootstrap/55083] " pinskia at gcc dot gnu.org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: pedzsan at gmail dot com @ 2012-10-26 14:53 UTC (permalink / raw)
  To: gcc-bugs


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

             Bug #: 55083
           Summary: failure while configuring libatomic is not cleaned up
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: pedzsan@gmail.com


If something fails during the configuration phase of libatomic, a subsequent
"make" will take a different path and not complete the configure processing.

The error can be seen in the configure-target-libatomic: code of Makefile.in
(at the top directory).  Midway down, if the directory exists, exit 0 is
called.  If it does not exist, then it is created and configure for libatomic
is called.  But if configure fails, the directory is not removed.  Subsequent
"make" will assume that everything had been configured.


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

end of thread, other threads:[~2012-12-09  5:40 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-26 14:53 [Bug c/55083] New: failure while configuring libatomic is not cleaned up pedzsan at gmail dot com
2012-10-26 15:14 ` [Bug bootstrap/55083] " pinskia at gcc dot gnu.org
2012-10-26 15:31 ` pedzsan at gmail dot com
2012-12-09  2:24 ` pinskia at gcc dot gnu.org
2012-12-09  4:46 ` pedzsan at gmail dot com
2012-12-09  5:07 ` pinskia at gcc dot gnu.org
2012-12-09  5:40 ` pedzsan 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).