[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ddt-client error " ld.so: Incorrectly built binary"



On Fri, Jan 23, 2004 at 01:47:07AM +0100, Benedict Verheyen wrote:
> ----- Original Message -----
> From: "Jan Minar" <Jan.Minar@seznam.cz>
> To: <debian-user@lists.debian.org>
> Sent: Friday, January 23, 2004 12:55 AM
> Subject: Re: ddt-client error " ld.so: Incorrectly built binary"
> 
> <snip>
> 
> >The workaround would be changing 0.1 to an integer, or commenting out
> >the whole ``sleep 0.1'' line in /etc/init.d/ddt-client if that didn't
> >help (maybe adding some another time-consuming thingie).  However, many
> >things can break when the sleep command is broken, so replacing the
> >broken version should be the primary concern.
> 
> Well, i ended up getting the source code but there was more
> than just the client in there. It also had code for the server
> which i don't need and when i tried dpkg-buildpackage -uc -us
> the code for the server failed. I didn't know how to adjust
> the rules files to only compile the client subdirectory.
> But that didn't matter as the ddtc and ddtcd binaries where
> compiled correctly although not put correctly together in a deb.
> So i copied those to the correct directories, adjusted the
> /etc/init.d/ddt-client script and restarted. Now i didn't get an
> error so i assume i should file 2 bug reports against the package:

What you did, basically, is you circumvent the installation scripts.
This is not a Good Thing:  These scripts not only copy the things where
they should be, but also do some housekeeping work, change permissions
here and there, etc.  Your system is now in an undefined state.  Don't
report bugs or ask for a help, if things break...  Furthermore, the sleep
bug might be a consequence by your disk failure you wrote about in
another thread.

> 1. sleep 0.1 should change to sleep 1

Wrong.  It's a sleep(1) bug.  Read my last mail.

> 2. ld complaint that goes away when recompiling so the binary
> in the deb package contains an error

Yes, the code is lose, probably.  But again, this didn't cause your
problem in the first place.

-- 
Jan Minar                   "Please don't CC me, I'm subscribed." x 9

Attachment: pgpsrnU6IUDff.pgp
Description: PGP signature


Reply to: