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
FC(1) General Commands Manual FC(1)
NAME
fc - frontend script to the f2c fortran compiler
SYNOPSIS
/usr/bin/fc [-o objfile] [-c] [-S] [-C] [-u] [-w] [-w66] [-D switch] [-I includepath] [-Ntnnn] [-P] files [-l library]
DESCRIPTION
fc is a script intended to be used as a front end to the f2c FORTRAN-to-C translator. It is supposed to make the whole f2c and C compiler
setup look like a real Fortran compiler.
File arguments with a .f suffix are compiled as Fortran source. Files with a .F suffix are passed through the C preprocessor cpp(1) first.
Files with .c (C source) or .s (assembly source) suffixes are passed to the C compiler directly. Files with a .e suffix are treated as efl
source files, and files with a .r suffix are treated as RATFOR source files.
OPTIONS
-o objfile
Produce an output executable named objfile rather than using the default name a.out.
-c Do not call the linker; instead, leave relocatable object files as *.o.
-S Produce assembly output as file.s
-C Compile in extra code to check that array subscripts are in bounds.
-l library
Libraries specified with this option are passed to the linker.
-U def Definitions specified with this option are passed to C compiler (for .c files) or to cpp (for .F files) to remove definition.
-u Complain about undeclared variables.
-v, --version
Print version of f2c in use
-w Omit all warning messages.
-w66 Omit Fortran 66 (Fortran IV) compatibility warning messages.
-D switch
The given switch is passed to the C compiler (for .c files), to cpp (for .F files) and to f2c.
-I includepath
Passed to the C compiler (for .c files), to cpp (for .F files) and to f2c.
-Ntnnn Allow nnn entries in table t.
-P Emit .P files.
BUGS
fc isn't really very good -- try fort77 (1), which does a better job.
This manual page isn't really very good either...
AUTHOR
S. Feldman, D. Gay, M. Maimone, N, Schryer are all mentioned in the paper on the conversion of Fortran to C.
Peter Maydell (pmaydell@chiark.greenend.org.uk) wrote this manual page, and Alan Bain (alanb@chiark.greenend.org.uk) made some minor modi-
fications.
SEE ALSO
f2c(1), fort77(1), cc(1), cpp(1), ratfor(1)
May 1999 FC(1)