bugmake - Bugs: bug #1608, ordering problem: target-specific...

 
 

bug #1608: ordering problem: target-specific vars and conditionals

Submitted by:  Invalid User ID <Invalid User ID>
Submitted on:  Mon 04 Nov 2002 05:16:36 PM UTC  
 
Severity: 3 - NormalItem Group: Bug
Status: Not A BugPrivacy: Public
Assigned to: NoneOpen/Closed: Closed
Component Version: 3.80Operating System: POSIX-Based
Fixed Release: NoneTriage Status: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Mon 04 Nov 2002 05:28:51 PM UTC, comment #1:

It's not a design glitch: it's intentional and a direct consequence of make's two-pass approach to reading makefiles. When make reads the makefile it will resolve all preprocessor statements like "ifeq", etc. At that time, obviously, there is no target being built so there is no target-specific values in scope.

Target-specific values are only valid within the command script for the target; see the GNU make manual.

Paul D. Smith <psmith>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Mon 04 Nov 2002 05:28:51 PM UTCpsmithStatusNone=>(Error - Not Found)
  Open/ClosedOpen=>(Error - Not Found)

Back to the top


Powered by Savane 3.1-cleanup1