Different linker error !

[hanst99]

the -L is supposed to be a parameter for g++. And do not include the asterisks, I believe I already said so in my above post - I just used them to put emphasize on the path.

[Ali89]

I have wrote the command without asterisks and here is my terminal :

Ali-Marandis-MacBook-Pro:~ alimarandi$ -L partow/GaloisFieldArithmetic/libgalois.a
-bash: -L: command not found

would you mind telling me what is my fault ?

Thanks in advance :-).

[hanst99]

I already told you, -L is a parameter for g++

What you are supposed to do should look a little something like this:

g++ -Lpartow/GaloisFieldArithmetic/ yourThingy.cpp -lgalois

[Ali89]

hanst99,
I suggest you not to give advice in the cases that you are not sure you are advising in right place !!!
I have told you two times that I am simulating under ns3 and I have to compile by ./waf!. THIS WAS NOT A COMMON C++ PROGRAM WHICH YOU ARE ABLE TO COMPILE IT BY WRITING "g++ filename.cpp" !!!
You'd better not to give wrong advice and waste people's time !.

[hanst99]

I thought waf was just a python based build system, similar to make? You said you used gcc. I just said that you need to provide the library path to g++ with -L and the library name with -l - that should be true for waf as well, just that the method you use to provide the path and library may be slightly different. In any case, I don't see how this is related to being build for ns3 or not. My advice wasn't wrong either way, so please don't insult other people by telling them they are giving wrong advice when you just don't know what's going on.

[Ali89]

I did not insult you. When I found two solutions for my problem and saw that creating libgalois.a is needless, I just gave you a suggestion that if you are not sure you are advising in right place, avoid advising.

Ali

[hanst99]

If you are somehow using gcc you would want to create a library for galois. You could keep the objects manually around - I believe I linked to an article explaining what object files are, if not I excuse myself - it's just that when using external libraries, using them as libraries is the default process.