More Problems Installing Speakup

More Problems Installing Speakup

[Luke Davis]

Okay, guys, either I am more of an idiot than I think, or there is
something wrong with the installation script used to patch the kernel.
Maybe I should stick to C.
I believe I know what is happening, but after looking through the script,
I'm not sure where it is breaking down--all of the expected directories
(/usr/src/{linux,linux-2.4.20,speakup,speakup-1.00}) exist.

I pulled the CVS speakup as directed, resulting in the following directory
contents:

BUGS         cvsversion.h   speakup.c            speakup_dtlk.c
COPYING      diff-v22/      speakup_acnt.h       speakup_dtlk.h
CVS/         diff-v23/      speakup_acntpc.c     speakup_ltlk.c
Changes      diff-v24/      speakup_acntsa.c     speakup_spkout.c
Config.in    diff-v25/      speakup_apolo.c      speakup_txprt.c
Makefile     genmap.c       speakup_audptr.c     speakupmap.c
TODO         install*       speakup_bns.c        speakupmap.map
checkclean*  patchlist-v22  speakup_decext.c     symbols.h
checkin*     patchlist-v24  speakup_dectlk.c
checkout*    patchlist-v25  speakup_drvcommon.c

Upon doing the install with the "install" script, I get this:

Patching version v24
cp: cannot stat `speakup': No such file or directory
Creating .orig files [cat:
/usr/src/linux/drivers/char/speakup/patchlist-v24: No such file or
directory
] done.
Patching files [ppatch: Changes: extra operand
patch: Try `patch --help' for more information.
] done.
Copying files [ccp: copying multiple files, but last argument `symbols.h'
is not a directory
Try `cp --help' for more information.
] done.

Re: More Problems Installing Speakup

[Jude DaShiell]

Some packages get particular as to where you need to be when you unpack
them .  Some packages like (/) for a starting position.  When a package
gets disoriented and cannot find existing directories this is sometimes
why.

-- 
Jude <dashielljt(at)gmpexpress-dot-net>

Re: More Problems Installing Speakup

[Steve Holmes]

When you run the checkout script, it expects to find a directory
/usr/src/linux.  Now that most recent kernels go into a directory
including the version number like linux-2.4.20, you would need to
create a symbolic link pointing linux to linux-2.4.20.  I did this
very step just the otherday and the checkout script went fine.  The
result of running the script will patch the actual speakup directories
within the linux source tree and not the speak-1.0 source.  

Now if you used CVS to download the entire patch collection instead of
running the checkout script, then you would put that directory (say
speakup-1.0.cvs for example) then run the install script from inside
the new speakup directory.  In any case, the patches are applied
directly to the linux source code itself.

After all that:) just run the usual 'make config' step like you always
do for a kernel compile.
-- 
Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: More Problems Installing Speakup

[Luke Davis]

I did this:

Tared the download of the CVS tree (comes down in a directory "speakup").
I then brought that to my (unconnected) Linux machine, and un-tarred it in
/usr/src, moved it to speakup-1.00 as the new directory name, and made a
simlink of "speakup" to it, just because.
I already knew that install expected /usr/src/linux, so I made that link
to the actual 2.4.20 source tree.
I then ran install, and got the output I forwarded.
Note that the directory listing I gave, was of /usr/src/speakup-1.00
(simlinked to speakup).

Regards,

Luke


On Sun, 2 Mar 2003, Steve Holmes wrote:

> When you run the checkout script, it expects to find a directory
> /usr/src/linux.  Now that most recent kernels go into a directory
> including the version number like linux-2.4.20, you would need to
> create a symbolic link pointing linux to linux-2.4.20.  I did this
> very step just the otherday and the checkout script went fine.  The
> result of running the script will patch the actual speakup directories
> within the linux source tree and not the speak-1.0 source.
>
> Now if you used CVS to download the entire patch collection instead of
> running the checkout script, then you would put that directory (say
> speakup-1.0.cvs for example) then run the install script from inside
> the new speakup directory.  In any case, the patches are applied
> directly to the linux source code itself.
>
> After all that:) just run the usual 'make config' step like you always
> do for a kernel compile.
>

Re: More Problems Installing Speakup

[Danny Crone]

How can I know which packages belong where?

At 08:43 3/2/03 -0500, you wrote:
>Some packages get particular as to where you need to be when you unpack
>them .  Some packages like (/) for a starting position.  When a package
>gets disoriented and cannot find existing directories this is sometimes
>why.
>
>--
>Jude <dashielljt(at)gmpexpress-dot-net>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: More Problems Installing Speakup

[Jude DaShiell]

When you changed accounts to root, did you also change ownership on that
rpm package to root before attempting the install?  chown root
filename.rpm will do it.

-- 
Jude <dashielljt(at)gmpexpress-dot-net>

Re: More Problems Installing Speakup

[William F. Acker WB2FLW +1-303-722-7209]

Jude: please tell the group why you think your advice below has any value 
what so ever!  An rpm package file is used as input to the rpm command.  
As long as the file can be read, and if you're root you can read any file 
no matter who owns it, the package will be installed, assuming all other 
criteria for the installation are met.
-- 
          Bill in Denver

On Mon, 3 Mar 2003, Jude DaShiell wrote:

> When you changed accounts to root, did you also change ownership on that
> rpm package to root before attempting the install?  chown root
> filename.rpm will do it.
> 
> 

Re: More Problems Installing Speakup

[Shaun Oliver]

*SNIP*
On Mon, 3 Mar 2003, Jude DaShiell wrote:

> When you changed accounts to root, did you also change ownership on
that
> rpm package to root before attempting the install?  chown root
> filename.rpm will do it.
>
>
I don't believe that shit above. like bill stated root can read any file
it wants so why go changing ownership and group when you don't have to.
let's get our information true and correct people, and yes I do it too
so that's as much my fault as the next person's.
the only time you'd want to chown a file is if you've copied it from one
users's dir to another and u can't access it for whatever reason.
oh well,
plenty more misinformation to go around I suppose,

-- 
Shaun Oliver


"We're upgrading /dev/null"


EMAIIL: shaun_oliver@optusnet.com.au
ICQ: 76958435
MSN: blindman_2001@hotmail.com
YAHOO: blindman01_2000