[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: make install makes bad binaries

Hi Philip,
You where quite right!   the /usr/local/bin/strip program is to blame...

I have both /usr/local/bin and /usr/css/bin in my $PATH (and in that

I renamed /usr/local/bin/strip to /usr/local/bin/strip.broken
so that  "which strip" now finds  /usr/css/bin/strip

I did the make install again and now all the /usr/local/bin/ldap* binaries are much smaller (sizes as I would expect), and /usr/local/bin/ldapsearch now does exactly what I want...

I see from my documentation that my /usr/local/bin/strip comes from installing GNU binutils, version 2.17, which i installed Apr 18 2007, just 2 days after I installed my previous openldap (version 2.3.32)

/usr/local/bin/strip although has the same date and bytesize now as it
had a year ago (I record files changed in /usr/local directories after
installing new packages) (and my $PATH also did not change in the last year, /usr/local/bin always was before /usr/css/bin..)
I have many other software installed after GNU binutils, never had that
problem ... ... quite strange ..

Never thought a GNU distributed set of tools could contain a broken program ... ??!?

On Mon, 28 Apr 2008, Philip Guenther wrote:

On Mon, 28 Apr 2008, Pieter Donche wrote:
but $ /usr/local/bin/ldapsearch
on the other hand, if I use the ldapsearch binary from my
openldap-2.3.39 build directory:
# ./clients/tools/ldapsearch
succeeds and I can perform a search on my LDAP database returning the
correct results..

I noticed a big difference in size between:
-rwxr-xr-x  1 root  root    457772 Apr 28 09:02 ./clients/tools/ldapsearch
-rwxr-xr-x  1 root  root   1023664 Apr 28 09:27 /usr/local/bin/ldapsearch

All the clients tools have that same size difference between the compiled
versions in ./openldap-2.3.39/clients/tools/ldap* and the ones in

Sounds like the 'strip' program that you're using is broken. What's the output of "which strip"? If it's _not_ /usr/ccs/bin/strip, then try moving /usr/ccs/bin to the front of your path and redo the install. If that fixes it, then REMOVE the broken strip program.

Philip Guenther