01-09-2017
The -b and -G options probably meant something completely different wherever this code came from, so I would look up what they meant on your old system. If they're not anything crucial, you can probably just delete them.
On GNU Linux, ld's -b parameter should be followed with a binary executable format, such as elf64-x86-64, and -G is an optimization option which is supposed to be followed by a size related to MIPS register mapping.
9 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. UNIX for Dummies Questions & Answers
Getting the following error ,
ld: /opt/syncsort39/lib/libsyncsort.sl: Mismatched ABI. 64-bit PA shared library found in 32-bit link.
Is there any difference in the ld options in opt file while linking a 64 bit shared library ? Or is the problem because we are trying to link both 32 bit and 64... (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
3. Programming
Hi,
Could any one tell me solution for this.
i have a library in my /usr/lib and latest in /myhome/lib/ (thay differ functionality symbols my application uses symbols from latest lib).
when compile and link my application , every thing goes fine
but when running the application ld... (4 Replies)
Discussion started by: Raom
4 Replies
4. Programming
Hello all
Im using CC: Sun C++ 5.6 2004/07/15 and using the -library=stlport4 when linkning im getting
The fallowing error :
Undefined first referenced
symbol in file
std::ostream &std::ostream::operator<<(std::ios_base&(*)(std::ios_base&))... (0 Replies)
Discussion started by: umen
0 Replies
5. Solaris
at the end of the compilation in solaris 9. it is showing link error.
like.....
ld: fatal: library -lgthread-2.0 not found
failed to create the binary
the library is in /usr/lib and in /usr/local/lib the lib file is present
--->libgthread.2.0.so ......etc
if i remove... (3 Replies)
Discussion started by: biswajithit
3 Replies
6. UNIX for Dummies Questions & Answers
how would i link 2 files together?
is it the same as copying? (1 Reply)
Discussion started by: trob
1 Replies
7. Programming
Hi, I have got sample linux driver written in C.
I got also some assembly code, compiled into .o file (using as compiler).
In my Makefile I got:
obj-m += someDriver.o
someDriver-objs := CFile1.o CFile2.o ASMFile.o
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modulesUnfortunatelly I cannot... (0 Replies)
Discussion started by: Chrisdot
0 Replies
8. Programming
Hi,
I have the following files:
// file.hvoid foo();
int i = 5; // should be just declared as extern int i;
// file1.c#include <stdio.h>
#include "file.h"
void foo() {
i = 10;
printf("%d\n", i);
}
// file2.c#include <stdio.h>
#include "file.h"
int main() {
foo(); (9 Replies)
Discussion started by: royalibrahim
9 Replies
9. Programming
I am on a FreeBSD system trying to build a piece of software that I wrote. I had built it in the past but recently reinstalled FreeBSD. I am not sure what is going on. The software depends on and wxgtk2.8.
Using g++:
$ make
g++ -c `wx-config --cxxflags`... (9 Replies)
Discussion started by: AntumDeluge
9 Replies
dlerror(3C) dlerror(3C)
NAME
dlerror - get diagnostic information
SYNOPSIS
[flag ... ] file ... [library] ...
DESCRIPTION
is one of a family of routines that give the user direct access to the dynamic linking facilities (using the option on the compiler or com-
mand line). returns a null-terminated character string (with no trailing newline) that describes the last error that occurred during
dynamic linking processing. If no dynamic linking errors have occurred since the last invocation of returns NULL. Thus, invoking second
time, immediately following a prior invocation, results in NULL being returned.
MULTITHREAD USAGE
This routine is thread-safe.
WARNINGS
The messages returned by may reside in a static buffer that is overwritten on each call to Application code should not write to this buf-
fer. Programs wishing to preserve an error message should make their own copies of that message.
SEE ALSO
dlclose(3C), dlopen(3C), dlsym(3C).
Texts and Tutorials:
(See the option)
(See manuals(5) for ordering information)
dlerror(3C)