Torsten Werner schrieb:
Hi Uli,
On 9/30/07, Ulrich von Zadow <[EMAIL PROTECTED]> wrote:
That patch can be removed. The code is in the release, so it probably
doesn't apply anymore.
In the new version, it should be possible to run make check on the build
servers to perform some sanity checks on all directories except
src/test/ itself. Only the tests in that directory actually open a window.
I'll upload a new version.
Also, currently, there is no way for the build server to notice if there
are any unresolved externals because the library is never linked to
python, right? Would it help if I wrote a small python script that
checked for that?
I do not really understand what are you talking about... ;-)
Ok. I'll probably tell you some things you already know, but I don't
know which bit is missing...
The make process builds a library (libavg) that can be imported by
python to add functions to it. libavg calls functions that are located
in other libraries (so-called externals). When libavg is imported in
python, the dynamic linker attempts to find the externals that weren't
present on the link line of the library itself. Hopefully, it finds them
all in python. If not, there's something wrong. This happens, for
instance, if a library is missing on the link line.
The main problem is that these unresolved externals are not detected at
library creation time. They are only detected when libavg is imported
into python, and the debian build process never does that. So, my
proposal was to write a small python script that just tries to import
libavg. That way, the debian build process would notice if there are any
unresolved externals.
Regards,
Uli
--
Ulrich von Zadow | +49-172-7872715 | [EMAIL PROTECTED]
_______________________________________________
libavg-users mailing list
[email protected]
https://mail.datenhain.de/mailman/listinfo/libavg-users
