Re: [Mingw-msys] Defferences between MSYS and GNUWin32 sed's

[Earnie B. <ea...@us...>]

E. Weddington wrote:

>On 4 Mar 2004 at 7:45, Earnie Boyd wrote:
>
>  
>
>>Dave Hylands wrote:
>>
>>    
>>
>>>Hi Neil,
>>>
>>>This is slightly off topic since it isn't really related to MinGW, but I
>>>use cygwin quite extensively. I'll admit that it does have it's quirks,
>>>but it sure is nice to be able to use a bash shell and all of the
>>>utilities that go along with it. It makes switching between Linux and
>>>Windows much more palatable. Even though cmd.exe has improved over the
>>>years, it still doesn't compare to bash.
>>> 
>>>
>>>      
>>>
>>And MSYS uses bash as its shell.
>>
>>    
>>
>
>
>However, you default to using rxvt as the shell. I have had packages that fail to configure or 
>make using rxvt, but work fine in bash. And you don't provide an easy, hands-off way to specify 
>using bash beyond: "rename rxvt.exe to something else so the batch file will call bash instead".
> 
>  
>
Rxvt is not a shell, it spawns sh by default and uses pipes to 
communicate to it.  It is a ``Video Terminal'' application.  I know that 
the pty emulation is broken, that is the top of the list issue for 
version 1.0.11.  The rename bit was a suggested workaround for a known 
problem that would eventually be fixed.  Another workaround would be to 
``start sh --login'' from the rxvt window for the few times you have 
problems building an application because of rxvt problems.  Rxvt itself 
provides the Windows user with the Windows experience of being able to 
easily copy and paste, even in UNIX three button mouse style.  It has 
many benefits, including displaying the text faster to the Video 
Terminal than the default console.

>>>I prefer to use native tools (i.e. tools which don't use the
>>>cygwin1.dll) from vendors (which is where MinGW comes into play) because
>>>getting tools which use different versions of the cygwin1.dll to coexist
>>>in a complex build environment is not for the faint of heart (but I've
>>>done it).
>>> 
>>>
>>>      
>>>
>>And MSYS has taken out the pain for coexistence.  You can even have 
>>different mount tables.  MSYS also reports its system name as MINGW32 so 
>>that the configure script gets the build environment correctly 
>>identified for MinGW.  With Cygwin you have to specify --host, --target 
>>and --build to configure the build natively for MinGW..
>>    
>>
>
>What about when you do in Cygwin?:
>
>export CC="gcc -mno-cygwin"
>configure --target=foo
>make
>
>Won't that build natively for MinGW? Or do you also have to put in the --host and --build flags 
>as well?
>
>  
>
The build and host environments would be ``cygwin'' and not ``mingw32'' 
which would cause you to be in a ``cross-compile'' environment.  You 
need to specify the --host and --build flags to allow the configure 
script to build the Makefile for a native build.

>Another question I've been wondering about: When building GCC, in Cygwin, but using the 
>above to build using MinGW, will the resulting GCC be able to be relocated to a different 
>installation directory? This works (relocating to different install dir) when using MSYS 1.0.8-rc2, 
>but not later versions due to bug #671479 (assigned to earnie and still not fixed, even though 
>some analysis has been done).
>  
>
I had a question asked for 671479 on 2/24/2004 that is unanswered.  Yes, 
you should be able to build and move the components.

Earnie.

-- 
http://www.mingw.org
http://sourceforge.net/projects/mingw
https://sourceforge.net/donate/index.php?user_id=15438