[liblouis-liblouisxml] Re: harness lou_allround en-ueb-g1.ctb problem continued
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Fri, 3 Oct 2014 14:59:52 +0000
Are you telling me after I do
Sudo make install
I have to set environment variables for me to be able to load en-ueb-g1.ctb
because I sure have never had to do that with any other tables. I only
mentioned copying the script because after I did it and ran it as root
everything worked and it did not before. I was hoping that it would help find
what the sudo make install is not doing. Let me be clear.
If I have nothing installed no liblouis at all. I do all the steps in my
previous mail as I had been told to do. I then run lou_allround and load the
en-ueb-g1.ctb it errors. If I run it from tools directory it does not. That
is a bug. It works for you folks because you have environment variables set.
It should work when I do sudo make install with out setting environment
varibles shouldn't it?
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Christian Egli
Sent: Friday, October 3, 2014 8:36 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: harness lou_allround en-ueb-g1.ctb problem
continued
On 10/02/2014 02:35 PM, Ken Perry wrote:
> problem. So I thought maybe the "which" was not showing me really
> which lou_allround binary was being run. So I broot force removed
> lou_allround from /usr/bin. From that point on there was no
> lou_allround to be run. So then I thought cool I will just copy the
> working lou_allround from my tools directory and see if that fixed the
> problem.
>
> This is the result I got:
>
> When I run the lou_allround that I copy into usr/bin from the
> liblouis/tools directory I got an error of:
>
> mkdir: cannot create directory `/usr/bin/.libs': Permission denied
If you look at the file `lou_allround` in the tools directory you'll see that
it is just a shell script where presumably libtool sets up the environment to
find all the right libs and then starts the real `lou_allround`. `make install`
does the right thing and copies the binaries and the libs to the right place.
Now, if you just manually copy `lou_allround` which is really a shell script
you are bound to loose.
When running the test suite I try to do some of this setting up the
environment, so the test suite actually uses the code and the tables in the
source directory. The Makefile.am in the tests dir contains the following line:
> TESTS_ENVIRONMENT =
> \
>
> LOUIS_TABLEPATH=$(top_srcdir)/tables,$(top_srcdir)/tests/tables,$(top_srcdir)/tests/tables/moreTables
> \
> PYTHONPATH=$(HARNESS_DIR):$(top_srcdir)/python:$$PYTHONPATH
> \
> HARNESS_DIR=$(HARNESS_DIR)
> \
> LD_LIBRARY_PATH=$(top_srcdir)/liblouis/.libs:$$LD_LIBRARY_PATH
> \
> PATH=$(top_srcdir)/tools:$$PATH
Here you can see that LOUIS_TABLEPATH, LD_LIBRARY_PATH and PATH have to be set
up. Could this be your problem?
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse
12, CH-8045 Zürich, Switzerland
For a description of the software, to download it and links to project pages go
to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
