12-26-2019
Quote:
g++ -c -o echo.o echo.cpp
g++ -c -o src/Server.o src/Server.cpp
You collect object files without connecting the path to the header
You need to explicitly write -I/home/vagrant/libuv/include for a compilation of these objects
thanks @Neo
I deal with the task for a long time and did not reload the page
Last edited by nezabudka; 12-26-2019 at 10:48 AM..
10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I got a make compilation error saying
make: *** No rule to make target `/usr/include/iso/stdio_iso.h', needed by `.test.d'. Stop.
The mentioned folder `/usr/include/iso/' doesnt exist in solaris5.7 sparc that i am using.
I need to know which package will actually install the... (1 Reply)
Discussion started by: Nads
1 Replies
2. Shell Programming and Scripting
I wonder if the script below is possible to write somehow more efficiently. It seems to me the problem is very common..
CreateFolders() # parameter: name of file with relative path with regard to directory $project_root
{
echo $1 | awk '{ n=split($1, array, "/");
... (2 Replies)
Discussion started by: MartyIX
2 Replies
3. Shell Programming and Scripting
..... (2 Replies)
Discussion started by: mercury
2 Replies
4. Linux
Hi all
I want to compile a source gt_util.c into a lo file,
I use
libtool gcc -g -O -c gt_util.c -I./include
but it prompts me :
cannot determin name of library object from 'include'
how should I use the tool to compile a source to .lo file?
Thanks. (0 Replies)
Discussion started by: steven_TTG
0 Replies
5. Programming
How do i check if a path exists in C? (5 Replies)
Discussion started by: omega666
5 Replies
6. Shell Programming and Scripting
Hi All,
In make file i want to include header files from my local directory and if it did not find in local directory i want to include from network directory. can any help me how i can do this?.
here is the code
INCLUDE=${include}/
this is point to network dir how i can add option that it... (1 Reply)
Discussion started by: goraya430
1 Replies
7. UNIX for Dummies Questions & Answers
I would like to modify my .profile PATH to include all subdirectories of the directory I specify. For example, right now I have
PATH=$HOME/tier1
Tier1 has a tier2 directory in it. Right now I can execute files from tier1, but not tier2. I know I can add another path with $HOME/tier1/tier2,... (1 Reply)
Discussion started by: Smed
1 Replies
8. Shell Programming and Scripting
I need to pull down a good bit of files for another support team for an upgrade project. I have a server.list with all of the server names.
I need to do two parts:
FIRST:
I have this example, but it does not list the server name in front of each line.
#! /bin/bash
for server in $(<... (10 Replies)
Discussion started by: asnatlas
10 Replies
9. AIX
Hi,
I not familiar with MPIO pathing those stuffs!
Can any one please tell me ONE FC card can hold how many paths?
I have a stand alone server, where TWO fc card has been configured,
In one card i am getting ie., fsci0 im getting 4paths
Another card i am getting ie., fsci2 im gettin... (4 Replies)
Discussion started by: Thala
4 Replies
10. Shell Programming and Scripting
I use the below command with echo $? to determine if a file path exists.
ls /app/weblogic/myserver4/logs/`hostname`/data/proc.pid
Output:
/app/weblogic/myserver4/logs/myhostseven/data/proc.pid
The problem is that I have both AIX and Linux systems.
On some servers hostname is either... (6 Replies)
Discussion started by: mohtashims
6 Replies
ALEF(1) General Commands Manual ALEF(1)
NAME
8al, kal, val - ALEF compilers
SYNOPSIS
8al [ option ... ] [ file ... ]
kal [ option ... ] [ file ... ]
val [ option ... ] [ file ... ]
DESCRIPTION
ALEF is a concurrent programming language with a syntax like C's. Kal, val and 8al compile the named ALEF source files into SPARC, MIPS
and Intel 386 object files. Source files have the extension .l. The ALEF source is passed through cpp(1) prior to compilation. Object
files have the normal extension for each architecture: .k for SPARC, .v for MIPS and .8 for 386. Up to $NPROC files will be compiled in
parallel.
The compiler options are:
-o obj Place output in file obj (ignored if there is more than one input file). Default is to take the last element of the input pathname,
strip any trailing .l, and append the object file suffix.
-a Write no object file, but produce an acid(1) program on standard output, comprising a set of type declarations and functions to
print those types.
-aa Like -a but suppress output for types and functions declared in header files.
-w Print warning messages for non fatal errors.
-N Do not run the code optimizer.
-c Do not compile code for check statements.
-S Produce assembly language instead of object code as output. By default, output goes to a file named by the last element of the
input pathname with .l replaced by .s.
-Dname=def
-Dname Define the name to the preprocessor, as if by If no definition is given, the name is defined as
-Idir files whose names do not begin with are always sought first in the directory of the file argument, then in directories named in -I
options, then in /sys/include/alef, and finally in /$objtype/include/alef.
-dc Produce various forms of debugging. The character c is an alphabetic.
The compiler recognizes several #pragma directives. The first, #pragma lib, is the same as in 2c(1). The others have effect only when
profiling is turned on by the -p option of the loader (see 2l(1)). The directive #pragma noprofile disables the generation of profiling
code for subsequently declared functions; #pragma profile enables it again. The main use of these directives is to avoid the profiling
confusion caused by functions that do not explicitly return, such as the task-switching functions in the run-time system. Nonetheless,
without support for profiling multi-process programs, it remains difficult to profile Alef programs.
EXAMPLE
To compile and run on a SPARC the ALEF program in the current directory:
kal -w *.l
kl *.k
k.out
FILES
/sys/include/alef
directory for #include files.
/$objtype/lib/alef
directory for ALEF libraries
SOURCE
/sys/src/alef/port
machine-independent part
/sys/src/alef/8, etc.
machine-dependent parts
SEE ALSO
acid(1), 2a(1), 2l(1), mk(1), nm(1), db(1)
Phil Winterbottom, ``Alef Reference Manual'', and Bob Flandrena, ``Alef User's Guide''.
ALEF(1)