Re: Portability of find(1)

2001-09-18 Thread Sascha Schumann
> I'm looking for information on the portability of find(1). Please, > send me everything you know. In particular, I think I'm understanding > that `{}' is portably replaced by the argument only when alone, i.e., > exactly '{}' can only be used portable, if it is a separate argument. A

Re: shared library depending on static library on Solaris

2005-06-12 Thread Sascha Schumann
> > Having non-pic code in a shared lib has as effect that the lib > > actually isn't shared by several processes, so it's a waste of > > memory. Not everyone's top priority is memory. Non-pic code runs significantly faster on x86; for PHP scripts it can make about 30-50% difference i

Re: Libtool 1.4.3

2002-10-08 Thread Sascha Schumann
> > There is one big question which must be answered first: will it have > > to be Autoconf 2.13 compatible? We use it for the PHP project (>80k lines configure script), because 2.5x is 5 to 6 times slower and contains a dependency-ignorant cache system. So, please don't create i

Re: Libtool 1.4.3

2002-10-08 Thread Sascha Schumann
> I developed/maintain the configure script for ImageMagick. While the > total lines in the generated configure script is meaningless, it is > less than 1/2 of what you report for PHP, and PHP's configure script > is 4-8X larger than typical configure scripts for other large packages > (e.g. 4X l

Re: Libtool 1.4.3

2002-10-08 Thread Sascha Schumann
[Cc line trimmed] > me too! :) I think we have heard all arguments by now. There is no need to reiterate them. Whatever the outcome of this thread might be -- I hope those who work on libtool will continue to provide a toolkit which is suitable for all of us -- develop

Re: Libtool 1.4.3

2002-10-09 Thread Sascha Schumann
[Cc trimmed] > That's because it does provide a better service too :( I have timed a > lot of the code, and I can tell that we're hitting a M4 limitation > here. Hopefully future version of GNU M4 will help. In the mean time, we are happy to pursue our use of autoconf 2.13. > Sasc

Re: Libtool 1.4.3

2002-10-09 Thread Sascha Schumann
> You want autoconf -f then. -f, --force consider all files obsolete We do a ./cvsclean right now for autoconf +2.50 which purges all generated data. I guess that is basically the same. > You know, you are typically the kind of people who has valid grieves > against Au

Re: Creating lock file for compilers that don't support -c -o

2003-08-26 Thread Sascha Schumann
> I'd rather see a link to the POSIX standard defining link as atomic. IEEE Std 1003.1-2003 http://www.opengroup.org/onlinepubs/007904975/functions/link.html "The link() function shall atomically create a new link for the existing file and the link count of the file shall be