10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I get this error,
defaults.cpp: In member function ‘int Defaults::GetIntDefault(const std::string&)’:
defaults.cpp:68: error: ‘atoi’ was not declared in this scope
defaults.cpp: In member function ‘real_t Defaults::GetRealDefault(const std::string&)’:
defaults.cpp:76: error: ‘atof’ was not... (1 Reply)
Discussion started by: bstephens
1 Replies
2. Programming
Hello,
Met a problem when compiling a C++ program from source code without error, but when ran it there was always an error message:
./Ray: error while loading shared libraries: libmpi_cxx.so.1: cannot open shared object file: No such file or directoryAs the error points to openmpi which was... (0 Replies)
Discussion started by: yifangt
0 Replies
3. Web Development
Hi,
I am working on Linux Platform. I am just trying to port a CPP module to apache as a module. When I try to build the Apache , it throws an error as follows
libtool: unrecognized option `-DLINUX=2' Later I did some search and changed the config_vars.mk file under the "build" directory of... (0 Replies)
Discussion started by: ashabb
0 Replies
4. HP-UX
Hi,
The necessary symbols in a shared library can be exported to the application using linker option --version-script in Linux. The same can be done in Hp-ux using linker option +e. This can also be done by listing all the global symbols with +e in a file with linker option ld -c filename in... (0 Replies)
Discussion started by: roopa_v
0 Replies
5. Linux
Hi All,
I m new to this group.
I m facing one problem during my linking of CPP code at Linux env.
after compliation i m getting error
"undefined reference to ....."
Please anyone help me to resolve this error.
Regards,
ASR
make: Leaving directory /fwk'
echo g++ -o server ... (1 Reply)
Discussion started by: ASRRAJ
1 Replies
6. UNIX for Advanced & Expert Users
Hi, I want to define a symbol in my code as:
extern int Address;
and then I'd like to define the symbol value in linker (ld) script file, so each time I change the hardware, I don't need to redefine the value in code, just use different linker script. I've gone through ld reference and didn't... (3 Replies)
Discussion started by: lzwierko
3 Replies
7. HP-UX
Hi All
Could anyone help in giving a little background to the following runtime error.
/usr/lib/pa20_64/dld.sl: Mmap failed due to errno: 13.
Seen when executing a 64-bit ELF executable.
Thanks
Ed (3 Replies)
Discussion started by: C3000
3 Replies
8. Programming
using SUN C++ I have a problem when I do a push_back on a vector. The linker gives me a undefined symbol error on __cxa_end_catch.
Any ideas, is there a library to include?
Thanks
Chris (1 Reply)
Discussion started by: CDurkin
1 Replies
9. Programming
Hi Together,
while compiling my program with CC I get the following Error message from the Linker:
Undefined first referenced
symbol in file
std::basic_string<char,std::char_traits<char>,std::allocator<char>... (2 Replies)
Discussion started by: nik
2 Replies
10. UNIX for Dummies Questions & Answers
hai
I have installed Linux 7.0 on my system and i have an doubt the
linker
i ran simple hello.c program with gcc compiler
gcc -c hello.c
i want linker to produce the output
so i put on the command line as
ld first.o -lc
but it is not running ver properly
but there is an... (1 Reply)
Discussion started by: rajashekaran
1 Replies
FORT77(1) Linux Programmer's Manual FORT77(1)
NAME
fort77 - invoke f2c Fortran translator transparently, like a compiler
SYNOPSIS
fort77 [-c] [-g] [-v] [-k] [-P] [-cpp] [f2c option ...] [-L directory ...] [gcc-option ...] [link option ...] [-O optlevel] [-o out-
file] [-s] [-w] [-Wx,arg1[,arg2]...] file ...
DESCRIPTION
The fort77 script invokes the f2c command transparently, so it can be used like a real Fortran compiler. It can be used to compile For-
tran, C and assembler code, and to link it with the f2c libraries.
File arguments ending with .f are compiled as Fortran source files. Files which end with .P are passed through to f2c, and files ending
with .F are passed to the C preprocessor (invoked as "/lib/cpp -traditional") first. Any switches passed via -D will be passed to the pre-
processor. If the translation is successful, the resulting C files will be passed to cc for translation into an object file. Files ending
in .c, .C, .cc, .i, .s, .S, .m, .cc or .cxx are passed to the GNU C compiler directly; see gcc(1). All other files are passed to the
linker.
OPTIONS
-c Supress linking and produce an object ( .o ) file from each source file.
-g Include debugging information. -v Be verbose; supplying this twice will also tell the C compilers etc to be verbose.
-k Keep the C files generated by f2c around.
-cpp Pass Fortran code through the C preprocessor, as if filenames ended in .F.
-P Generate f2c .P files.
-Ldirectory
Include directory in the search for libraries in the final linking stage.
-o outfile
Send output to outfile.
-trapuv Have f2c generate code to trap uninitialized values.
-Wx,arg1[,arg2...]
Pass the argument[s] argi through to the subprocess x, where x can assume one of the following values: f for the f2c step, p for
the preprocessing step, c for the C compiler, a for the assembler (this is actually passed to the C compiler, too), and l for the
linker. As an example, defining a preprocessor constant for the C compilation step would be done with -Wc,-DUNIX=1. Specifying
the -f option to f2c would be done via -Wf,-f.
f2c option
fort77 passes through almost all f2c options: -C, -U, -u, -a, -E, -h, -P, -R, -r, -z, -I2, -I4, -onetrip, -!c, -!l, -!P, -!R, -ext,
-!bs, -W[n], -trapuv, -w8, -r8 and -w66.
gcc options
The following options are passed through to gcc: -f*, -W*, -U*, -A*, -m*, -S, -E, -v, -x, -pipe, -o, -I, -V, -b*, -p, -pg.
linker option
The options passed to the linking stage are -static, -shared, -v, -V, and -symbolic.
BUGS
To make debugging work, you need to set a breakpoint at MAIN__ before you start.
f2c This script automatically supplies the -I. option to f2c. Older versions of f2c may not support this.
This script is for the interaction of gcc and f2c; using it with another compiler will probably require modification.
The fort77 script does not strictly conform to Posix.2, because it acceppts long options with one leading slash. This is done for gcc com-
patibility.
SEE ALSO
f2c(1), cc(1), as(1), ld(1)
AUTHOR
Thomas Koenig, ig25@rz.uni-karlsruhe.de
Linux Nov 1996 FORT77(1)