g++ Compiling Question

ErikJohnson · 03-30-2004, 10:45 PM

I am compiling a program on my linux system that I want to run on another linux system. When I run the program on the other system, it says it can't find the shared library libstdc++.so.5. That sounds like some basic stuff to me, but it ain't there.

Is there anyway to make g++ build a standalone execuatable that won't require shared libraries? Or some other way to make it work on another linux system?

BTW, I do not have root access to the other system.

Thanks-
Erik

adz · 03-31-2004, 01:44 AM

You'll have to compile it statically. Look at the "-static" option.

ErikJohnson · 03-31-2004, 12:35 PM

Thanks for the help.

I notice when using the -static option, that the executable file size is exactly the same as it was before. It's like the -static option did nothing. Also, I get the same error.

Am I missing something?

Erik

Tinkster · 03-31-2004, 03:56 PM

Chances are that the source you're trying to
compile is looking for something older/newer
than what you actually have installed ...

You could try making a symlink from the
actually present library to .5 ...

[edit]
Ooops, stuff that, you don't have root
access, my bad
[/edit]

Cheers,
Tink

ErikJohnson · 03-31-2004, 04:33 PM

Would it be possible, if I move the required libraries into the runtime directory, to somehow have it find the libraries there, instead of looking for them in the standard spot?

Erik

Tinkster · 03-31-2004, 05:04 PM

Sure ... all you'd need is set-up a variable
export LD_LIBRARY_PATH="<where your version lives>"

Cheers,
Tink

ErikJohnson · 03-31-2004, 05:25 PM

Ok... well I exported that, and it seems to be working, however

It already wants more libraries that libstdc++.so.5 depends on, and I fear I will end up in a recursive dependency nightmare! Any idea how many dependent libraries, in total, libstdc++.so.5 requires? If it's more than a couple, I think I would like to pursue the --static route to solving my problem.

Do you have any suggestions why I the -static has no effect?

Thanks for your help-
Erik

adz · 03-31-2004, 05:50 PM

Try something like:

Code:

g++ dummy.cpp -o dummy /usr/lib/library1.a /usr/lib/library2.a -static

ErikJohnson · 03-31-2004, 06:37 PM

Well, I'm using the -c option for everything in my Makefile, so there shouldn't be any linking taking place anyway, right?

When I remove the -c options, and use -static, it bugs me for this:

cannot find -lstdc++

When I use both -c and -static, nothing is different than if I were to just use -c. And I don't think it makes sense (but I could be wrong) to use the -o option because I am doing lots of stuff in the Makefile:

Code:

# Makefile for snparser

CC     = g++
CFLAGS = -Wall -g 

LEX    = flex
LEXLIB = -lfl
YACC   = bison -ydv

OBJ    = main.o message.o ast.o unparse.o y.tab.o lex.yy.o

snparser: $(OBJ)
	$(CC)  $(OBJ)  -o snparser   $(LEXLIB) ; \
	cp snparser ../finished_text;	


main.o: main.cc ast.h symbol.h scanner.h
	$(CC) -c $(CFLAGS)   main.cc
ast.o: ast.cc ast.h symbol.h
	$(CC) -c $(CFLAGS)   ast.cc
unparse.o: unparse.cc ast.h symbol.h helpers.cc
	$(CC) -c $(CFLAGS)   unparse.cc
message.o: message.cc message.h
	$(CC) -c $(CFLAGS)   message.cc


y.tab.o: y.tab.c
	$(CC) -c $(CFLAGS)   y.tab.c
y.tab.h: y.tab.c
	touch y.tab.h
y.tab.c: grammar.yacc ast.h symbol.h scanner.h
	$(YACC)         grammar.yacc

lex.yy.o: lex.yy.c ast.h symbol.h scanner.h message.h y.tab.h
	$(CC) -c $(CFLAGS)   lex.yy.c  -DYY_NO_UNPUT
lex.yy.c: tokens.lex y.tab.h
	$(LEX) tokens.lex


clean:
	/bin/rm -f *.o lex.yy.c y.tab.*
erase:
	/bin/rm -f *.o lex.yy.c y.tab.*  u1

Maybe I'm in too deep!

Erik

Marius2 · 04-01-2004, 07:48 AM

Hi Erik,

just some hint:
>It already wants more libraries that libstdc++.so.5 depends on, and I fear
>I will end up in a recursive dependency nightmare! Any idea how many
>dependent libraries, in total, libstdc++.so.5 requires?
At the console, type ldd <nameofbinary>; this will dump the dependencies
of the file.

HTH