[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #35132] Side effects of .SECONDARY with no targets not documented
From: |
anonymous |
Subject: |
[bug #35132] Side effects of .SECONDARY with no targets not documented |
Date: |
Tue, 20 Dec 2011 22:07:22 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.106 Safari/535.2 |
URL:
<http://savannah.gnu.org/bugs/?35132>
Summary: Side effects of .SECONDARY with no targets not
documented
Project: make
Submitted by: None
Submitted on: Tue 20 Dec 2011 10:07:20 PM UTC
Severity: 3 - Normal
Item Group: Documentation
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Component Version: 3.82
Operating System: POSIX-Based
Fixed Release: None
Triage Status: None
_______________________________________________________
Details:
There are some side effects associated with intermediate/secondary targets
that aren't documented in any real detail in the documentation.
The documentation for .SECONDARY gives the impression you can use .SECONDARY
to disable automatic deletion of intermediate targets, but doing so causes a
number of side effects that produce unpredictable behavior in a build.
Unfortunately, I do not have a concise or publishable example demonstrating
the problem; however, I outlined it on this thread:
http://groups.google.com/group/gnu.utils.bug/browse_frm/thread/d882703f60b20ea5?hl=en#
-Brian
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35132>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #35132] Side effects of .SECONDARY with no targets not documented,
anonymous <=