04-13-2018
How to call .sh file from makefile.am?
in this bin_SCRIPTS = doEcho.sh this command is not working,
$(shell ./doEcho.sh ) this is also not working then how to execute it?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have learned native compilation of basic c code example programs from the net.
The issue is, .c code file doesn't come with respective Makefile.
Visited some web sites with Makefile manuals but still can not master writing Makefile file to work.
The idea is to have intelligent shell... (5 Replies)
Discussion started by: darius2
5 Replies
2. 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
3. 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
4. Shell Programming and Scripting
I'm writing a VERY simple shell script. I need to call a makefile in a subdirectory. What's the command I need to use?
./dir/make and ./dir/makefile doesn't work.
Thanks in advance (1 Reply)
Discussion started by: yamahabob
1 Replies
5. Shell Programming and Scripting
Hi,
I'm having a lot of trouble with a Makefile I am trying to make. I think it is a basic principles issue. When I try to make, I get the error a
buildfiles/bin/serial.o file not found error
And I have gone over this code multiple times. Based on the compiler, I believe the way I... (2 Replies)
Discussion started by: cciarleg
2 Replies
6. Programming
Hi guys,
I am writing a Makefile with some strange features.
What I have is:
list of files *.efi
list of guids (guid is just a number)
one *.efi file is supposed to be used with one guid, so efi file and guid is a pair.
What I need is:
list of files *.fv
How to make *.fv file... (1 Reply)
Discussion started by: Chrisdot
1 Replies
7. Programming
Hi there,
I have, in my application, one Makefile that generates a .a file. I would like to generate .a and binary executable in the same Makefile. This is possible?
Thank you! (2 Replies)
Discussion started by: cayo
2 Replies
8. Shell Programming and Scripting
I've created a tag in the makefile:
mytag: $(shell ${PWD}/script.sh)
When i do: make clean - the script is executed
When i perform make or make mytag the script is again executed with the output:
make: Nothing to be done for mytag
What i want ?
I want script.sh to be executed only... (0 Replies)
Discussion started by: Pufo
0 Replies
9. Solaris
I am new to Solaris and compilation using make files.
I have a code base which is organized into different folders. At the root folder is a master make file and in the sub directories, there are make files for that particular folder.
In the make files present in subdirectories, I am seeing... (2 Replies)
Discussion started by: rajujayanthy
2 Replies
10. UNIX for Beginners Questions & Answers
I have used $(shell ./doEcho.sh) and also tried bin_SCRIPTS = doEcho.sh but it is not working it is compiling but not executing.
I have kept mkdir filename in doEcho.sh (2 Replies)
Discussion started by: srikanth007
2 Replies
PWD(1) BSD General Commands Manual PWD(1)
NAME
pwd -- return working directory name
SYNOPSIS
pwd [-L | -P]
DESCRIPTION
The pwd utility writes the absolute pathname of the current working directory to the standard output.
Some shells may provide a builtin pwd command which is similar or identical to this utility. Consult the builtin(1) manual page.
The options are as follows:
-L Display the logical current working directory.
-P Display the physical current working directory (all symbolic links resolved).
If no options are specified, the -L option is assumed.
ENVIRONMENT
Environment variables used by pwd:
PWD Logical current working directory.
EXIT STATUS
The pwd utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
builtin(1), cd(1), csh(1), sh(1), getcwd(3)
STANDARDS
The pwd utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
BUGS
In csh(1) the command dirs is always faster because it is built into that shell. However, it can give a different answer in the rare case
that the current directory or a containing directory was moved after the shell descended into it.
The -L option does not work unless the PWD environment variable is exported by the shell.
BSD
April 12, 2003 BSD