Hello,
still unable to solve this problem.
Here is the command and again the errors it produces:
gcc -o tbl2hex tbl2hex.build.o program.build.o pid.build.o options.build.o
log.build.o file.build.o device.build.o parse.build.o timing.build.o
io_misc.build.o sys_linux.build.o charset.build.o chars
Shérab, le Mon 09 Jul 2012 11:56:43 +0200, a écrit :
> still unable to solve this problem.
> Here is the command and again the errors it produces:
> gcc -o tbl2hex tbl2hex.build.o program.build.o pid.build.o options.build.o
> log.build.o file.build.o device.build.o parse.build.o timing.build.o
>
[quoted lines by Samuel Thibault on 2012/07/08 at 16:47 +0200]
>Mmm, this is still marked as fuzzy in the tree, did you perhaps just
>forgot to remove the fuzzy keywords? It seems so, see attached patch.
This patch has now (revision 6588) been committed to brltty's development
stream.
--
Dave
My Alva BC640 behaves in an interesting way.
When I connect the device to my computer -- before I turn on BrlTTY, I am able
to type on the perkins keys as if the alva was a standard USB keyboard, but, of
course, the device's braille display doesn't do anything.
Once I turn on BrlTTY, I get the
Nicholas Dechman wrote:
> My Alva BC640 behaves in an interesting way.
>
> When I connect the device to my computer -- before I turn on BrlTTY, I am
> able to type on the perkins keys as if the alva was a standard USB keyboard,
> but, of course, the device's braille display doesn't do anything.
Samuel Thibault (2012/07/09 14:40 +0200):
> What's important here is the -fPIE -pie, which is spurious. IIRC it's
> icu-config which used to emit them. Upgrading to version 4.8.1.1-8
> should fix that.
Yes! That fixed it, thank you !
Best wishes,
Sherab.
__
