Login or Register to Ask a Question and Join Our Community


Programming

Problem with a Makefile

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Programming Problem with a Makefile
# 8  
Old 11-22-2008
Finally I found the problem
Finally I get the answer.
The solution is to put -Aa, -D_HPUX_SOURCE

I guess the problem come when you put the -Aa option in the Makefile, because that makes tha cc to ignore some libraries that are needed in the new code.

From the man of cc:
Requests a compilation in ANSI C mode. The -Aa option requests
a strict implementation of ANSI C. ANSI C specifies which names
are available in the standard libraries and headers, which are
reserved for the implementation, and which must be left available
for you. HP C in ANSI mode conforms to these restrictions and
only names permitted by ANSI C are defined or declared in the
standard libraries and headers. Macro definitions can be used to
access names that are normally defined in other standards

Any way thanks to the people of the forum, specially to Corona688 for the help.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Problem running a makefile

I have written this makefile and am getting an error saying make nfd gfortran -O -Wall -fbacktrace -fno-align-commons -c -o fd.o fd.f fd.f:49: Error: Can't open included file 'fd.par' make: *** Error 1 The directory structure is as follows . ├── library │ ├── fd │ │ ├──... (3 Replies)
Discussion started by: kristinu
3 Replies

2. Programming

Problem creating a makefile

hello, I'm trying to create a makefile to run multiple c files. I am able to run one c file only with the code I have when I tried to run 2 or more c files I'm not able. here is my code # $Source: /home/hectormasencio/make/Makefile,v $ # $Date: 2012/11/27 11:35:30 $ CC= gcc OBJS= temp.o... (3 Replies)
Discussion started by: Hector M.
3 Replies

3. Emergency UNIX and Linux Support

Problem With Makefile

I had created a Makefile for my project. my project file hierarchy is like this: 1. a source folder with main.c and Makefile in it 2. and a top level Makefile here is the Makefile in src folder all: program program: main.c gcc -o program main.c clean: rm programand here is top... (3 Replies)
Discussion started by: majid.merkava
3 Replies

4. Programming

Noob makefile problem

Im trying to build a makefile for the first time in many years and Im coming to a screaching halt on something that should be child's play; just compiling two files. Here is an excerpt of the make file. (using GMAKE on a TI compiler) CCHP = <<compiler>> PROJ_DIR = . APP_DIR ... (2 Replies)
Discussion started by: DrNismo
2 Replies

5. Programming

Problem with Makefile

Hi, Here is my makefile http://pastie.org/1104332. I am trying to compile different .c files and .s files (assembly files) from different sub directories into E:/em35x/build/mfg-sample-app-cortexm3-iar-em357-em3xx-dev0680/ then the linker should link all the .o files from the build directory... (1 Reply)
Discussion started by: blade2008
1 Replies

6. Programming

please help me with this big makefile problem

I need to create an executable with these two makefiles(they both have libaries i need(qt and ruby)) i have extconf.rb gui.ui gui_include.h main.cpp ScaleIM_client.rb ui_gui.h i want to combine them all into one executable please!... (2 Replies)
Discussion started by: gjgfuj
2 Replies

7. UNIX for Advanced & Expert Users

Makefile problem - How to run module load in a Makefile

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

8. Programming

Simple Makefile Problem (with a dependency)

Hi all, I have 4 '.cpp' files and 1 header files: Tools.cpp Code1.cpp Code2.cpp Code3.cpp and Tools.hh Now all Code1.cpp, Code2.cpp, Code3.cpp use functions stored in Tools.cpp. Currently, what I do to compile all of them is using this simple shell script: (1 Reply)
Discussion started by: monkfan
1 Replies

9. Programming

Problem with makefile

My make file is CFLAGS = -Wall -g LDFLAGS = -lm CC = g++ all: server client rc4.o: rc4.cpp rc4.h ${CC} ${CFLAGS} -c rc4.cpp server.o: server.cpp rc4.h ${CC} ${CFLAGS} -c .cpp client.o: client.cpp rc4.h ${CC} ${CFLAGS} -c client.cpp server: server.o... (2 Replies)
Discussion started by: neerajgoyal12
2 Replies

10. UNIX for Advanced & Expert Users

problem with Makefile

Hi, I have a makefile which looks like this ProcessA : commands touch pro1 ProcessB : pro1 commands touch pro2 ProcessC: pro3 commands and after some runs, i wish only pro3 to run and I check that "pro1" and "pro2" are there in the directory, but still, if i give make... (3 Replies)
Discussion started by: sskb
3 Replies
Login or Register to Ask a Question

LEARN ABOUT OSX

md

md(1)							    BSD General Commands Manual 						     md(1)

NAME

     md -- process raw dependency files produced by cpp -MD

SYNOPSIS

     md [-d] [-f] [-m makefile] [-u makefile] [-o outputfile] [-v] [-x] [-D c|d|m|o|t|D]

DESCRIPTION

     The md command basically does two things:

     Process the raw dependency files produced by the cpp -MD option.  There is one line in the file for every #include encountered, but there are
     repeats and patterns like .../dir1/../dir2 that appear which should reduce to .../dir2.  md canonicalizes and flushes repeats from the depen-
     dency list.  It also sorts the file names and "fills" them to a 78 character line.

     md also updates the makefile directly with the dependency information, so the .d file can be thrown away (see d option).  This is done to
     save space.  md assumes that dependency information in the makefile is sorted by .o file name and it procedes to merge in (add/or replace [as
     appropriate]) the new dependency lines that it has generated.  For time efficiency, md assumes that any .d files it is given that were cre-
     ated before the creation date of the "makefile" were processed already.  It ignores them unless the force flag [f] is given.

FLAG SUMMARY

     -D c|D|d|m|o|t
	     Specify debugging option(s):

	     c	     show file contents

	     D	     show very low level debugging

	     d	     show new dependency crunching

	     m	     show generation of makefile

	     o	     show files being opened

	     t	     show time comparisons

     -d      Delete the .d file after it is processed

     -f      Force an update of the dependencies in the makefile, even if the makefile is more recent than the .n file.  (This implies that md has
	     been run already.)

     -m makefile
	     Specify the makefile to be upgraded.  The defaults are makefile and then Makefile.

     -o outputfile
	     Specify an output file (other than a makefile) for the dependencies.

     -u makefile
	     Like -m, but the file will be created if necessary.

     -v      Set the verbose flag.

     -x      Expunge old dependency information from the makefile.

SEE ALSO

     make(1)

BUGS

     Old, possibly not used by anyone.

HISTORY

     The md utility was written by Robert V. Baron at Carnegie-Mellon University.

BSD
								   June 2, 2019 							       BSD