Sponsored Content
Top Forums Programming Makefile cannot find separator Post 303026362 by Corona688 on Monday 26th of November 2018 10:21:06 AM
Old 11-26-2018
Quote:
Originally Posted by colt
It works, but it's not using the compiler flags to speedup the code. I realize that the problem is that the flags are in the wrong place, they should be before the .o files are created. I guess I shall put them in the CFLAGS?
Yes.
Quote:
I read somewhere that since the CFLAGS are made to be adjusted by the end-user, it's a bad practice to set them in the Makefile.
Your makefile is less than ten lines, it is easily adjusted by whoever wants it to, as makefiles should be.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Separator in Makefile?

all: $(LIBRARY) $(EXE) $(MAKEMAKE): @rm -f $(MAKEMAKE) $(PURIFY) $(CXX) -M $(INCLUDE) $(CPPFLAGS) *.cpp > $(MAKEMAKE) $(EXE): $(OBJS) $(LIBRARY) @echo "Creating a executable " $(PURIFY) $(CC) -o $(EXE) $(OBJS) $(ALLLDFLAGS) $(LIBS) This is a snippet... (2 Replies)
Discussion started by: laila63
2 Replies

2. UNIX for Dummies Questions & Answers

Help with unix separator

can some one give me a list of unix separtor(s) if one than just the separator please thank you. (2 Replies)
Discussion started by: Black mage2021
2 Replies

3. 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

4. UNIX for Advanced & Expert Users

Makefile executing another Makefile first?

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. UNIX for Dummies Questions & Answers

Issues with Makefile (cannot find )

Hello guys ! Need a bit of help is compiling a code, the makefile for which was originally designed to work on a 32-bit Linux platform, for a 64-bit Linux platform. My platform is Ubuntu 10.04 LTS 64-bit. I am trying to compile a code called csim, file name csim-1.1.tar.gz. To compile this... (0 Replies)
Discussion started by: pbhat
0 Replies

6. Homework & Coursework Questions

Help with Simple Multi-Level Makefile (Extremely New at Makefile)

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

7. UNIX for Dummies Questions & Answers

GCC Makefile-Missing Separator

Hello, I am attempting to build gcc 4.0.4 on my Mac (OS X). When I use the "make" command, it returns with something like this: Makefile:6089: *** missing separator. Stop. This means that at the given line, I must go into the file and insert a TAB before the contents of that line. I have... (1 Reply)
Discussion started by: Tyler_92
1 Replies

8. Shell Programming and Scripting

Find "*.c" and "Makefile" and then delete them with one line

find "*.c" and "Makefile" and then delete them with one line (3 Replies)
Discussion started by: yanglei_fage
3 Replies

9. Shell Programming and Scripting

Field separator

Hello All, I have a file, but I want to separate the file at a particular record with comma"," in the line Input file APPLE6SSAMSUNGS5PRICEPERPIECEDOLLAR600EACH010020340URX581949695US to Output file APPLE6S,SAMSUNGS5,PRICEPERPIECE,DOLLAR600EACH,010020340URX581949695,US This is for... (11 Replies)
Discussion started by: m6248m
11 Replies

10. Shell Programming and Scripting

Separator

Hello everybody, I'll get one more help I have a cabundle file that I need to separate into 2 parts, the first sequence and the second sequence, I thought of several things but I did not remember anything that could actually accomplish this separation and transform into 2 variables, first... (4 Replies)
Discussion started by: c0i0t3
4 Replies
AUTOMAKE(1)						      General Commands Manual						       AUTOMAKE(1)

NAME
automake - automatically create Makefile.in's from Makefile.am's SYNOPSIS
automake [ -a | --add-missing ] [ --amdir=DIR ] [ --build-dir=DIR ] [ -c | --copy ] [ --cygnus ] [ -f | --force-missing ] [ --foreign ] [ --gnits ] [ --gnu ] [ --help ] [ -i | --ignore-deps ] [ --include-deps ] [ --no-force ] [ -o DIR ] [ --output-dir=DIR ] [ --srcdir-name=DIR ] [ -v | --verbose ] [ --version ] [ --Werror | --Wno-error ] DESCRIPTION
To create all the Makefile.ins for a package, run the automake program in the top level directory, with no arguments. automake will auto- matically find each appropriate Makefile.am (by scanning configure.in) and generate the corresponding Makefile.in. Note that automake has a rather simplistic view of what constitutes a package; it assumes that a package has only one configure.in, at the top. If your package has multiple configure.ins, then you must run automake in each directory holding a configure.in. You can optionally give automake an argument; .am is appended to the argument and the result is used as the name of the input file. This feature is generally only used to automatically rebuild an out-of-date Makefile.in. Note that automake must always be run from the topmost directory of a project, even if being used to regenerate the Makefile.in in some subdirectory. This is necessary because automake must scan configure.in, and because automake uses the knowledge that a Makefile.in is in a subdirectory to change its behavior in some cases. automake accepts the following options: -a --add-missing Automake requires certain common files to exist in certain situations; for instance config.guess is required if configure.in runs AC_CANONICAL_HOST. Automake is distributed with several of these files; this option will cause the missing ones to be automatically added to the package, whenever possible. In general if Automake tells you a file is missing, try using this option. By default Automake tries to make a symbolic link pointing to its own copy of the missing file; this can be changed with --copy. --libdir=DIR Look for Automake data files in directory DIR instead of in the installation directory. This is typically used for debugging. -c --copy When used with --add-missing, causes installed files to be copied. The default is to make a symbolic link. --cygnus Causes the generated Makefile.ins to follow Cygnus rules, instead of GNU or Gnits rules. -f --force-missing When used with --add-missing, causes standard files to be rebuilt even if they already exist in the source tree. This involves removing the file from the source tree before creating the new symlink (or, with --copy, copying the new file). --foreign Set the global strictness to foreign. --gnits Set the global strictness to gnits. --gnu Set the global strictness to gnu. This is the default strictness. --help Print a summary of the command line options and exit. -i --ignore-deps This disables the dependency tracking feature. --include-deps This enables the dependency tracking feature. This feature is enabled by default. This option is provided for historical reasons only and probably should not be used. --no-force Ordinarily automake creates all Makefile.ins mentioned in configure.in. This option causes it to only update those Makefile.ins which are out of date with respect to one of their dependents. -o DIR --output-dir=DIR Put the generated Makefile.in in the directory DIR. Ordinarily each Makefile.in is created in the directory of the corresponding Makefile.am. This option is used when making distributions. -v --verbose Cause Automake to print information about which files are being read or created. --version Print the version number of Automake and exit. --Werror --Wno-error --Werror will cause all warnings issued by automake to become errors. Errors affect the exit status of automake, while warnings do not. --Wno-error, the default, causes warning to be treated as warnings only. SEE ALSO
aclocal(1), and the Texinfo documentation for automake AUTHORS
Automake was written primarily by David Mackenzie and Tom Tromey. This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the Debian GNU/Linux automake package. 28 Jan 2002 AUTOMAKE(1)
All times are GMT -4. The time now is 11:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy