Update. I got this working. The issue is linux users have to build a php 
instance from source per 
https://gae-php-tips.appspot.com/2014/11/15/app-engine-php-1-9-17-pre-release-sdk/.
 
The dev appserver works OK once it is configured to point at this newly 
compiled php instance. The google documentation on this should be improved. 
The reason for the missing libraries errors is because the appengine 
extension expects them to be compiled into the corresponding php version. 
I'm closing on this issue for now.

On Wednesday, May 4, 2016 at 12:27:05 PM UTC-7, Chris Hoffman wrote:
>
> I'm on linux and have a simple helloworld-level Fat-Free Framework php 
> application consisting of a single route to a single view. I am only 
> requiring F3's base.php. Absolutely no sql anything. 
>
> When I build a simple yaml file pointing to the index.php and start the 
> dev_appserver, it complains that it can't find pdo_mysql.so but nowhere in 
> the code is mysql referenced. The error message from dev_appserver 
> indicates it is looking for pdo_mysql.so in the 
> appengine-php-extension-master/modules/ directory (where I had previously 
> successfully built gae_runtime_module.so). I have no local php.ini defined.
>
> I can successfully run dev_appserver.py against some simple php file, but 
> as soon as it uses F3, it complains about pdo, curl, json, mysql, mysqli 
> and pdo_mysql.so not being loaded as they are not found even though I'm not 
> using any of these in this simple case.
>
> Any help or pointers would be greatly appreciated,
> Chris
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7cc41656-225f-4d08-b4da-9f87924005de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to