Sponsored Content
Top Forums Programming undefined reference to 'function' Post 302315621 by bigrigdriver on Wednesday 13th of May 2009 12:49:37 AM
Old 05-13-2009
In your fortran code, don't you need to import the function, or the module that contains the function, that is causing the problem?

Something like:
modulename import

or possibly,
from modulename import functionname

Here is a link you can go to to read more about fortran and linking modules: IBM Compilers
 

9 More Discussions You Might Find Interesting

1. Programming

Undefined reference to Error

Hello, plz help me out with this error, i am getting this error when i compile my code with gcc. /usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../crt1.o(.text+0x18): In function `_start': : undefined reference to `main' /tmp/cciLxqdV.o(.text+0x3c): In function `HandleUserTransaction()':... (2 Replies)
Discussion started by: svh
2 Replies

2. Programming

about undefined reference for 'sinf'

I m writting code in c using another library(parapin) and making Makefile .but there is a error like undefined reference to `sinf' undefined reference to `ceilf' although i have added math.h library in my code . I tried to run simple programme using math.h and it run.but in making Makefile it... (2 Replies)
Discussion started by: bharat suthar
2 Replies

3. Programming

undefined reference to `pthread_create'

Hi I wanted to learn communication between threads and I used a simple example but I faced with this error while I have a sofware that uses this functions without any problem so would you please help me to know the reason thanks for your help and great favor. #include <pthread.h>... (2 Replies)
Discussion started by: netman
2 Replies

4. Programming

undefined reference to `__ctype_b'

when i compile my program, i meet the following error: ... undefined reference to `__ctype_b' ... anybody knows which shared library should be linked during make? thanks a lot! (6 Replies)
Discussion started by: princelinux
6 Replies

5. Programming

undefined reference to pthread_create

I try to compile a sample c code in fedora eclipse 3.2 as managed makefile using pthread library,it shows some error on pthread functions.Error is of undefined reference to pthread.Anybody guide me to solve this problem. Thanking you (1 Reply)
Discussion started by: sujith4u87
1 Replies

6. Programming

undefined reference to `pthread_create'

Hi guys. H was learning posix threads in C with anjuta IDE. it gives me undefined reference to `pthread_create' I know i should compile it like: gcc -lpthread main.c how should i import this configuration in anjuta so i can compile inside it? (2 Replies)
Discussion started by: majid.merkava
2 Replies

7. Homework & Coursework Questions

undefined reference help

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: i know when undefined reference shows up the program is saying it is not link to that function but the problem... (1 Reply)
Discussion started by: mgyeah
1 Replies

8. Homework & Coursework Questions

undefined reference help

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: The problem is a function which i typed although it kept saying that it is a undefined reference still. other... (1 Reply)
Discussion started by: mgyeah
1 Replies

9. Programming

Undefined reference to omp_get_thread_num using OpenMP?

I am using a large code-base that compiled successfully before using make with a makefile and cmake. However, now that I'm trying to use openmp with it, I'm now getting the errors undefined reference to `omp_get_thread_num' undefined reference to `omp_get_num_threads'I don't think this... (0 Replies)
Discussion started by: larry burns
0 Replies
SDFGET(1)						User Contributed Perl Documentation						 SDFGET(1)

NAME
sdfget - Documentation Extraction Utility PURPOSE
sdfget extracts documentation embedded in source code. USAGE
usage : sdfget [-h[help]] [-o[out_ext]] [-l[log_ext]] [-O[out_dir]] [-f formatting_filename] [-g[get_rule]] [-r[rpt_file]] [-s scope] [-i] [-v[verbose]] file ... purpose: extract documentation embedded in source code version: 2.000 (SDF 2.001) The options are: Option Description -h display help on options -o output file extension -l log file extension -O output to input file's (or explicit) directory -f filename to use when formatting the output -g rule to use to get documentation -r report file -s scope of documentation to be extracted -i only output lines not extracted -v verbose mode DESCRIPTION
The -h option provides help. If it is specified without a parameter, a brief description of each option is displayed. To display the attributes for an option, specify the option letter as a parameter. By default, generated output goes to standard output. To direct output to a file per input file, use the -o option to specify an extension for output files. If the -o option is specified without a parameter, an extension of out is assumed. Likewise, error messages go to standard error by default. Use the -l option to create a log file per input file. If the -l option is specified without a parameter, an extension of log is assumed. By default, generated output and log files are created in the current directory. Use the -O option to specify an explicit output directory. If the -O option is specified without a parameter, the input file's directory is used. The -f option can be used to specify a filename to use when formatting the output. This is useful when the text is coming from the standard input stream. The get-rule nominates the formatting of the embedded documentation to be extracted. All currently defined get-rules assume the documentation is in comment blocks in one of the following formats: >>section_title1:: text of section 1, line 1 text of section 1, line .. >>section_title2:: text of section 2, line 1 text of section 2, line .. >>END:: >>section_title3:: text of section 3 The first form is most commonly used. In this format, the text in a section extends until the end of the current "comment block" or the start of the next section, whichever comes first. The second form (i.e. explicitly specifying where the section ends) is useful if you wish to add some normal comments (i.e. non-documentation) which you do not want extracted. If the text is short, the third form can be used. Regardless of the format, if a section is found which is already defined, the text of the section is concatenated onto the existing text. This permits the documentation for each entity to be specified immediately above where it is defined in the source code. The -g option specifies the get-rule to use. The available get-rules differ on the prefix expected at the front of each line as shown below. Rule Prefix perl # cpp // c * or /* fortran c (with 5 preceding spaces) eiffel -- bat rem Within C code, a trailing space is required after the characters above. For other languages, a trailing space is optional. Within FORTRAN code, the "c" character must be preceded by exactly 5 spaces. For other languages, zero or more whitespace characters are permitted before the characters above. For example, embedded documentation within C code looks like: /* >>Purpose:: * This library provides a high level interface * to commonly used network services. */ If the -g option is not specified, perl is the default get-rule. If the -g option is specified without a parameter, the extension in lowercase of the filename (or the formatting filename if the text is coming from standard input) is used to guess the get_rule as shown below. Rule Extensions cpp cpp, c++, cc, hpp, hpp, h, java, idl c c fortran fortran, for, f77, f eiffel eiffel, ada bat bat, cmd A report filename can be specified using the -r option. If the name doesn't include an extension, sdg is assumed. Reports provide a mechanism for: o selectively extracting sections, and o rudimentary reformatting (e.g. to SDF) If no report is specified, all sections are output in the following format: section_title1 section_text1 section_title2 section_text2 If -r is specified on its own, default.sdg is assumed. This report selects the set of sections (within the SDF documentation standards) which form the user documentation and formats them into SDF. Details on the report format are specified below. Reports are searched for in the current directory, then in the stdlib directory within SDF's library directory. The -s option can be used to specify the scope of the documentation to be extracted. (This is an experimental feature and may change so most users should avoid using it.) The -i option outputs only those lines which the get-rule did not match. This option is useful for extracting non-documentation from a file to give just the code. Note: The -r option is ignored if -i is specified. The -v option enables verbose mode. This is useful for seeing which rule is being used for each file. EXAMPLES
To extract the user documentation from a SDF application written in C++ (xyz, say) and save it into xyz.sdf: sdfget -gcpp -r -osdf xyz.cpp LIMITATIONS AND FUTURE DIRECTIONS
It would be nicer if the get-rule was always guessed from the filename extension but changing the default from perl could break existing scripts. Therefore, get-rule guessing must be explicitly enabled by specifging the -g option without a parameter. perl v5.12.4 2011-11-09 SDFGET(1)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy