[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug #3403] Memory effect on GNUmakefile ?
From: |
nobody |
Subject: |
[Bug #3403] Memory effect on GNUmakefile ? |
Date: |
Wed, 30 Apr 2003 09:57:05 -0400 |
=================== BUG #3403: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3403&group_id=99
Submitted by: yjchen Project: GNUstep
Submitted on: Wed 04/30/2003 at 09:56
Category: Makefiles Severity: 5 - Major
Bug Group: Bug Resolution: None
Assigned to: None Status: Open
Summary: Memory effect on GNUmakefile ?
Original Submission: It seems to be a bug, but I'm not sure.
If files is changed in GNUmakefile from C_FILES to OBJC_FILES
and file extension is changed from .c to .m,
without 'make distclean', it will complain that
the old .c file doesn't exist even the GNUmakefile is updated.
It memorizes the old GNUmakefile in this case.
I use these two files for testing.
GNUmakefile:
include $(GNUSTEP_MAKEFILES)/common.make
# The application to be compiled
TOOL_NAME = Test
# The Objective-C source files to be compiled
Test_OBJC_FILES = main.m
# The C source files to be compiled
Test_C_FILES =
include $(GNUSTEP_MAKEFILES)/tool.make
main.m:
int main(int argc, const char **argv)
{
printf("Test\n");
return 0;
}
Compile these two files. Then 'mv main.m main.c',
and change GNUmakefile to include the new main.c in C_FILES
(and comment out OBJC_FILES)
Compile again will complain the old main.m doesn't exist.
Only after 'make distclean' will make it work
No Followups Have Been Posted
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3403&group_id=99
- [Bug #3403] Memory effect on GNUmakefile ?,
nobody <=