04-13-2018
Duplicate thread.
Continue
here.
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
cd(1) General Commands Manual cd(1)
NAME
cd - change working directory
SYNOPSIS
[directory]
DESCRIPTION
If directory is not specified, the value of shell parameter is used as the new working directory. If directory specifies a complete path
starting with or directory becomes the new working directory. If neither case applies, tries to find the designated directory relative to
one of the paths specified by the shell variable. has the same syntax as, and similar semantics to, the shell variable. must have execute
(search) permission in directory.
exists only as a shell built-in command because a new process is created whenever a command is executed, making useless if written and pro-
cessed as a normal system command. Moreover, different shells provide different implementations of as a built-in utility. Features of as
described here may not be supported by all the shells. Refer to individual shell manual entries for differences.
If is called in a subshell or a separate utility execution environment such as:
(which invokes on accessible directories) does not affect the current directory of the caller's environment. Another usage of as a stand-
alone command is to obtain the exit status of the command.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multi-byte character code sets are supported.
Environment Variables
The following environment variables affect the execution of
The name of the home directory,
used when no directory operand is specified.
A colon-separated list of pathnames that refer to directories.
If the directory operand does not begin with a slash character, and the first component is not dot or dot-dot, searches
for directory relative to each directory named in the variable, in the order listed. The new working directory is set
to the first matching directory found. An empty string in place of a directory pathname represents the current direc-
tory. If is not set, it is treated as if it was an empty string.
EXAMPLES
Change the current working directory to the directory from any location in the file system:
Change to new current working directory residing in the current directory:
or
Change to directory residing in the current directory's parent directory:
Change to the directory whose absolute pathname is
Change to the directory relative to home directory:
RETURN VALUE
Upon completion, exits with one of the following values:
The directory was successfully changed.
An error occurred. The working directory remains unchanged.
SEE ALSO
csh(1), pwd(1), ksh(1), sh-posix(1), sh(1), chdir(2).
STANDARDS CONFORMANCE
cd(1)