Vitalie Spinu

Here is the output: ``` > devtools::install_github("rstats-db/RMySQL@stable", INSTALL_opts="INCLUDE_DIR=/opt/lampp/include LIB_DIR=/opt/lampp/lib/") Downloading github repo rstats-db/RMySQL@stable Installing RMySQL '/usr/lib64/R/bin/R' --no-site-file --no-environ --no-save --no-restore CMD \ INSTALL '/tmp/RtmpOfh8BA/devtools1cae70ff165f/rstats-db-RMySQL-b7f1470' \ --library='/VMS/home/vitalie/R/x86_64-redhat-linux-gnu-library/3.1' \ --install-tests * installing...

> Ugh. Did you try the static linking that I suggested earlier? I.e. just rename mysqlclient.so to something else and then try installing the R package? I don't have access...

With this I am getting ``` usr/bin/ld: cannot find -lmysqlclient ``` I think this is expected as the `mysql_config` is not picked up at all.

> Are you sure libmysqlclient.a is in the path that you set in LIB_DIR? Oh, I am such a doofus ... I misspelled the dir. It actually goes through but...

This gives: ``` * installing *source* package ‘RMySQL’ ... ** package ‘RMySQL’ successfully unpacked and MD5 sums checked sh: -lmysqlclient: command not found ERROR: configuration failed for package ‘RMySQL’ *...

Aga. Perfect. This works: ``` > install.packages("RMySQL", configure.vars='INCLUDE_DIR=/opt/lampp/include LIB_DIR="/VMS/home/vitalie/tmp/ -lmysqlclient -lpthread -lrt -lssl -lcrypto"') Installing package into ‘/VMS/home/vitalie/R/x86_64-redhat-linux-gnu-library/3.1’ (as ‘lib’ is unspecified) trying URL 'http://cran-mirror.cs.uu.nl/src/contrib/RMySQL_0.10.6.tar.gz' Content type 'application/x-gzip' length 52407...

Thanks for the very thorough input! As far as I am concerned my problem is fixed and you can close the issue, but I still wonder if this could be...

I actually tracked it down to how I activate `ido-everywhere`. I used to simply `(qset ido-everywhere t)`. Now this no longer works, so have to initialize explicetly with `(ido-everywhere t)`...

BTW, the same rationale is valid for `anaconda-mode-eldoc-function`. It can fall back on `python-eldoc-function` when no completion was found.

How about checking for native python completion first and only when there is nothing on that end dispatch to the server side? I think there is little to lose here....