clone 395529 -1
reassign -1 dpkg-dev
retitle -1 dpkg-shlibdeps doesn't look at all rpaths?
thanks

On Sat, Oct 28, 2006 at 12:46:15AM +0200, Josip Rodin wrote:
> > 
> > The amd64 package (and all others that were built in old environments)
> > can be fixed by binary-only uploads...
> 
> No other architectures exhibit this bug, only amd64.
[...]
> Kurt, what gives? Why was this build daemon not operating like all others?

>From the buildd log:
dpkg-shlibdeps: warning: could not find any packages for libcourierauth.so.0
dpkg-shlibdeps: warning: unable to find dependency information for shared libra
ry libcourierauth (soname 0, path libcourierauth.so.0, dependency field Depends
)

On amd64 you have the following rpath:
  RPATH       /usr/lib:/usr/lib/courier-authlib

While on i386 you have:
  RPATH       /usr/lib/courier-authlib

May I say that it's very annoying that all it shows is:
Linking maildrop

You even tell libtool to be --quiet.

It would be alot more useful if all the commands that were used
where in the buildd log.

So, what actually happens is:
g++ -g -Wall -O2 -I./../rfc822 -I./../rfc2045 -I.. -I./.. -Wall -o maildrop 
deliver.o deliverdotlock.o dotlockmaildrop.o filelock.o filter.o formatmbox.o 
globaltimer.o lexer.o log.o maildir.o main.o message.o messageinfo.o pipefds.o 
re.o recipe.o recipenode.o recipeparse.o reeval.o rematch.o rematchmsg.o 
rematchstr.o search.o token.o varlist.o  ./.libs/libmdcommon.a 
/usr/lib/libgdbm.so -L/usr/lib/courier-authlib 
/usr/lib/courier-authlib/libcourierauth.so -lcrypt -lpcre -Wl,--rpath 
-Wl,/usr/lib -Wl,--rpath -Wl,/usr/lib/courier-authlib -Wl,--rpath -Wl,/usr/lib 
-Wl,--rpath -Wl,/usr/lib/courier-authlib

When I relink it without the 2 "-Wl,--rpath -Wl,/usr/lib", dpkg-shlibdeps
seems to find it.

If I upgrade libtool to the latest version, they're also gone, and
dpkg-shlibdeps finds it's libraries.  So I suggest you do that.

But this also seems to be atleast a bug in dpkg-shlibdeps,
so I'm cloning it.


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to