relative rpath issue

[Alexander Dreyer <alexander.dreyer@itwm.fraunhofer.de>]

Hi!
I've a problem linking a unit test (for a "make check"-style target) to 
a recently build shared library on debian-hurd.
The library is not installed yet (the check is run before), but there is 
a relative rpath as well as a (relative) symlink in place.

g++ -o testsuite/unittests -Wl,-z,relro 
-Wl,-rpath=\$ORIGIN/../build/debian/tmp/usr/lib/i386-gnu -z origin 
testsuite/src/GroebnerStrategyTest.o [...]
 -L/usr/lib -L/usr/lib/python2.7/config -lboost_unit_test_framework 
build/debian/tmp/usr/lib/i386-gnu/libpolybori-0.8.so.3.0.0 
build/debian/tmp/usr/lib/i386-gnu/libpolybori_groebner-0.8.so.3.0.0 
-lm4ri -lpng
testsuite/unittests: error while loading shared libraries: 
libpolybori-0.8.so.3: cannot open shared object file: No such file or 
directory

The full log is here:
https://buildd.debian.org/status/fetch.php?pkg=polybori&arch=hurd-i386&ver=0.8.3-1~exp1&stamp=1361023063

Are there any known problems with relative rpaths, maybe in combination 
with symbolic links?

Best regards,
  Alexander Dreyer