From: "jim grimsby" <jimgrims@pacbell.net>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Building speechd-up
Date: Wed, 30 Mar 2005 14:50:32 -0800 [thread overview]
Message-ID: <000101c5357a$e4684c90$220110ac@jim> (raw)
In-Reply-To: <20050330222111.GB11401@blackbox>
Hi, ok well version of automake is 1.7 now maid sure by doing this
apt-get install automake1.7
Before was 1.4 still getting the error. Sheesh.
-----Original Message-----
From: speakup-bounces@braille.uwo.ca
[mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Kenny Hitt
Sent: Wednesday, March 30, 2005 2:21 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Building speechd-up
Hi.
I have 2 guesses. Either you are missing a Debian package or you are
running an old version of automake.
What version of automake are you using?
I'm running automake 1.8.5.
Hope this helps.
Kenny
On Wed, Mar 30, 2005 at 02:10:20PM -0800, jim grimsby wrote:
> Hi, ok I ran that same error informing me that it failed.
> Just what in gods name am I doing wrong here.
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca
> [mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Janina Sajka
> Sent: Wednesday, March 30, 2005 2:03 PM
> To: Speakup is a screen review system for Linux.
> Subject: Re: Building speechd-up
>
>
> There's either a build.sh or an install.sh script that you might need
> to execute first:
>
> sh build.sh
>
> Something like that, I think.
>
> jim grimsby writes:
> > Ok well any one try to build speechd-up get this problem I tried
> > first ./configure Before I could move on to the next step I was told
> > this file could not be found. I was in the /speechd-up directory
> > So I went on to the next step if this does not work
> > aclocal && autoconf && autoheader && automake -a && automake
> > I got a error message that reads
> > Aclocal: configure.in: 36: macro `am_prog_libtool'
> > ./configure is still not found.
> > So what am I doing wrong here?
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
>
> Janina Sajka Phone: +1.202.494.7040
> Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
>
> Chair, Accessibility Workgroup Free Standards Group
(FSG)
> janina@freestandards.org http://a11y.org
>
> If Linux can't solve your computing problem, you need a different
> problem.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
jim grimsby
` Janina Sajka
` jim grimsby
` Kenny Hitt
` jim grimsby [this message]
` John covici
` Kenny Hitt
` Sean McMahon
` Sean McMahon
` Kenny Hitt
jim grimsby
` Sean McMahon
` jim grimsby
` Luke Yelavich
` jim grimsby
` jim grimsby
` Gregory Nowak
` jim grimsby
` jim grimsby
` Steve Holmes
` Sean McMahon
` Janina Sajka
` Kenny Hitt
` jim grimsby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000101c5357a$e4684c90$220110ac@jim' \
--to=jimgrims@pacbell.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).