After the make run, binaries are not stripped. This results in ~1.1.GB data in the source directory. make install tried to copy theses 1.1GB to /local/samba-3.0.12 which ended in a full /local filesytem. I can reproduce this behavior with debian testing too.
what compiler (and version) and what configure flags are you using?
(In reply to comment #0) > After the make run, binaries are not stripped. This results in ~1.1.GB data in > the source directory. make install tried to copy theses 1.1GB to > /local/samba-3.0.12 which ended in a full /local filesytem. I can reproduce this > behavior with debian testing too. (In reply to comment #0) > After the make run, binaries are not stripped. This results in ~1.1.GB data in > the source directory. make install tried to copy theses 1.1GB to > /local/samba-3.0.12 which ended in a full /local filesytem. I can reproduce this > behavior with debian testing too. (In reply to comment #1) > what compiler (and version) and what configure flags are you using? On Solaris (gcc version 2.95.2) just I ran ./configure --with-acl-support --prefix=/usr/local/samba3012 --with-quotas --with-ssl --with-included-popt These are the same options I used the last x upates. On Debian (gcc-Version 3.3.5) only ./configure - nothing special. I will upload the config.log from the solaris system.
Created attachment 1062 [details] config.log (solaris)
Ralf, Looks like the default CFLAGS setting is "-g -O2" if nothing has been set explicitly. You can override the by setting env CFLAGS="-O2" ./configure ..... This is a temporary fix for now. The long term fix is to call either install or install-strip based on whether the --enable-debug configure option has been defined. I'll work on this later.
(In reply to comment #4) > Ralf, Looks like the default CFLAGS setting is "-g -O2" if > nothing has been set explicitly. You can override the > by setting > > env CFLAGS="-O2" ./configure ..... > > This is a temporary fix for now. The long term fix is to > call either install or install-strip based on whether > the --enable-debug configure option has been defined. > I'll work on this later. Fine, I'll give it a try. Thanks!
closing since we have a workaround