cygwin build_alias issue (and a possible workaround...)

Bogdan Vacaliuc bvacaliuc at ngit.com
Sat Sep 4 13:57:24 UTC 2004


Hi Scott,

Ugh.  You have a bizarre editor.  Your file contains some leading 0x240
characters.  I'm zipping you my file and attaching it.  Here's the analysis:

[/opt/rtems-4.6/bin] diff expr.sn expr.bv
1,12c1,10
< #!/bin/sh
< echo "Calling expr with" "$@" >> ${HOME}/expr.log
<
< if result=`/usr/bin/expr "$@"` ; then
<     echo "expr $@ result $result status 0" >> ${HOME}/expr.log
<     echo $result
<     exit 0;
< else
<     echo "expr $@ result $result status !0" >> ${HOME}/expr.log
<     echo $result
<     exit 1;
< fi
\ No newline at end of file
---
> #!/bin/sh
> if result=`/usr/bin/expr "$@"` ; then
>     echo "expr $@ result $result status 0" >> ${HOME}/expr.log
>     echo $result
>     exit 0;
> else
>     echo "expr $@ result $result status !0" >> ${HOME}/expr.log
>     echo $result
>     exit 1;
> fi
[/opt/rtems-4.6/bin] od -c expr.sn
0000000   #   !   /   b   i   n   /   s   h  \r  \n   e   c   h   o
0000020   "   C   a   l   l   i   n   g       e   x   p   r       w   i
0000040   t   h   "       "   $   @   "       >   >       $   {   H   O
0000060   M   E   }   /   e   x   p   r   .   l   o   g  \r  \n  \r  \n
0000100   i   f       r   e   s   u   l   t   =   `   /   u   s   r   /
0000120   b   i   n   /   e   x   p   r       "   $   @   "   `       ;
0000140       t   h   e   n  \r  \n 240 240 240       e   c   h   o
0000160   "   e   x   p   r       $   @       r   e   s   u   l   t
0000200   $   r   e   s   u   l   t       s   t   a   t   u   s       0
0000220   "       >   >       $   {   H   O   M   E   }   /   e   x   p
0000240   r   .   l   o   g  \r  \n 240 240 240       e   c   h   o
0000260   $   r   e   s   u   l   t  \r  \n 240 240 240       e   x   i
0000300   t       0   ;  \r  \n   e   l   s   e  \r  \n 240 240 240
0000320   e   c   h   o       "   e   x   p   r       $   @       r   e
0000340   s   u   l   t       $   r   e   s   u   l   t       s   t   a
0000360   t   u   s       !   0   "       >   >       $   {   H   O   M
0000400   E   }   /   e   x   p   r   .   l   o   g  \r  \n 240 240 240
0000420       e   c   h   o       $   r   e   s   u   l   t  \r  \n 240
0000440 240 240       e   x   i   t       1   ;  \r  \n   f   i
0000456
[/opt/rtems-4.6/bin] od -c expr.bv
0000000   #   !   /   b   i   n   /   s   h  \n   i   f       r   e   s
0000020   u   l   t   =   `   /   u   s   r   /   b   i   n   /   e   x
0000040   p   r       "   $   @   "   `       ;       t   h   e   n  \n
0000060                   e   c   h   o       "   e   x   p   r       $
0000100   @       r   e   s   u   l   t       $   r   e   s   u   l   t
0000120       s   t   a   t   u   s       0   "       >   >       $   {
0000140   H   O   M   E   }   /   e   x   p   r   .   l   o   g  \n
0000160               e   c   h   o       $   r   e   s   u   l   t  \n
0000200                   e   x   i   t       0   ;  \n   e   l   s   e
0000220  \n                   e   c   h   o       "   e   x   p   r
0000240   $   @       r   e   s   u   l   t       $   r   e   s   u   l
0000260   t       s   t   a   t   u   s       !   0   "       >   >
0000300   $   {   H   O   M   E   }   /   e   x   p   r   .   l   o   g
0000320  \n                   e   c   h   o       $   r   e   s   u   l
0000340   t  \n                   e   x   i   t       1   ;  \n   f   i
0000360  \n
0000361

> >SharedSection=1024,3072,128,128
> 
> SharedSection=1024,3072,512,512 

That should be ok; its what I started out with; I've been trying to 'stress'
my system.

> >Its going to be a long weekend...
> 
> Absolutely.

:)

I wait for your results...

-bogdan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: expr.gz
Type: application/x-gzip
Size: 147 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20040904/ecf37ac3/attachment-0001.bin>


More information about the users mailing list