05.13.09

phpize complains about $PHP_AUTOCONF

Posted in rants, bugs/fixes at 5:44 pm by tal

You’re trying to phpize some package, but no matter what you do it complains that it cannot find autoconf? whatever you do it throws at you:

Cannot find autoconf. Please check your autoconf installation and the $PHP_AUTOCONF environment variable is set correctly and then rerun this script

I’ve been stuck with this for 5 hours till I found the solution at: http://georgedonnelly.com/unix/the-fix-for-those-silly-freebsd-php-ports-php_autoconf-errors

Basically, if you’re like me - you’ve been trying to point $PHP_AUTOCONF at the executable, right? What you should do instead is:

1) make sure the autoconf binary is in the path
2) set $PHP_AUTOCONF to whatever the name of your autoconf binary is

I hope it took you less than 5 hours to get here. (go google!)

P.S.

If you need autoconf you can follow the uzair’s instructions which are:

You can download it from http://ftp.gnu.org/gnu/autoconf/ and then do
1. ./configure –prefix=/path/to/your/home/directory
2. make
3. make install

12.23.08

Google Checkout Carrier-Calculated-Shipping is broken

Posted in rants, bugs/fixes, google, code at 1:57 am by tal

I’ve been integrating my uncle’s corporate cookie gift baskets website with Google Checkout. Google has done a great job making everything easy and straightforward, and the experience has been delightful. Except that it is terribly broken.

Google offers three methods of determining shipping costs: Flat-rate, Carrier-Calculated and Merchant-Calculated.

Carrier-Calculated-Shipping provides the merchant the options of specifying an additonal fixed charge, and a percentage modification, which should be enough so that the vast majority of integrations would not have to resolve to creating their own shipping calculation code.

Google allows for “address restrictions” to be added to the Flat-Rate and the Merchant-Calculated shipping option, so if for example you do not wish to offer a flat-rate option to people outside of a certain set of states or zip-codes you can easily define that.

For some unknown, undocumented, incredibly annoying reason - you cannot specify address restrictions on Carrier-Calculated-Shipping. The result is that if you choose to use Carrier-Calculated-Shipping you must offer it to all buyers regardless of address. Even addresses which are obviously unavailable (such as UPS shipping to APO/FPO addresses) are being offered those services. I don’t think it is too much to ask for those obvious excluded addresses to be pre-configured into the google system, but it is outrageous that you cannot even specify those restrictions yourself!

This is very un-Google-like. I can’t stop thinking that I’m missing something. Google cannot be this stupid…

On the forums they suggest that I collect the zip/state of the user prior to checkout and then decide which shipping options to add to the cart-xml-request. This defeats the purpose of being a single-step, quick, checkout option doesn’t it?

I can’t think of a reason why implementing address restrictions on the Carrier-Calculated-Shipping option would be anything but a straight forward one-liner on google’s side.

In one word: dissapointing!