[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 02:45 -0500]
>Here is the complete log file, and the build failed as you can see.
Where are you getting the brltty-5.2.tar.xz file from?
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-00
I took the latest git and ran ./autogen and tarred it up.
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 02:45 -0500]
>
> >Here is the complete log file, and the build failed as you can see.
>
> Where are you getting the brltty-5.2.tar.xz file from?
>
> --
> Da
Hi Vincent,
I'm slightly out of topic, but can xou tell me whats your distro and
your release of brltty? Is your BrailleSense up-to-date? I ask because
on my Debian 8, BrailleSense is not recognized. brltty says the usb
descriptor is not present and, indeed, BrailleSense uses a gene!ic usb
dr
On Mon, 14 Dec 2015, Dave Mielke wrote:
> This is just a warning. It means that the pcspkr kernel module can't be
> modrobed, which, as far as brltty is concerned, isn't a problem. It might be
> a
> problem for the user, though.
>
> Brltty plays what we call alert tunes for events the user mig
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 07:58 -0500]
Hi:
>I took the latest git and ran ./autogen and tarred it up.
That's the problem. Run autogen and configure, and then do: make src-tar
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone:
[quoted lines by Dave Mielke on 2015/12/14 at 12:22 -0500]
>That's the problem. Run autogen and configure, and then do: make src-tar
Also, don't run autoconf when you untar. Just start with the configure.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1
Hi,
I'm afraid I can't help much. I'm running Vinux verison 5 (I didn't
mean to take much risks with accessibility for this first try). But I
run a VritualBox. The host system is still Windows. I had to install a
driver on Windows to help the device be identified, but Windows doesn't
know
OK, I will try that.
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 07:58 -0500]
>
> Hi:
>
> >I took the latest git and ran ./autogen and tarred it up.
>
> That's the problem. Run autogen and configure, and then do: make src-tar
>
> --
> Dave Mielke |
Doing that gives me the following output and it fails
./mktar ./ brltty-5.2 brltty-5.2.tar
./mktar: line 53: ./autogen: Permission denied
Makefile:62: recipe for target 'brltty-5.2.tar' failed
make: *** [brltty-5.2.tar] Error 1
Also, I need to end up with a .xz file, so how can I run tar with the
hmmm, I never run autocon, just autogen which creates configure.
Dave Mielke wrote:
> [quoted lines by Dave Mielke on 2015/12/14 at 12:22 -0500]
>
> >That's the problem. Run autogen and configure, and then do: make src-tar
>
> Also, don't run autoconf when you untar. Just start with the config
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 14:15 -0500]
>hmmm, I never run autocon, just autogen which creates configure.
autoconf. I think I read in the log you sent yesterday that, after untarring,
autoconf was run.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 14:13 -0500]
>I need to end up with a .xz file, so how can I run tar with the
>compression option?
make src-tar-xz
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 14:13 -0500]
>Doing that gives me the following output and it fails
>
>./mktar ./ brltty-5.2 brltty-5.2.tar
>./mktar: line 53: ./autogen: Permission denied
What's the umask set to at the point that you're doing this?
--
Dave Mielke
This is done by the ebuild and was done before -- is it not to be done
anymore? I thought it just ran configure.
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 14:15 -0500]
>
> >hmmm, I never run autocon, just autogen which creates configure.
>
> autoconf. I thin
The comments in the ebuild are
# We run eautoconf instead of using eautoreconf because brltty uses
# a custom build system that uses autoconf without the rest of the
# autotools.
eautoconf
So, is this no longer the case?
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covic
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 15:03 -0500]
>This is done by the ebuild and was done before -- is it not to be done
>anymore? I thought it just ran configure.
no, autoconf makes configure (from configure.ac). The software that makes the
tar file (the mktar script) has a
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 15:07 -0500]
>The comments in the ebuild are
> # We run eautoconf instead of using eautoreconf because brltty uses
> # a custom build system that uses autoconf without the rest of the
> # autotools.
> eautoconf
>
>So, is this
But the original error which stops the making of the tar file is
./mktar: line 53: ./autogen: Permission denied
This is after I ran ./autogen and ./configure without any options.
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 14:13 -0500]
>
> >I need to end up with
umask is 022
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 14:13 -0500]
>
> >Doing that gives me the following output and it fails
> >
> >./mktar ./ brltty-5.2 brltty-5.2.tar
> >./mktar: line 53: ./autogen: Permission denied
>
> What's the umask set to at the poi
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 15:18 -0500]
>But the original error which stops the making of the tar file is
>./mktar: line 53: ./autogen: Permission denied
>This is after I ran ./autogen and ./configure without any options.
I do that all the time. It works, so it must b
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 15:20 -0500]
>umask is 022
Before you start the build, or at the point in the build where the make src-tar
is done?
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario
umask is 022
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 15:18 -0500]
>
> >But the original error which stops the making of the tar file is
> >./mktar: line 53: ./autogen: Permission denied
> >This is after I ran ./autogen and ./configure without any options.
>
Before I start the build -- this is my default umask.
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 15:20 -0500]
>
> >umask is 022
>
> Before you start the build, or at the point in the build where the make
> src-tar
> is done?
>
> --
> Dave Mielke
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 16:01 -0500]
>Before I start the build -- this is my default umask.
I'm asking what the umask is at the time that the make src-tar is run. Are you
running it manually from the command line? If so, the umask isn't the problem,
then. In fact
OK, my sequence is the following: clone the git repository into
brltty-test, execute autogen by typeing ./autogen, executing ./configure
by typing ./configure and then typing make src-tar-xz -- is this
correct?
Dave Mielke wrote:
> [quoted lines by cov...@ccs.covici.com on 2015/12/14 at 16:01 -0
[quoted lines by cov...@ccs.covici.com on 2015/12/14 at 17:10 -0500]
>OK, my sequence is the following: clone the git repository into
>brltty-test, execute autogen by typeing ./autogen, executing ./configure
>by typing ./configure and then typing make src-tar-xz -- is this
>correct?
Yes. I just m
Hi,
Sorry for the delay. I had trouble logging and keeping track, I had to
try several times. Attached to this email you will find my
/sys/kernel/debug/usb/devices file, when the BrailleSense is connected.
I don't know if it will be very helpful. You will also find a log of a
BRLTTY sessi
[quoted lines by Vincent LE GOFF on 2015/12/14 at 14:42 -0800]
>You will also find a log of a BRLTTY session (I selected only part of it and
>wrote down the key press just before pressing it). Each key is pressed 4-5
>seconds of each other to clearly separate it. and I made longer pauses betwee
Okay, I'll do a second session of test (probably in a half hour from
now, I just need to get some sun :D ). Now that I know how to do it
(writing into the log file at runtime is a bad idea), it should be
easier. I just need to have a clear and ordered list of keys to press
and combine it with
OK, I got this done a better way by using the gentoo ebuild from git
system -- the only strange things I had to do was to do autogen by hand
and to make the documents -- I was actually missing linuxdoc-tools, but
it went fine and it does actually work, at least in preliminary testing,
after all th
Hi,
Here's the new log. I've included what I could and hope the matching is
correct (some were a bit tricky and I hope I got them right). I didn't
press the Windows key or any combination with it, because it's
interpreted by the HIMS system. Pressing Windows leave the screen
reading mode.
Could you also please do shift + each of the four arrow keys?
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
_
There's a problem with this one. I got only two key logged. I tried
several times but I'm not sure of what works. I tried Shift + Up arrow,
Shift + Down arrow, Shift + left arrow and Shift + right arrow. I
assumed only the two first ones worked. But perhaps only the two last
ones worked.
It's okay. I guess only Shift+ArrowUp/Down are working.
Correctly interpreting these keys will take a bit of coding. Additionally, I
now have an updated protocol document which does allow querying the keyboard
type and whether two or four scroll keys are being used, and that, too, will
take a b
Okay. Should I try to build the 5.3 when it's realsed? If I understood
well, it won't change the accessibility for the BrailleSense, but it's
also true it will provide a good exercise for building from sources in
the first place.
Thanks for your work,
On 12/14/2015 7:46 PM, Dave Mielke wrot
[quoted lines by Vincent LE GOFF on 2015/12/14 at 19:56 -0800]
>Should I try to build the 5.3 when it's realsed? If I understood well, it
>won't change the accessibility for the BrailleSense, but it's also true it
>will provide a good exercise for building from sources in the first place.
You
Great, I have to test it! I've downloaded the code using git directly.
But there, I'm at a loss. I've installed from source using simply the
./configure;make;make install command, but it seems I can't do that as
easily with sources that way. Sorry with my beginner question, I've
tried to fi
Sorry, I had missed the ./autogen configuration. Now I get an error
because /var/brltty already exists, which is kind of normal since I'm
using it to build it. I don't feel quite comfortable removing it before
installing it, but I'm looking at the build options, perhaps there's one
to do that
[quoted lines by Vincent LE GOFF on 2015/12/14 at 21:20 -0800]
>I get an error because /var/brltty already exists, which is kind of normal
>since I'm using it to build it.
Do you mean that you checked out the brltty source into /var/brltty/?
I'm not sure what that error would be. Can you post
I got it wrong, it's the /var/run/brltty that can't be created (a
process?). I've checked out the code in my home directory:
cd /home/vincent/src
git clone https://github.com/brltty/brltty.git
cd brltty
./autogen
./configure
sudo make install
Here's the log of the configure and make install co
[quoted lines by Vincent LE GOFF on 2015/12/14 at 21:52 -0800]
>Here's the log of the configure and make install command. I'm afraid
>I don't know what is wrong.
>
>test -z "/var/run/brltty" || /usr/bin/install -c -d /var/run/brltty
>/usr/bin/install: cannot create directory ‘/var/run/brltty’: Fi
Version 5.3 of BRLTTY has been released. You can get it by doing the following:
Go to: http://brltty.com/
Click on: Download
Click on: Current Release
Here's a summary of the major things that have happened to BRLTTY since 5.2:
General fixes:
The missing key event (stuck key) problem
Should I then run 'make install -d' to ignore that error? I don't know
why it would be different, but BRLTTY was installed on the system and I
have no idea how it is run (as a service or deamon or something
similar). Perhaps the problem comes from the current configuration.
I'd rather use it
43 matches
Mail list logo
