[PHP-DEV] Re: Serious problems with libtool 1.4..
Please let me know whether the current CVS works for you. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: Serious problems with libtool 1.4..
And that fix of yours is a hack. Could you please revert it? As I remember you yourself told me once that we don't want to fix symptoms but the causes.. :) There are no rules without exception. In this case, the macro can be helpful to determine when you are using broken extensions. Note that I'm still operating under the assumption that something is actually adding -L/usr/lib to LDFLAGS. Your message it is still broken does not really help us to determine whether that is the actual cause. Let's start working on the libtool problems for 4.0.7. HEAD is always the development branch. Instead of reverting working changes, I suggest branching off 4.0.6 and backing out the libtool-related changes in that branch only. I think the real fix is to find and fix those extensions that are the cause for these problems. That is what I said earlier. Attached is my configure script... :) Please add set -x to the top of your configure script and send me the output. Thanks. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: Serious problems with libtool 1.4..
At 05:20 PM 5/9/2001 +0200, Sascha Schumann wrote: And that fix of yours is a hack. Could you please revert it? As I remember you yourself told me once that we don't want to fix symptoms but the causes.. :) There are no rules without exception. In this case, the macro can be helpful to determine when you are using broken extensions. Note that I'm still operating under the assumption that something is actually adding -L/usr/lib to LDFLAGS. Your message it is still broken does not really help us to determine whether that is the actual cause. Let's start working on the libtool problems for 4.0.7. HEAD is always the development branch. Instead of reverting working changes, I suggest branching off 4.0.6 and backing out the libtool-related changes in that branch only. I want to branch tomorrow so why not revert the patch today and reapply it tomorrow night or the day after? Same effect but it makes more sense to me to have the tree 4.0.6-dev until we branch. Andi I think the real fix is to find and fix those extensions that are the cause for these problems. That is what I said earlier. Attached is my configure script... :) Please add set -x to the top of your configure script and send me the output. Thanks. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: Serious problems with libtool 1.4..
I want to branch tomorrow so why not revert the patch today and reapply it tomorrow night or the day after? Because that creates more work than reverting the patch once? Same effect but it makes more sense to me to have the tree 4.0.6-dev until we branch. I'd like to see this apparent problem fixed quickly in the development branch. Prolonging it by backing the changes out from the main branch and reapplying them a day later makes little sense to me. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Re: Serious problems with libtool 1.4..
Whatever. I just think it makes more sense to put such patches after we branch. Andi At 07:34 PM 5/9/2001 +0200, Sascha Schumann wrote: I want to branch tomorrow so why not revert the patch today and reapply it tomorrow night or the day after? Because that creates more work than reverting the patch once? Same effect but it makes more sense to me to have the tree 4.0.6-dev until we branch. I'd like to see this apparent problem fixed quickly in the development branch. Prolonging it by backing the changes out from the main branch and reapplying them a day later makes little sense to me. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Re: Serious problems with libtool 1.4..
On Wed, 9 May 2001, Jani Taskinen wrote: The upgrade to libtool 1.4 was most likely a big mistake. Here's what happened on my system where everything worked just fine before the update: You most likely have a -L/usr/lib in LDFLAGS/LIBS then which has been added by a broken config.m4. There are still some autoconf checks which don't use PHP_ADD_LIBPATH to add library search paths, and hence the suppression of adding /usr/lib to the search path is not applied everywhere. Please post your configure line, so that we can look into it. As a quick fix, we can apply s#-L/usr/lib## to some variables at the end of configure. I'll implement that later (have to run now). - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
