Well, the act of linking against libobj should definitely be performed by gcc and from gnustep-make (at worse). And you are right: they have been put back.

Let me get back to you.

Even when I don't have the -lobjc in the GNUmakefiles, I see when it comes to the linking stage the -lobjc2 automatically added. The same should be true for others having the -lobjc as default. gnustep-make should take care of that automagically.

Also, running ldd on the libraries, I see them being linked against libobjc2 in my case.

Sebastian

I don't really understand why libobjc is installed as libobjc2, because the whole point of the version number at the end of the filename of libraries is that you can install for example libobjc.so.1 and libobjc.so.2 at the same time...

With regards to whether or not to link with libobjc: if I run objdump on libSOGo.so I see that it uses at least three methods from libobjc directly (objc_get_class, objc_msg_lookup, objc_msg_lookup_super), so it should link with libobjc. Whether this linking is specified by gcc, gnustep or directly in the makefile doesn't really matter much, but if a library uses symbols from a different library it needs to link against it.

With regards to -ldl we should only link to that for the platforms that need it, that should be an easy fix.

Dekkers: (as mentionned on irc)

It should not beneeded to specify it from the makefiles, because gcc "knows" which runtime library it uses. A makefile should not bother with this. the same way that issuing "gcc test.c -o test" will automatically link your program with the right libc.

Buzzdee:

which version of gnustep-make are you using?

Latest release: 2.6.2

@Dekkers: why its installed as libobjc? reason is just that it was decided that way when the libobjc2 port was introduced, to for example not clash at some point in time with system libobjc (in /usr/lib), or libobjc from a gcc port in /usr/local/lib.

gnustep-make is configured with parameter:

--with-objc-lib-flag=-lobjc2

So whenever it links something, it automatically adds -lobjc2 instead of adding -lobjc, which is the default.

I think with the current GMakefiles, you see the -lobjc two times in the gcc parameters?

Since GNUstep Make takes care to link against the right runtime, there should be no need to tinker in GNUmakefiles with it.

I just tested on Ubuntu 12.10 and I only see it once when linking libSOGo.so, somehow gnustep-make doesn't care of it on Debian/Ubuntu...

Then, maybe in configure stage, the libraries needed could be determined automatically and saved in a variable. I remembered, Richard did the something similar for gnustep-base. In gnustep-base there was also -lobjc hardcoded, he changed it to use gnustep-config --objc-libs.
Since we link against gnustep-base, we could use:
gnustep-config --base-libs

For me on OpenBSD this prints out:
-Wl,-E -L/usr/local/lib -pthread -shared-libgcc -fexceptions -fgnu-runtime -L/home/sebastia/GNUstep/Library/Libraries -L/usr/local/lib -L/usr/local/lib -lgnustep-base -lobjc2 -lm

or on an older system, linking against -lobjc from gcc, it prints:
-Wl,-E -pthread -fgnu-runtime -L/home/sebastia/GNUstep/Library/Libraries -L/usr/local/lib -L/usr/local/lib -lgnustep-base -pthread -lobjc -lm

This could be saved in a variable, and used all over the place, instead of the hardcoded information. This way SOPE/SOGo should get it always right.

So how about that one then?

I don't have any problem with replacing the explicit linking with the output of gnustep-config --base-libs.

This has now been done.

Hi,

I found a similar issue with gnustep's SQLClient library. They just fixed it after my report with exchanging:
-lgnustep-base -lobjc
with:
$(FND_LIBS) $(OBJC_LIBS)
The diff I'm talking about, you can find here:
http://svn.gna.org/viewcvs/gnustep/libs/sqlclient/trunk/GNUmakefile?r1=35788&r2=35787&pathrev=35788

Those two variables are defined in makefiles that get installed with gnustep-make and gnustep-base.

I wasn't aware of those variables before, but I think now this would be the cleanest way to link against gnustep base and libobjc, when desired.

With the changes from comment 0004788, are we now all set with that bug and can close it?

From my side, yes, even given I did not checked what you have done when you said its fixed. A link to the git was missing ;)
I only wanted to point out that there is a probably more clean way than the one I first proposed. So, if you think its fine with you, fine for me too.
When the time comes to upgrade to 2.0.3, and things are not as expected, I'll open another one.

We now use "gnustep-config --base-libs" in both SOGo and SOPE's configure scripts.