04-12-2007
Hi reborg, hmm not sure what you mean by clobber..
So, I execute make once. The object files are built from the source files. The executable is then built from these object files.
Now if I run make again (without changing the source code) Nothing will happen because the files are already up to date and so nothing will be done.
What I want is, on running make again. The object files and the executables are built again.
let me know if this is clear..
10 More Discussions You Might Find Interesting
1. Programming
can anyone well explain how to create a makefile? especially those commands in the makefile?
BTW, what is CFLAG? (2 Replies)
Discussion started by: ligerdave
2 Replies
2. High Performance Computing
I am new to creating makefiles.
I have several fortran programs in a folder called as "test" and also have several subroutines in another folder (which is inside this test folder) called as libry
My makefile is in the folder "test"
I want to create a makefile which can access the files in... (2 Replies)
Discussion started by: explorer
2 Replies
3. UNIX for Advanced & Expert Users
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
Discussion started by: hernandinho
2 Replies
4. UNIX for Advanced & Expert Users
I have 2 libraries in 2 different directories that I build with Makefiles.
library B depends on library A. If I modify a .cpp file in library A and run lib B's Makefile can I have B's makefile to automatically rebuild library A?
I am now rebuilding A, followed by B... but I'd like B to... (0 Replies)
Discussion started by: wwuster
0 Replies
5. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
Discussion started by: Tatl
1 Replies
6. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I have been trying to make the program swap but i have been getting errors with the makefile such as
driver.o:... (1 Reply)
Discussion started by: mgyeah
1 Replies
7. UNIX for Dummies Questions & Answers
I'm really confused how to use a makefile.
Are you supposed to be make a file from emacs called MakeFile and put code in there to compile?
I am trying to create a makefile to compile two .cpp files in my current directory to produce two .o files and then link them...
What I did was make a... (1 Reply)
Discussion started by: jzhang172
1 Replies
8. Shell Programming and Scripting
Dear all,
I have a quite simple question about how to manipulate "makefile.am". I intend to:
1. "CFLAGS" and "CXXFLAGS" have no value at all. I know that these values get "-g -O2" by default. On the other hand, when I try to set them as "CFLAGS = " in "makefile.am", I get warning messages... (4 Replies)
Discussion started by: Dandan
4 Replies
9. UNIX for Dummies Questions & Answers
Hey everybody,
This may be stup*d question for you, but i am new in unix and i wonder how can i make the rules for translating and linking my .c "primjer1.c", "primjer2.c" and "primjer3.c" in makefile.
Thank you. (7 Replies)
Discussion started by: jskako
7 Replies
10. Programming
Hi All,
We have moved our OS from Sun Solaris to Linux and also some of the compilers.
Our old makefile used to be as below:
CC=cc
FLAGS=-G -KPIC -DLG_SOLARIS_OS
DEFINES=-DSunOS
SYSLIBS=-lc
.SUFFIXES : .c
.c.o : ;$(CC) -c $(FLAGS) $(DEFINES) $*.c -o $*.o
... (3 Replies)
Discussion started by: shash
3 Replies
LEARN ABOUT DEBIAN
objdump86
objdump86(1) General Commands Manual objdump86(1)
NAME
objdump86, size86, nm86 - Examine object, archive or executable files
SYNOPSIS
objdump86 [file...]
size86 [file...]
nm86 [file...]
DESCRIPTION
These commands are used to examine the contents of object files. They may also be used to examine archive or executable files. When archive
files are examined each module in the archive will be processed in sequence.
nm86 prints the symbol table in each of the specified files.
size86 displays a summary of the sizes of the segments in each of the files.
objdump86 decodes and displays the contents of the object files specified. This includes the section headers, symbols tables, segment
sizes, and segment contents.
OPTIONS
The programs are not designed to accept any options.
It should be noted that all three of objdump86, size86, and nm86 are implemented as links to the same executable file (called objdump86 in
the source distribution). The result of running this executable is determined by the file name actually used to execute it.
It is possible to force a specific behavior irrespective of the invocation file name using one of the options below
-s Behave like size86.
-n Behave like nm86.
RESTRICTIONS
These commands are intended for use only with the Dev86/ELKS toolchain.
SEE ALSO
as86(1), bcc(1), ld86(1)
AUTHORS
objdump86, size86, and nm86 (C) 1999 Greg Haerr <greg@censoft.com>.
COPYRIGHT
The manual page was written for Debian GNU/Linux, (C) 2006 Shyamal Prasad <shyamal@member.fsf.org>. It is distributed under the terms of
the GNU General Public License version 2 (or any later version released by the Free Software Foundation).
May, 2006 objdump86(1)