From: William Sundberg <william@...4trade.com>
Date: 2004-01-28T04:51:01+09:00
Subject: Re: ./configure problem

Sorry my fault, "patch" is a script/pgm I shuld have looked in the old
arcives.

Thank you/William

On Tue, 2004-01-27 at 20:43, William Sundberg wrote:
> Thank you again, now I feel even more stupid. I tried with this. Cut out
> the text from the first mail(the patch) and put it in a "file".
> -----------file: patch_m
> @@ -120,3 +120,3 @@ maybe_os=`echo $1 | sed 's/^\(.*\)-\([^-
>  case $maybe_os in
> -  nto-qnx* | linux-gnu* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* |
> os2-emx* | rtmk-nova*)
> +  nto-qnx* | linux-* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* |
> os2-emx* | rtmk-nova*)
>      os=-$maybe_os
> -----------
> Then I tried the following without luck:
> [william@localhost ruby-1.8.1]$ config.sub < patch_m
> bash: config.sub: command not found
> [william@localhost ruby-1.8.1]$ patch_m < config.sub
> bash: patch_m: command not found
> [william@localhost ruby-1.8.1]$ chmod +x patch_m
> [william@localhost ruby-1.8.1]$ patch_m < config.sub
> bash: patch_m: command not found
> 
> 
> What am I missing?
>  
> On Tue, 2004-01-27 at 20:19, benny wrote:
> > Am Wed, 28 Jan 2004 04:02:16 +0900
> > schrieb William Sundberg <william@m4trade.com>:
> > 
> > > Thank you for your reply but how do you "try this patch"? Should I add
> > > this lines in config.sub if so where?
> > 
> > usually you can patch a patch with
> > 
> > patch < patch.file
> > 
> > just make sure that the filenames in the patch file (e.g. config.sub) can be found
> > 
> > benny
> > 
> > 
> > 
> 
> 
> 
> 
>