Mailinglist Archive: opensuse-buildservice (260 mails)

< Previous Next >
Re: [opensuse-buildservice] Pitfall with building on oS 11.2 (SUSE_ASNEEDED in environment)
  • From: Peter Pöml <poeml@xxxxxxxxxxx>
  • Date: Thu, 17 Dec 2009 14:32:02 +0100
  • Message-id: <BDBBC57C-40B6-43CD-B243-E3DC4A598528@xxxxxxxxxxx>
Hi,

Am 16.12.2009 um 20:49 schrieb Adrian Schröter:
Am Mittwoch, 16. Dezember 2009 18:15:03 schrieb Peter Pöml:

-gcc $RPM_OPT_FLAGS -Wall -lGeoIP -o geoiplookup_continent
geoiplookup_continent.c
+gcc $RPM_OPT_FLAGS -Wall -o geoiplookup_continent
geoiplookup_continent.c -lGeoIP


Critique:
---------
IMHO, this could have been made more obvious.
The above shown linker error isn't really elucidating. In fact, it
doesn't seem to make any sense at all.
I doubt that all build service users read the opensuse-specific
packaging list. And new users won't know that it might have been
discussed there. Some kind of keyword as a start for a Google
recherche is lacking.

Well, yes, but this is a typical problem which can happen at any time with the
gnu tools. Link order just matters, even when this particular case was
introduced with the asneeded feature of gcc, it can happen also without.

The error as such - indeed, it could happen in various situations. However, the particular situation here is that it unexpectedly happens only on a certain platform, for code that has worked for years and on several platforms, and is not reproducible at first.

So, a better message would be a task to the linker people. But I think it is
quite hard to list all possible reasons there in a readable way.

I see your point. But I think it would be enough if the linker issues a hint only if SUSE_ASNEEDED=1 is set in the environment (which seems to be special enough a situation to me).

("Note: experimental linker feature enabled by SUSE_ASNEEDED=1 in the environment; watch your link argument order carefully.")

I agree that it's more a job for the linker (people). Or for those who set SUSE_ASNEEDED=1 in the build environment.

The OBS solution for such kind of problems would be a kind of generic expert
system for the error analyses. But we don't have that yet.

However, if someone wants to draft a concept .... ;)

I realize that it's not easy to give advice for universally occurring errors. Still, something like http://ubuntu-virginia.ubuntuforums.org/showpost.php?p=6577455&postcount=2 would be useful. It might be a good start, cover a majority of the problems that you could run into, at least by pointing to the documentation. On 11.2, it could include a hint on the asneeded thing.

Peter--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >