public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: speakup@braille.uwo.ca
Subject: Re: Gentoo - where's speakup been put?
Date: Wed, 7 May 2008 20:59:19 -0500	[thread overview]
Message-ID: <20080508015918.GA5181@linux1> (raw)
In-Reply-To: <1210168036.9293.16.camel@violet.perfumed-garden.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Gena,

> Sorry, I'm confused here.  I emerged gentoo-sources which gave me the
> kernel source then I created my /etc/portage directory and the required
> package.keywords file.  Then emerged speakup.  So you are saying that
> the sources are ready for further configuration according to hardware
> and compilation and I can proceed with the install?
 
 That is correct, see my comment below about speakup.

> I'll set up the chroot env again and run menuconfig and I'll
> immmediately be able to see if speakup is there.  

No, not in menuconfig.  On gentoo, speakup is installed the same way
alsa was before it became part of kernel.org.  It is a set of modules,
outside the kernel.

I need to make one correction on the steps I gave you.  Once you are in
the croot, emerge, configure, compile and install your kernel.  Make
sure that /usr/src/linux points to the correct kernel tree.  Once that
is set up, then emerge speakup.

Again, in order for all of this to work, you must use at least
gentoo-sources-2.6.25-r1.

Once you have that set up, you should specify in
/etc/modules.autoload.d/kernel-2.6 which synthesizer you want to load,
for example:

speakup_ltlk start=1

But, I am about to do another snapshot for gentoo, and when that
happens, you will no longer need the start parameter.

Let me know if you still have questions.

William

> As I've used git and fresh kernel sources previously.  I expected to see
> a directory called speakup ready for me to run the installer manually.
 
> Thanks.
> 
> Gena
>   
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkgiXnYACgkQblQW9DDEZTg5SACgnz4rgtBYcWvFztlbws+2hSZx
YNEAn10XBlZZgUDvyPVQCsdH/Y5Q16TE
=G6+d
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Georgina Joyce
 ` William Hubbs
   ` Georgina Joyce
     ` William Hubbs
       ` Georgina Joyce
         ` William Hubbs [this message]
           ` Robert Spangler
           ` Garrett Klein
             ` William Hubbs
               ` Garrett Klein
               ` Garrett Klein

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=20080508015918.GA5181@linux1 \
    --to=williamh@gentoo.org \
    --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).