On Sep 21, 2014, at 8:23 PM, Chris Moore wrote:
> Hello,
> Thanks to all of your advice, I was able to compile and run brltty on the mac.
> The cfg-darwin script gave much better results. The other issue I had was
> that I had to run screen under su. If I ran it without the su, there
> appea
Hello,
Thanks to all of your advice, I was able to compile and run brltty on the mac.
The cfg-darwin script gave much better results. The other issue I had was
that I had to run screen under su. If I ran it without the su, there appeared
to be no communication between screen and brltty.
Chri
On Sep 20, 2014, at 1:35 PM, Chris Moore wrote:
> Hello,
> I’m trying to build on a 64-bit mac running mavericks. I did the following
>
> git pull
>
> ./configure —prefix=/opt/local
> make
>
Did you run ./autogen before you did ./configure? As Dave says, it's best to
use ./cfg-darwin instea
[quoted lines by Chris Moore on 2014/09/20 at 14:35 -0400]
>I’m trying to build on a 64-bit mac running mavericks. I did the following
>
>git pull
>
>./configure —prefix=/opt/local
It's better to use our wrapper for configure on Mac OS X, which is called
cfg-darwin. You can still give it any o
On 20 Sep 2014, at 20:35, Chris Moore wrote:
> Hello,
> I’m trying to build on a 64-bit mac running mavericks. I did the following
>
> git pull
>
> ./configure —prefix=/opt/local
> make
>
Hi,
did you try without prefix?
i never used it.
Norma lly macport put its path in .bashrc, it
