09-18-2001
Try with a space in between, instead of a comma.
10 More Discussions You Might Find Interesting
1. Programming
Hi
I'm getting
ld: fatal: option -h and building a dynamic executable are incompatible
ld: fatal: Flags processing errors
When I run
ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o
after running
gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c
I'm... (6 Replies)
Discussion started by: laho
6 Replies
2. Programming
I'm trying to do something fairly simple but keep getting frustrating messages..
Here it is:
I have 3 files:
init.h <header>
init.c <#include <curses.h> and "init.h">
main.c <#include "init.h">
now, how can I compile my main.c using gcc?
( I have a hard time making the init.o)
... (1 Reply)
Discussion started by: My_Name
1 Replies
3. UNIX for Dummies Questions & Answers
hi,
This is the first time I work in a big C project. All source code files are located in say directory /source/pp and all header files are in /include/pp. I've created a link to both of these directories from my home dir, say /home/ss. So in the /home/ss dir I have the /source/pp and /include/pp... (1 Reply)
Discussion started by: bruins2005
1 Replies
4. UNIX for Dummies Questions & Answers
Hello,
Can anyone tell me how I can make a file link or shortcut in UNIX 4.0, several
file links where damaged during an outage examples below.
Examples: file -> file
libX11.so -> /usr/shlib/libX11.so.pre.O3D
All of the file links that were damaged were in /shlib and point to... (3 Replies)
Discussion started by: jays337
3 Replies
5. Programming
Dear friends,
First off all , let me apologize for my inexperience. I am just starting use of Linux and gcc .
Actually I ve some .c files in the present directory , and now I am
giving
+vc <my_file1.c> <my.file2.c> <myfile3.c>.
All the c files are in present directory.... (2 Replies)
Discussion started by: user_prady
2 Replies
6. Shell Programming and Scripting
I used to program ksh a while back, but I've been off in Oracle/Windows land (for clients -- not by choice) for so long that I can't remember what should be an easy thing. Here's the scenario:
1)Find all files and directories beneath some directory point (A).
2)If directory, make the... (7 Replies)
Discussion started by: scyphers
7 Replies
7. Programming
I have one C program which contains a function call.
I have been given some .so and .h files.
I want to know how to compile and link the c program with .so files.
I tried following:
$ gcc My_program.c libCommon.so
My_program.c: In function āmainā:
My_program.c:11: warning: parameter names... (3 Replies)
Discussion started by: junaid.nehvi
3 Replies
8. SuSE
Hi everyone I installed OpenSuse 12.3 and many development tools but when i propose build the kernel from the source (the first step make menuconfig) i saw this:
HOSTLD scripts/kconfig/mconf
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: warning: libdl.so.2,... (2 Replies)
Discussion started by: bacesado
2 Replies
9. Shell Programming and Scripting
I have 2 txt files, 1.txt and 2.txt which contain the paths to files that need to be linked.
Example 1.txt:
/root/001/folder2/image4.nii.gz
/root/002/folder2/image4.nii.gz
Example 2.txt:
/root/001/folder2/image5.nii.gz
/root/002/folder2/image5.nii.gz
Each line represents images from... (7 Replies)
Discussion started by: LeftoverStew
7 Replies
10. Programming
Basically my problem is that when I try to compile anything using ./configure && make, it fails because of linker errors. I can reproduce the behavior I'm getting as follows:
I have the two following files
main.c:
#include <stdio.h>
extern void func(void);
int
main(int argc, char... (5 Replies)
Discussion started by: MarshallBanana
5 Replies
LEARN ABOUT FREEBSD
file2c
FILE2C(1) BSD General Commands Manual FILE2C(1)
NAME
file2c -- convert file to c-source
SYNOPSIS
file2c [-sx] [-n count] [prefix [suffix]]
DESCRIPTION
The file2c utility reads a file from stdin and writes it to stdout, converting each byte to its decimal or hexadecimal representation on the
fly. The byte values are separated by a comma. This also means that the last byte value is not followed by a comma. By default the byte
values are printed in decimal, but when the -x option is given, the values will be printed in hexadecimal. When -s option is given, each
line is printed with a leading tab and each comma is followed by a space except for the last one on the line.
If more than 70 characters are printed on the same line, that line is ended and the output continues on the next line. With the -n option
this can be made to happen after the specified number of byte values have been printed. The length of the line will not be considered any-
more. To have all the byte values printed on the same line, give the -n option a negative number.
A prefix and suffix strings can be printed before and after the byte values (resp.) If a suffix is to be printed, a prefix must also be
specified. The first non-option word is the prefix, which may optionally be followed by a word that is to be used as the suffix.
This program is typically used to embed binary files into C source files. The prefix is used to define an array type and the suffix is used
to end the C statement. The -n, -s and -x options are useful when the binary data represents a bitmap and the output needs to remain read-
able and/or editable. Fonts, for example, are a good example of this.
EXAMPLES
The command:
date | file2c 'const char date[] = {' ',0};'
will produce:
const char date[] = {
83,97,116,32,74,97,110,32,50,56,32,49,54,58,50,56,58,48,53,
32,80,83,84,32,49,57,57,53,10
,0};
BSD
March 22, 2007 BSD