public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: chastain@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/3550: "touch" still in libiberty/Makefile.in, gcc/mklibgcc.in
Date: Tue, 03 Jul 2001 14:46:00 -0000 [thread overview]
Message-ID: <20010703213955.8757.qmail@sourceware.cygnus.com> (raw)
>Number: 3550
>Category: bootstrap
>Synopsis: "touch" still in libiberty/Makefile.in, gcc/mklibgcc.in
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jul 03 14:46:03 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Michael Chastain
>Release: gcc 3.0
>Organization:
>Environment:
native solaris 2.7
>Description:
gcc/Makefile.in does not use the the "touch" command because of bugs with nanosecond time stamps on native solaris 2.7 and native solaris 2.8.
Hoever, libiberty/Makefile.in and gcc/mklibgcc.in still have "touch" commands in them.
I have seen unreproducible build failures which look like the fault of "touch".
See:
http://gcc.gnu.org/ml/gcc/2001-05/msg00487.html
http://gcc.gnu.org/ml/gcc/2001-06/msg01558.html
>How-To-Repeat:
I can't squeeze a reproducible failure out of this.
>Fix:
Change libiberty/Makefile.in and gcc/mklibgcc.in to use a different command to make timestamp files,
just as gcc/Makefile.in uses a $(STAMP) command.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-07-03 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 14:46 chastain [this message]
2003-05-14 8:36 Dara Hazeghi
2003-05-14 8:46 Dara Hazeghi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010703213955.8757.qmail@sourceware.cygnus.com \
--to=chastain@redhat.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).