that old /bin/sh: django_libsass.SassCompiler: command not found issue again

[Bug Eyed]

So I've been digging around and trying to find a solution to this issue.

I'm running my site on Webfaction, in a virtualenv. Everything is set up, but I'm getting the error that is in the title. 

I've used pip freeze, and I have both libsass and django-libsass installed. 

While libsass does install, I get the following warnings:

Running setup.py install for libsass

    building '_sass' extension

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bbuild/temp.linux-x86_64-2.7/pysass.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    In file included from /usr/local/include/python2.7/Python.h:8:0,

                     from pysass.cpp:4:

    /usr/local/include/python2.7/pyconfig.h:1182:0: warning: "_POSIX_C_SOURCE" redefined [enabled by def

    /usr/include/features.h:162:0: note: this is the location of the previous definition

    /usr/local/include/python2.7/pyconfig.h:1204:0: warning: "_XOPEN_SOURCE" redefined [enabled by defau

    /usr/include/features.h:164:0: note: this is the location of the previous definition

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b_compressed.cpp -o build/temp.linux-x86_64-2.7/libsass/output_compressed.o -c -O2 -fPIC -std=c++0x -Wall

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b_str.cpp -o build/temp.linux-x86_64-2.7/libsass/copy_c_str.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthe

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/bind.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/util.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/json.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/to_c.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/ber.cpp -o build/temp.linux-x86_64-2.7/libsass/prelexer.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bt.cpp -o build/temp.linux-x86_64-2.7/libsass/context.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bing.cpp -o build/temp.linux-x86_64-2.7/libsass/to_string.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthese

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b_map.cpp -o build/temp.linux-x86_64-2.7/libsass/source_map.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthe

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/btualize.cpp -o build/temp.linux-x86_64-2.7/libsass/contextualize.o -c -O2 -fPIC -std=c++0x -Wall -Wno-pa

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/file.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bt.cpp -o build/temp.linux-x86_64-2.7/libsass/inspect.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b.cpp -o build/temp.linux-x86_64-2.7/libsass/parser.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b.cpp -o build/temp.linux-x86_64-2.7/libsass/expand.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bnterface.cpp -o build/temp.linux-x86_64-2.7/libsass/sass_interface.o -c -O2 -fPIC -std=c++0x -Wall -Wno-

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b_placeholders.cpp -o build/temp.linux-x86_64-2.7/libsass/remove_placeholders.o -c -O2 -fPIC -std=c++0x -

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/btring.cpp -o build/temp.linux-x86_64-2.7/libsass/utf8_string.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parent

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/node.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bp -o build/temp.linux-x86_64-2.7/libsass/ast.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/be.c -o build/temp.linux-x86_64-2.7/libsass/cencode.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1: warning: command line option '-std=c++0x' is valid for C++/ObjC++ but not for C [enabled by def

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bons.cpp -o build/temp.linux-x86_64-2.7/libsass/functions.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthese

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bcss.cpp -o build/temp.linux-x86_64-2.7/libsass/sass2scss.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthese

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b.cpp -o build/temp.linux-x86_64-2.7/libsass/extend.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bcpp -o build/temp.linux-x86_64-2.7/libsass/units.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bvlq.cpp -o build/temp.linux-x86_64-2.7/libsass/base64vlq.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthese

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/eval.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/btil.cpp -o build/temp.linux-x86_64-2.7/libsass/sass_util.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthese

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bhandling.cpp -o build/temp.linux-x86_64-2.7/libsass/error_handling.o -c -O2 -fPIC -std=c++0x -Wall -Wno-

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/b_nested.cpp -o build/temp.linux-x86_64-2.7/libsass/output_nested.o -c -O2 -fPIC -std=c++0x -Wall -Wno-pa

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bpp -o build/temp.linux-x86_64-2.7/libsass/sass.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parentheses

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/home/bnts.cpp -o build/temp.linux-x86_64-2.7/libsass/constants.o -c -O2 -fPIC -std=c++0x -Wall -Wno-parenthese

    cc1plus: warning: command line option '-Wstrict-prototypes' is valid for Ada/C/ObjC but not for C++

    g++ -pthread -shared -L/home/bugeyed/gcc/lib -I/home/bugeyed/gcc/include build/temp.linux-x86_64-2.76_64-2.7/libsass/copy_c_str.o build/temp.linux-x86_64-2.7/libsass/bind.o build/temp.linux-x86_64-2.7/libbsass/to_c.o build/temp.linux-x86_64-2.7/libsass/prelexer.o build/temp.linux-x86_64-2.7/libsass/context./source_map.o build/temp.linux-x86_64-2.7/libsass/contextualize.o build/temp.linux-x86_64-2.7/libsass/fis/parser.o build/temp.linux-x86_64-2.7/libsass/expand.o build/temp.linux-x86_64-2.7/libsass/sass_interfa4-2.7/libsass/utf8_string.o build/temp.linux-x86_64-2.7/libsass/node.o build/temp.linux-x86_64-2.7/libsabsass/functions.o build/temp.linux-x86_64-2.7/libsass/sass2scss.o build/temp.linux-x86_64-2.7/libsass/exs/base64vlq.o build/temp.linux-x86_64-2.7/libsass/eval.o build/temp.linux-x86_64-2.7/libsass/sass_util.osass/output_nested.o build/temp.linux-x86_64-2.7/libsass/sass.o build/temp.linux-x86_64-2.7/libsass/consso -fPIC -lstdc++

    changing mode of build/scripts-2.7/sassc.py from 664 to 775

    changing mode of /home/bugeyed/webapps/osa_prod/bin/sassc.py to 775

    Installing sassc script to /home/bugeyed/webapps/osa_prod/bin

And then a note saying it was successfully installed. I'm not sure if these warnings have anything to do with my issue.

While I do have node/npm and ruby installed, I'm not finding any sass compilers in the lists

[Matthew Westcott]

Hi,

Please can you try the steps in https://github.com/torchbox/wagtaildemo/issues/55#issuecomment-73119787 and let me know the results?


The installation output looks fine to me - those warnings don't look like anything out of the ordinary. Node and ruby aren't required at all here - the compiler we're using here is pure C++ and Python, and is being invoked as a library, so there are no SASS command-line tools involved.

Cheers,
- Matt

[Bug Eyed]

Thanks,

>>> import sass; sass

<module 'sass' from '/home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/sass.pyc'>

I added the lines recommended to my base.py and receive the following in my error log

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1] mod_wsgi (pid=27501): Target WSGI script '/home/bugeyed/webapps/osa_prod/osa/osa/wsgi.py' cannot be loaded as Python module.

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1] mod_wsgi (pid=27501): Exception occurred processing WSGI script '/home/bugeyed/webapps/osa_prod/osa/osa/wsgi.py'.

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1] Traceback (most recent call last):

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]   File "/home/bugeyed/webapps/osa_prod/osa/osa/wsgi.py", line 14, in <module>

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]     application = get_wsgi_application()

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]   File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/django/core/wsgi.py", line 14, in get_wsgi_application

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]     django.setup()

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]   File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/django/__init__.py", line 20, in setup

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]     configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]   File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/django/conf/__init__.py", line 46, in __getattr__

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]     self._setup(name)

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]   File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/django/conf/__init__.py", line 42, in _setup

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]     self._wrapped = Settings(settings_module)

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]   File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/django/conf/__init__.py", line 98, in __init__

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1]     % (self.SETTINGS_MODULE, e)

[Tue Feb 17 23:57:15 2015] [error] [client 127.0.0.1] ImportError: Could not import settings 'osa.settings.dev' (Is it on sys.path? Is there an import error in the settings file?): /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by /home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/_sass.so)

So I'm assuming I'm just missing this libstdc++.so ?

[Matthew Westcott]

> So I'm assuming I'm just missing this libstdc++.so ?

It seems so, yes. It's interesting to note that the same lines apparently succeed on the command line (presumably you also tried "from django_libsass import SassCompiler" on the command line and didn't get any errors?), so the fact that libstdc++ can't be found when running under Apache would suggest a deployment / UNIX configuration issue, which isn't my area of expertise I'm afraid...

Just throwing out a wild guess based on the last time I ran into an issue like this (which may be totally outdated for all I know) - do you have anything set in your LD_LIBRARY_PATH environment variable (i.e. does "echo $LD_LIBRARY_PATH" on the command line return anything)? That's commonly used to point the OS at libraries it can't otherwise find, but it's considered a poor fix because it fails as soon as you run the same thing outside a shell session (such as within a web server process). It could be that the command line version only works because it's improperly relying on this setting.

Cheers,
- Matt

[Bug Eyed]

ok, so I didn't run the import in the shell. 

running just the python shell, i get 

>>> from django_libsass import SassCompiler

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/django_libsas                                                                                                             s.py", line 4, in <module>

    from compressor.filters.base import FilterBase

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/compressor/fi                                                                                                             lters/__init__.py", line 2, in <module>

    from compressor.filters.base import (FilterBase, CallbackOutputFilter,

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/compressor/fi                                                                                                             lters/base.py", line 12, in <module>

    from compressor.conf import settings

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/compressor/co                                                                                                             nf.py", line 9, in <module>

    class CompressorConf(AppConf):

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/site-packages/compressor/co                                                                                                             nf.py", line 11, in CompressorConf

    ENABLED = not settings.DEBUG

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/djan                                                                                                             go/conf/__init__.py", line 46, in __getattr__

    self._setup(name)

  File "/home/bugeyed/webapps/osa_prod/lib/python2.7/Django-1.7.4-py2.7.egg/djan                                                                                                             go/conf/__init__.py", line 40, in _setup

    % (desc, ENVIRONMENT_VARIABLE))

django.core.exceptions.ImproperlyConfigured: Requested setting DEBUG, but settin                                                                                                             gs are not configured. You must either define the environment variable DJANGO_SE                                                                                                             TTINGS_MODULE or call settings.configure() before accessing settings.

however, when running python manage.py shell, I get no errors.

echo $LD_LIBRARY_PATH gives me:

 echo $LD_LIBRARY_PATH

/home/bugeyed/gcc/lib:

I really appreciate you taking the time to help with this. I may just end up taking this as an opportunity to learn how to deploy to heroku... is the vagrant set up suitable to get started with to deploy from?

[Matthew Westcott]

On 18 Feb 2015, at 13:01, Bug Eyed <k...@bugeyedllc.com> wrote:

> ok, so I didn't run the import in the shell.
>
> running just the python shell, i get
>
> >>> from django_libsass import SassCompiler
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>

> ...

>
> however, when running python manage.py shell, I get no errors.

Ah yes - django_libsass needs access to the Django project config, so the behaviour in 'python manage.py shell' is the meaningful one.

> echo $LD_LIBRARY_PATH gives me:
>
> echo $LD_LIBRARY_PATH
> /home/bugeyed/gcc/lib:

I think that'll be your problem. I take it Webfaction doesn't give you root access to install libstdc++ globally (where Apache would be able to see it)? Not sure what the best way around that is, then - you'd have to either compile libsass so that it's aware of that path, or somehow feed the equivalent of LD_LIBRARY_PATH to Apache.

> I really appreciate you taking the time to help with this. I may just end up taking this as an opportunity to learn how to deploy to heroku... is the vagrant set up suitable to get started with to deploy from?

I'll leave that for one of our Heroku gurus to answer :-)

- Matt

> --
> You received this message because you are subscribed to the Google Groups "Wagtail" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wagtail+u...@googlegroups.com.
> To post to this group, send email to wag...@googlegroups.com.
> Visit this group at http://groups.google.com/group/wagtail.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/wagtail/9848640b-3a1c-4c32-a5d3-756fc014d093%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Bug Eyed]

I have the wagtail installation running via a virtualenv, maybe that's the issue.

the following list of installed packages lists libstdc++, but I had to build GCC to the most recent version locally... in fact, I wonder if I can comment out the path in my .bashrc file to that version of gcc.

https://community.webfaction.com/questions/16162/is-there-a-list-of-installed-packages-on-a-webfaction-server

[Bug Eyed]

removing the path info in my bash file resulted in no path being returned.

The thing that is annoying is that others have been successful getting wagtail up and running on webfaction. Granted, learning Heroku's deployment may just make life easier as a freelancer anyway.