I'd like to create a target named "debug" or something similar which will use some special optimization flags useful when debugging (for example -ggdb). At the moment my makefile is neat (which I like) and looks like
Code:
SRC = $(wildcard *.cxx)
OBJ = $(SRC:.cxx=.o)
INCDIR = -I.
LIB = -lm
[Code]....
I have problems with linking object files.
This is what I get:
If I would normal compile using the following line:
Code:
Where should those library flags go in a makefile? Say I having the following makefile:
Code:
all: ${PROGS}
clean:
We have a 32-bit SLES build server and we compile our 32-bit application on top of it. Our target is 32-bit SLES.Now want to change our target to 64-bit SLSE and keep the application 32-bit, do we need change the build server to 64-bit and recompile the application with some flags? OR can we use the 32-bit binaries compiled on 32-bit SLES build server?We use g++ compiler. It would be great if any Linux Guru can give me the steps to be followed.
View 1 Replies View RelatedWe have a 32-bit SLES build server and we compile our 32-bit application on top of it. Our target is 32-bit SLES.
Now, if we want to change our target to 64-bit SLSE and keep the application 32-bit, do we need change the build server to 64-bit and recompile the application with some flags? OR can we use the 32-bit binaries compiled on 32-bit SLES build server?
We use g++ compiler. It would be great if any Linux Guru can give me the steps to be followed.
I'm learning about how to write Makefiles, and am a bit lost at how to run a command in a target depending on the value of a variable.
What I'm trying to do, is run "strip" only if the user is running a given version of a C compiler.
Here's the code:
Code:
$(LUA_T): $(LUA_O) $(LUA_A)
$(CC) -o $@ $(MYLDFLAGS) $(LUA_O) $(LUA_A) $(LIBS)
#FDPIC ELF binaries can be stripped, but not FLAT binaries
$(if($(CROSS),bfin-linux-uclibc-),
$(STRIP) $@
;)
Does someone know the correct way to do this?
Code:
anisha@linux-p0mg:~> uname -r && cat /etc/*release
2.6.25.5-1.1-pae
openSUSE 11.0 (i586)
VERSION = 11.0
My small Makefile:
Code:
obj-m += serialPortISR.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
Errors I receive:
Code:
anisha@linux-p0mg:~/Desktop/serialPortISR_31_10_09> make
make -C /lib/modules/2.6.25.5-1.1-pae/build M=/home/anisha/Desktop/serialPortISR_31_10_09 modules
make[1]: Entering directory '/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory '/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make: *** [all] Error 2
I want to gave much details as possible. working directory (~/a1/shell) in the shell directory i have Makefile. also in the shell directory i have subdirectory's (obj, src, include)
My current Makefile
Quote:
#What needs to be built to make all files and dependencies
clean:
# End of Makefile
I wanted it so: all .o files are created in the obj subdirectory, and my application, sshell, is created in the shell directory.
I am getting this error when i run the make run: No rule to make target 'shell.h', needed by 'shutil.o'. stop
I have ~200 c files in my makefile[$(SRCS)], and it compiles all of the files using a single gcc command. So each time I make a change in one c file, it ends up re-compiling all the files, then linking to make the
binary. How can I break out the compilation into individual gcc commands for each c file, so that make checks the timestamp and accordingly compiles only the modified files.
My current Makefile looks like this.
clean:
I am dealing with one FORTRAN 90 code, have made small changes.
milenko@milenkons:~/mt4$ make mt4
make: 'mt4' is up to date.
milenko@milenkons:~/mt4$ ifort -c MT2DDIB1.FOR
milenko@milenkons:~/mt4$ make mt4
make: 'mt4' is up to date.
milenko@milenkons:~/mt4$ make mt4
make: 'mt4' is up to date.
milenko@milenkons:~/mt4$ make mt4
make: 'mt4' is up to date.
I go for make command but it does not see that the source code has been modified.Than I do compilation from command line,try make again but no use.
F95=ifort
FFLAFGS= -O1
mt3: driver_mt2ddi.o constants.o settings.o params.o mt2dmod.o fdsystem.o mt2ddat.o mt2dsens.o
$(F95) -o $(FFLAGS) mt3 constants.o settings.o params.o mt2dmod.o fdsystem.o mt2ddat.o mt2dsens.o driver_mt2ddi.o
driver_mt2ddi.o: driver_mt2ddi.for constants.o settings.o params.o mt2dmod.o fdsystem.o mt2ddat.o mt2dsens.o
$(F95) -c $(FFLAGS) driver_mt2ddi.for
I am having an error during my Oracle 11g R2 installation on Fedora 13 that I couldn't get rid of or fix it, and I just continued the installation by clicking on the continue button to skip this error. The error message on the alert window is:
Error in invoking target 'agent nmhs' of makefile '/u01/app/oracle/product/11.2.0/dbhome_1/sysman/lib/ins_emagent.mk'. See '/u01/app/oraInventory/logs/installActions2010-06-24_03-22-15PM.log' for details.
and here is the contenets (error part) of the installActions2010-06-24_03-22-15PM.log file
INFO: /usr/bin/ld: /u01/app/oracle/product/carried(nmectlt.o): undefined reference to symbol 'B_DestroyKeyObject'
/usr/bin/ld: note: 'B_DestroyKeyObject' is defined in DSO /u01/app/oracle/product/11.2.0/dbhome_1/lib/libnnz11.so so try adding it to the linker command line
/u01/app/oracle/product/11.2.0/dbhome_1/lib/libnnz11.so: could not read symbols: Invalid operation
[code]....
i m trying to install glib on my pc but i was always encounter a probelem in make. it says "No Target Specified No Makefile Found Stop"
[code]...
I am executiong a instruction, ADD CX, BX ;which affects the (carry flag) CF =1
Now, my question is when (CF =0) it will be reset ?
Is there any constrains for other flags/instruction to reset FLAGS?
I cannot seem to find any good documentation on the role of flags -Bdynamic and -Bstatic in g++. The man pages are not very helpful either.I found an example on the web:"gcc object1.o object2.o -Wl,-Bstatic -lapplejuice -Wl,-Bdynamic -lorangejuice -o binary".According to which -Bstatic instructs the linker to statically link
the applejuice library and to dynamically link the orangejuice library. If orangejuice uses the applejuice library anywhere however,the applejuice is also linked dynamically. Is it correct to assume that this is correct and describes the true functionality of those two flags in gcc? (ie: Bstatic and Bdynamic are used for mixing static and shared libraries during linking)Is it correct to assume that the same applies to g++ as well?
I have written a regular expression (tested in regexpal and regextester alpha something) with which I want to replace something like code...
but it only matches functions which occupy one line only, despite my tests showing multiple line matching in javascript testers online and using the m and s flags (which should make it multi line no?)
I am writing a C program which is contains Mysql header files and APIs but it can not compile it and its error is : Quote: undefined reference to
to all of Mysql APIs that I included their headers .In command line I compile my source like this with no problem: Quote: gcc test.c -Wall -o test -lz `mysql_config --cflags --include --libs`
I think code block does not have bold italic part of this command. How can I add this to code block to compile my project or those project that contains Mysql APIs (just my project not all of defined projects that has no relation to mysql APIs)with this gcc flags.
I am writing a C program which is contains Mysql header files and APIs but it can not compile it and its error is :
Quote:
undefined reference to
to all of Mysql APIs that I included their headers .In command line I compile my source like this with no problem:
Quote:
gcc test.c -Wall -o test -lz `mysql_config --cflags --include --libs`
I think code block does not have bold italic part of this command. How can I add this to code block to compile my project or those project that contains Mysql APIs (just my project not all of defined projects that has no relation to mysql APIs)with this gcc flags.
I just downloaded slackware 13.1(x86) and i'm trying to compile ndiswrapper-1.56 using the slackbuild from slackbuils.org and i'm getting this error:
Code:
Makefile:535: /usr/src/linux-2.6.33.4/arch/i486/Makefile: No such file or directory
make[2]: *** No rule to make target `/usr/src/linux-2.6.33.4/arch/i486/Makefile'. Stop.
make[1]: *** [modules] Error 2
make: *** [all] Error 2
looks like the folder i486 doesn't exist
When compiling a C program i get the following errors.How do i modify the code to remove these warning messages?
1) "test.c", line 614: warning #4212-D: mismatch between character pointer
types "unsigned char *" and "char *"
p_data = m_lines[p_text_idx];
[code]....
i am working with ad hoc network but the problem is not getting any good documentation of how to compile c++ code then how to add the code into Tcl intrepreter and how to work with make file. i want to run my own algorithm using c++ and then want to incorporate it into tcl interpreter and then want to run.
View 2 Replies View RelatedI want to define _LINUX in my makefile which I would be using in my source code like #if _Linux. I do not want to #define _Linux __linux__ in my source code.
View 2 Replies View Relatedat present I compile the same code for different systems (cross compilers)I need to call libs and include paths for the different processors. At present I simply comment out the paths not needed
eg
#INCDIR = -I/cross1/.......
#INCDIR = -I/cross2/.......
[code]....
I want to run ISCSI target on CentOS. Both "scsi-target-utils" and "iscsi-target" can be used.
They seem to have the same function.
Is there any significant difference between them, on performance or stability?
I wish to know that which gcc release version had support on ARM 9 multicore system by using pthread library for its parallelizing method on ecos rtos.I assume that the compiler that support the single ARM 9 processor will surely compile its multicore version also.But i need a clarification about it.It is good if you give a article or provide a suitable link on the ARM multicore programming and its compilation method
View 1 Replies View RelatedI have got following code from a book:
Code:
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <string.h>
#include <stdlib.h>
#define PORTNUMBER 12345
[Code]...
I had been working on a CPP code for sometime now, without being aware that some parts of its code, especially security related were not being compiled. Problem was like my product did not work for SSL mode. On analysis, I found that some part of CPP codes inside a switch(ENABLE_SSL_LIBRARY)were not getting compiled at all. And also that this gets set when we do newgrp crypto command on the box. This left me without lots of doubts. I wanted to understand how these switches work and if this switch was propreitary to my code or something related to Linux.
My questions now are:
1. Switches like the one mentioned above, are they user defined, for my particular code or are they related to Linux/GCC or makefiles?
2.If a user can define such switches to control code compilation, then need to know the concepts/procedures behind it. How is it done ?
Kindly excuse if these are very very basic. But since I could not get proper stuffs on google, I thought I should ask some experts here who could either explain me or point me to appropriate resources (links of articles / tutorials)
I am a beginner in Linux. Never did any kernel programming in Linux/Windows before. I am now on a project and I am supposed to understand a Linux Device Driver Code. It contains 6 .c files and 1 Makefile.
The make file goes as this:
I have a.c b.c c.c d.c d.c e.c f.c in the director along with the Makefile mentioned.
I am using Fedora Red Hat Linux 32 bit.
How to compile the Makefile.
How to create a simple Makefile using C....
View 3 Replies View RelatedI'm trying to figure out how Make handles directories.
How can I modify this makefile so it will put all of the .o files in a separate build directory?
Code:
But make ignores this and still puts main.o in the base directory. And if I refer to the build directory in the dependencies for bandit, make complains about "no rule ..."
I want to keep main.cpp in the base directory, all other sources in the src directory, and all object files in the build directory.
When I put a "test" target in my Makefile containing
Code:
@echo "CXX= $(CXX)"
it tells me "CXX= g++".
But I have nothing in the Makefile assigning any value to CXX, and as far as I can tell I have no CXX environment variable (no "CXX" appears when I run the shell command "env", and "echo $CXX" returns a blank line. So where's the g++ value coming from. Is this just built into Gnu Make, or is there a configuration file for make somewhere?