mingw-msys Mailing List for MinGW - Minimalist GNU for Windows

I have successfully installed MSYS/MinGW under Windows Vista x64 using 
the following procedure.  If there is an easier way to do this please 
let me know.

1) Download and execute the following file:

  MSYS-1.0.10.exe

  When it asks you to continue with the post install press 'n' because
  it will fail if you are running Windows Vista.  Attempting to run MSYS 
now
  will also fail under Vista (you will get around 120 cascading windows 
that
  will all terminate).

2) Download the following file and untar the contents over your MSYS
  installation.  This will fix the cascading windows problem under Vista.

  MSYS-1.0.11-20071204.tar.bz2

3) Download and execute the following file:

  msysDTK-1.0.1.exe

  This contains additional MSYS utilites such as ftp, telnet, and perl.

4) Open an MSYS window and type the following:

  mv /bin/ftp /bin/ftp.old

  This will allow you to use the MSYS version of ftp instead of the Windows
  version of ftp (which spawns and opens in a Windows console).

5) Download the following files and copy them to c:\mingw:

  binutils-2.18.50-20080109-2.tar.gz
  gcc-core-3.4.5-20060117-3.tar.gz
  mingw-runtime-3.14.tar.gz
  w32api-3.11.tar.gz

6) Open an MSYS window and execute the following commands:

  cd /c/mingw
  gzip -d *.gz
  find -name '*.tar' -exec tar -xvf {} \;
  rm *.tar
  echo 'C:/mingw /mingw' > /etc/fstab

  The first four lines untar the archives and delete them while the last 
line
  sets up the mount point for mingw (you need to do this manually since you
  aborted the post install for MSYS).

On 2008-04-25 08:09Z, vasilios anagnostopoulos wrote:
> 
> Do you have any idea why makefiles had :: instead of :
> for targets (although this created no erros )?

http://www.gnu.org/software/make/manual/html_node/Double_002dColon.html

CSMake worked fine. 

Do you have any idea why makefiles had :: instead of :
for targets (although this created no erros )?

Thanks for your great help.


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

vasilios anagnostopoulos wrote:
> Hi all I tried to build xereces_2_8_0 from source with
> msys/mingw combination. Previously this was not a
> problem.
> 
> With the latest releases of msys which I list in the
> attachments I get the following errors when I  run
> make
> 
> keep in mind that I put gcc-sjlj, g++-sjlj as
> compilation options
> 
> "THE ERROR"
> 
> Makefile.incl:1168: warning: overriding commands for
> target `.c.o'
> Makefile.incl:1165: warning: ignoring old commands for
> target `.c.o'

It seems to me this makefile is using case sensitive patterns. Please 
try typing "csmake" instead of "make". Does this helps?

Regards,

Cesar

Hi all I tried to build xereces_2_8_0 from source with
msys/mingw combination. Previously this was not a
problem.

With the latest releases of msys which I list in the
attachments I get the following errors when I  run
make

keep in mind that I put gcc-sjlj, g++-sjlj as
compilation options

"THE ERROR"

Makefile.incl:1168: warning: overriding commands for
target `.c.o'
Makefile.incl:1165: warning: ignoring old commands for
target `.c.o'
makefile:71: *** target file `ALL' has both : and ::
entries.  Stop.

Any ideas?


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

On Friday 04 April 2008 18:14, Ryan Rosario wrote:
> I have a student that is trying to use GRASS via MSYS. He has Windows
> XP. When he tries to load the GRASS shell, a black box appears with a
> cursor, but no command prompt.

I've no idea what GRASS is, but this sounds like a manifestation of the 
broken pty emulation in the MSYS implementation of RXVT; is your 
student using rxvt.exe to provide the MSYS console?  If so, try 
removing rxvt.exe from the MSYS /bin directory, and run in a native 
Win32 console window.

> When he attempts to run GRASS, anything that requires the command
> prompt causes GRASS to hang.

More likely, it is just waiting for user input, the prompt having been 
written to stdout, but buffered in the pipe used to emulate the pty, 
and therefore not flushed to the display.

> Has anybody experienced MSYS not loading a command prompt?

No, but I have been plagued by the broken behaviour of RXVT, so I just 
don't use it, ever.

> Any ideas on a solution?

Get rid of RXVT, and run in a native Win32 console.  If you don't like 
that, check this archived posting:
http://article.gmane.org/gmane.comp.gnu.mingw.msys/3930

for tips on making it more presentable, or try console2, from:
https://sourceforge.net/projects/console

Regards,
Keith.

--- Brian Dessent <br...@de...> wrote:

> Tripp wrote:
> 
> >     
>
c:/mingw/bin/../lib/gcc/mingw32/4.2.3/../../../../include/windef.h:234:
> >      error: two or more data types in declaration specifiers
> >
> > 
> > can anyone help me with any pointerson whats needed here?
> 
> 1. Please don't sent HTML email.
> 
> 2. This has nothing to do with MSYS, so I'd suggest using the MinGW
> list
> instead.

i picked this one cause i thought it was more general,
 
> 3. What is line 234 of your version of windef.h?

typedef unsigned long DWORD;
typedef int WINBOOL,*PWINBOOL,*LPWINBOOL;
/* FIXME: Is there a good solution to this? */
#ifndef XFree86Server
#ifndef __OBJC__
typedef WINBOOL BOOL;                     ******!!!! Line 234 ****
#else
#define BOOL WINBOOL
#endif
typedef unsigned char BYTE;
#endif /* ndef XFree86Server */
typedef BOOL *PBOOL,*LPBOOL;
typedef unsigned short WORD;
typedef float FLOAT;
typedef FLOAT *PFLOAT;
typedef BYTE *PBYTE,*LPBYTE;
typedef int *PINT,*LPINT;
typedef WORD *PWORD,*LPWORD;
typedef long *LPLONG;
typedef DWORD *PDWORD,*LPDWORD;
typedef CONST void *PCVOID,*LPCVOID;
typedef int INT;
typedef unsigned int UINT,*PUINT,*LPUINT;

#include <winnt.h>

typedef UINT_PTR WPARAM;
typedef LONG_PTR LPARAM;
typedef LONG_PTR LRESULT;
#ifndef _HRESULT_DEFINED
typedef LONG HRESULT;
#define _HRESULT_DEFINED
#endif
#ifndef XFree86Server
typedef WORD ATOM;
#endif /* XFree86Server */
 
> 4. What is the preprocessed output of that line?  (use -save-temps or
> -E)

adding -E to the last command gives me nothing on the console.
and i think it creates 2 files
-save-temps gives me the same error as make and
3 files are created as far as i can see.
is interface.tpo the one of interest?
anyway i tried including them all in zip attachments,
and the message was bounced.
is it the zip format specifically, or all attachments?

 
> Brian
 
 
ty
tripp


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

Hy all,

I have this strange problem: I use
*   cp --recursive --preserve //smbserver/sharename/directory ./
*to copy a new project from another computer in my network onto my computer,
and the resulting directory tree has many of the files different from the
source directory.

It must be that the line endings are converted, because a text compare will
find no differences, only the binary compare will show differences. The
problem is it happens even with zip files, and it does not happen with some
of the text files. If I copy from the local file system things are ok. I
have Windows XP at work and if I use Copy/Paste in Windows Explorer than the
resulting copy is ok.

Do you know about this problem. How can I tell *cp* or any underlaying
library to treat all files as binary ?

(sorry I do not know which list (mingw/msys) is appropriate for my question,
please reply in the right list)

Thank you,
Timothy Madden

James Kanze a écrit :
> This has probably been asked before, but how can I set the font
> in the MSys window (and what fonts are available)?  I can see in
> the msys.bat file that the shell is started with a -fn option,
> but I have no idea what is available in the line of fonts, nor
> how to specify them.
> 
> FWIW: in my _gvimrc, I have the GUI font set to
> Lucida_Console:h9:cANSI, which results in the font I want.  I
> tried replacing the '-fn Courier-12' with '-fn Lucida_Console-9'
> in the .bat; this gave more or less the font I wanted, but with
> an extra blank after each character.  I seem to recall having
> had similar problems sometime in the past with vim, and I think
> that it is the cANSI which does the trick.  But how do I specify
> this for MSys?
> 

I guess Lucida_Console is a multibyte font and not well handled by rxvt 
(it requires ASCII fonts). Switching to a plain Win32 Console and 
changing the font is likely to be easier.

Myself, I use Console2 (found on sourceforge) that decorate win32 
consoles to allow tabbed widows and easy resize.
http://sourceforge.net/projects/console/

A little change in the msys.bat launcher: (I put Console2 in a 
/opt/Console2 directory at the root of msys)
-----------------------------
#line 40
if EXIST bin\nul cd bin
if EXIST ..\opt\Console2\Console.exe goto startconsole
if EXIST rxvt.exe goto startrxvt
if EXIST sh.exe goto startsh

echo Cannot find the Console.exe, rxvt.exe or sh.exe binary -- aborting.
pause
exit 1

rem If you don't want to use Console then rename the file Console.exe to 
something
rem else.  Then sh.exe will be used instead.
:startconsole

start ..\opt\Console2\Console.exe -w MSYS -c ..\opt\Console2\console.xml 
-t bash
exit
--------------------------------

The console.xml file is generated from Console2. The relevant part to 
Msys is in tabs:
---------------------------
<tabs>
	<tab title="bash">
		<console shell="sh.exe --login -i" init_dir=""/>
		<cursor style="0" r="255" g="255" b="255"/>
		<background type="0" r="0" g="0" b="0">
		<image file="" relative="0" extend="0" position="0">
				<tint opacity="0" r="0" g="0" b="0"/>
			</image>
		</background>
	</tab>
...
----------------------------

Michael

Peter Selinger wrote:

> I am not sure if this list is the correct place for bug reports.

This is code from newlib, and the version of newlib that MSYS includes
is extremely old, from 2001-09-07 as far as I can tell.  Maybe at some
point it would be a good idea to import a more fresh copy of newlib into
the tree.

> I found the following code in the floating point library
> newlib/libm/mathfp/sf_isinf.c:
> 
> int isinff (float x)
> {
>   __uint32_t wx;
>   int exp;
> 
>   GET_FLOAT_WORD (wx, x);
>   exp = (wx & 0x7f800000) >> 23;
> 
>   if ((exp == 0x7f8) && !(wx & 0xf0000))
>     return (1);
>   else
>     return (0);
> }

Current newlib has this:

int
_DEFUN (isinff, (x),
        float x)
{
        __int32_t ix;
        GET_FLOAT_WORD(ix,x);
        ix &= 0x7fffffff;
        return FLT_UWORD_IS_INFINITE(ix);
}

It looks like this change was made when the file was moved from mathfp/
to common/ around 2006-02-26:

<http://sourceware.org/cgi-bin/cvsweb.cgi/src/newlib/libm/common/sf_isinff.c?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=src>
<http://sourceware.org/ml/newlib/2006/msg00132.html>

Brian

Tripp wrote:

>      c:/mingw/bin/../lib/gcc/mingw32/4.2.3/../../../../include/windef.h:234:
>      error: two or more data types in declaration specifiers
>
> 
> can anyone help me with any pointerson whats needed here?

1. Please don't sent HTML email.

2. This has nothing to do with MSYS, so I'd suggest using the MinGW list
instead.

3. What is line 234 of your version of windef.h?

4. What is the preprocessed output of that line?  (use -save-temps or
-E)

Brian

tripp <el...@ya...> wrote: hello,

i've been trying to compile lame-3.98beta6 on win xp2,
using msys (1.0.11(0.46/3/2) 2007-12-05 00:35 i686 Msys)
added cureutils 5.97and bash 3.1
with mingw (4.2.3 tdragonbuild, but used technology preview as well)
added binutils 2.18.50, runtime 3.14, w32api 3.1

compiling fails on 'make' :

/bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H  -I. -I.. -I../include -I. -I../libmp3lame -I..    -O3 -fomit-frame-pointer -ffast-math       -maccumulate-outgoing-args -Wall -pipe  -MT interface.lo -MD -MP -MF .deps/interface.Tpo -c -o interface.lo interface.c
 gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I. -I../libmp3lame -I.. -O3 -fomit-frame-pointer -ffast-math -maccumulate-outgoing-args -Wall -pipe -MT interface.lo -MD -MP -MF .deps/interface.Tpo -c interface.c -o interface.o
In file included from  c:/mingw/bin/../lib/gcc/mingw32/4.2.3/../../../../include/windows.h:48,
                 from ../libmp3lame/machine.h:130,
                 from interface.c:15:
c:/mingw/bin/../lib/gcc/mingw32/4.2.3/../../../../include/windef.h:234: error: two or more data types in declaration specifiers
make[2]: *** [interface.lo] Error 1
make[2]: Leaving directory `/c/test/lame-3.98b6/mpglib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/test/lame-3.98b6'
make: *** [all] Error 2


in windef.h:

typedef unsigned long DWORD;
typedef int WINBOOL,*PWINBOOL,*LPWINBOOL;
/* FIXME: Is there a good solution to this? */
#ifndef XFree86Server
#ifndef __OBJC__
typedef WINBOOL BOOL;
#else
#define BOOL WINBOOL
#endif
typedef unsigned char BYTE;
#endif /*  ndef XFree86Server */
typedef BOOL *PBOOL,*LPBOOL;
typedef unsigned short WORD;
typedef float FLOAT;
typedef FLOAT *PFLOAT;
typedef BYTE *PBYTE,*LPBYTE;
typedef int *PINT,*LPINT;
typedef WORD *PWORD,*LPWORD;
typedef long *LPLONG;
typedef DWORD *PDWORD,*LPDWORD;
typedef CONST void *PCVOID,*LPCVOID;
typedef int INT;
typedef unsigned int UINT,*PUINT,*LPUINT;


is there something i could do to windef.h 
to force compiling to work?


thanks

tripp

------------------

can anyone help me with any pointerson whats needed here?

tripp

        

Hi,

I am not sure if this list is the correct place for bug reports.  
I found the following code in the floating point library
newlib/libm/mathfp/sf_isinf.c:

int isinff (float x)
{
  __uint32_t wx;
  int exp;

  GET_FLOAT_WORD (wx, x);
  exp = (wx & 0x7f800000) >> 23;

  if ((exp == 0x7f8) && !(wx & 0xf0000))
    return (1);
  else
    return (0);
}

Note that exp can never equal 0x7f8, so this function always returns 0.
What was probably meant was either >> 20, or exp == 0xff.

-- Peter

On Sun, 13 Apr 2008 20:09:33 -0700, Brian Dessent wrote:
> There are two flavors of the autotools, see
> <http://thread.gmane.org/gmane.comp.gnu.mingw.msys/4309/focus=4324>.

OK, that's *much* clearer now.  Thanks a lot for the link.

<Snipped>
> wget works just fine with sourceforge, e.g.
>
> $ for pkg in autoconf-2.61 automake-1.10 libiconv-1.11 \
> gettext-0.16.1 gettext-devel-0.16.1; do \
> wget -nv \
> http://downloads.sourceforge.net/mingw/$pkg-MSYS-1.0.11.tar.bz2; \
> done
>
> The downloads.sourceforge.net URL above will http-redirect to a
> random mirror.  You can also just pick your desired mirror URL and
> use that directly as sometimes you get redirected to a mirror very
> far from you.

And thanks for that as well.

Regards,

Peter

"Peter J. Farley III" wrote:

> I'm a bit confused.  Aren't all the tools in that directory MSYS
> builds?  Or are only the ones marked MSYS truly MSYS builds?
> 
> If so, does that mean the *-bin-* builds are for mingw only, and
> therefore should go into the mingw/bin directory, as opposed to the
> msys/bin directory?

There are two flavors of the autotools, see
<http://thread.gmane.org/gmane.comp.gnu.mingw.msys/4309/focus=4324>.

> BTW, is there an easier way than the sourceforge DL pages to get all
> those files one by one?  Could I use wget and put together a script to
> just get them all at one go?  If so, what would I use for the url?  Or
> is there an ftp alternative?

wget works just fine with sourceforge, e.g.

$ for pkg in autoconf-2.61 automake-1.10 libiconv-1.11 \
             gettext-0.16.1 gettext-devel-0.16.1; do \
  wget -nv \
  http://downloads.sourceforge.net/mingw/$pkg-MSYS-1.0.11.tar.bz2; \
  done

The downloads.sourceforge.net URL above will http-redirect to a random
mirror.  You can also just pick your desired mirror URL and use that
directly as sometimes you get redirected to a mirror very far from you.

Brian

On Sun, 13 Apr 2008 22:59:26 -0200, Cesar Strauss wrote:
> Peter J. Farley III wrote:
>> So should the msysCORE be installed first and the coreutils
>> snapshot laid over that?  Should the coreutils contents be copied
>> after extracting the archive to the regular msys directories?
>
> Correct on both accounts.

Thanks for the reply and the confirmation.

>> What about the individual utility sets like findutils and
>> diffutils? Should they be installed over the msysCORE and
>> coreutils snapshot, or instead of one or both of them, or not at
>> all?
>
> They should be installed over.

Thanks again.

>> And I have similar questions for the DTK utilities.  Should I use
>> autoconf-2.5-2.61 or autoconf-2.1-2.13?  automake-1.9 or automake-
>> 1.10 or automake-3-1?  Should I install gettext-1.16.1-1.bin or
>> gettext-0.16.1-MSYS-1.0.11-1?
>>
>>
> You can safely install all of the above. automake-3-1 is a wrapper
> script which calls autoconf-2.5-2.61 or autoconf-2.1-2.13 as
> appropriate, dependent on the requirements of the particular source
> package you are building. Likewise for automake-3-1.
>
> As for gettext-1.16.1-1-bin, it provides autopoint, which is
> another autotool you may need. The gettext-0.16.1-MSYS-1.0.11-1, on
> the other hand, is a MSYS build. You can install it as well, other
> MSYS-built tools may depend on it.

I'm a bit confused.  Aren't all the tools in that directory MSYS 
builds?  Or are only the ones marked MSYS truly MSYS builds?

If so, does that mean the *-bin-* builds are for mingw only, and 
therefore should go into the mingw/bin directory, as opposed to the 
msys/bin directory?

> Note that you don't need to install all of the DTK tools, you can
> pick those you really need. You may find, however, that some tools
> have dependencies you need to install as well. A safe bet is to
> install them all.

Yes, that would be a my thought as well.  I like a robust build 
environment that will handle whatever I need to throw at it.

BTW, is there an easier way than the sourceforge DL pages to get all 
those files one by one?  Could I use wget and put together a script to 
just get them all at one go?  If so, what would I use for the url?  Or 
is there an ftp alternative?

Many thanks for your cogent and prompt answers.

Regards,

Peter

Peter J. Farley III wrote:
> So should the msysCORE be installed first and the coreutils snapshot 
> laid over that?  Should the coreutils contents be copied after 
> extracting the archive to the regular msys directories?

Correct on both accounts.

> What about the individual utility sets like findutils and diffutils? 
>  Should they be installed over the msysCORE and coreutils snapshot, or 
> instead of one or both of them, or not at all?

They should be installed over.

>  
> And I have similar questions for the DTK utilities.  Should I use 
> autoconf-2.5-2.61 or autoconf-2.1-2.13?  automake-1.9 or automake-1.10 
> or automake-3-1?  Should I install gettext-1.16.1-1.bin or 
> gettext-0.16.1-MSYS-1.0.11-1?
>

You can safely install all of the above. automake-3-1 is a wrapper 
script which calls autoconf-2.5-2.61 or autoconf-2.1-2.13 as 
appropriate, dependent on the requirements of the particular source 
package you are building. Likewise for automake-3-1.

As for gettext-1.16.1-1-bin, it provides autopoint, which is another 
autotool you may need. The gettext-0.16.1-MSYS-1.0.11-1, on the other 
hand, is a MSYS build. You can install it as well, other MSYS-built 
tools may depend on it.

Note that you don't need to install all of the DTK tools, you can pick 
those you really need. You may find, however, that some tools have 
dependencies you need to install as well. A safe bet is to install them all.

Regards,

Cesar

My most sincere apologies to the whole list for sending the prior 
version of this email in HTML.  Mea maxima culpa!  I forgot to set my 
mail client to plain text.  Hopefully this will come to you plain text 
as it should have in the first place.


Hi all,
 
I have been reading as many messages related to installation of msys 
as I can in the mingw-msys archive, but I did not see any posts that 
describe which MSYS-1.0.11 files should be installed in which order to 
update a base msys-1.0.10 system to whatever the current state of 
msys-1.0.11 may or should be.
 
I have used MinGW-5.1.3.exe to install gcc and g++, then installed 
MSYS-1.0.11.exe as recommended.  My directory structure is also as 
recommended, c:\msys\1.0 for msys and c:\msys\1.0\mingw for gcc and 
g++.  I DL'd and ran msysDTK-1.0.1.exe as well.
 
Now I would like to update to msys-1.0.11 as far as possible, so I 
DL'd all the "Technology Preview" *.tar.gz or *.tar.bz2 files on the 
download page under MSYS Base System, but there isn't a reference 
anywhere I could find that indicates in what order these archives 
should be installed, if any order is needed.
 
In particular, I now have both msysCORE-1.0.11-2007.01.19-1.tar.bz2 
and coreutils-5.97-MSYS-1.0.11-snapshot.tar.bz2.  The msysCORE archive 
seems to have about half the utilities dated 2002 and 2003 and the 
rest in January 2007, while the base msys-1.1.10 installed all the 
core utilities dated in March 2004.  The coreutilis snapshot has many 
of the same utilities (but not all of them) dated in August 2007. 
 Plus the coreutils snapshot has a different directory structure, with 
an extra level named "coreutils-5.97" above the bin/doc/info/lib 
directories.
 
So should the msysCORE be installed first and the coreutils snapshot 
laid over that?  Should the coreutils contents be copied after 
extracting the archive to the regular msys directories?
 
What about the individual utility sets like findutils and diffutils? 
 Should they be installed over the msysCORE and coreutils snapshot, or 
instead of one or both of them, or not at all?
 
And I have similar questions for the DTK utilities.  Should I use 
autoconf-2.5-2.61 or autoconf-2.1-2.13?  automake-1.9 or automake-1.10 
or automake-3-1?  Should I install gettext-1.16.1-1.bin or 
gettext-0.16.1-MSYS-1.0.11-1?
 
If there is a page or a message or set of messages I need to read to 
clear up my confusion, please point me to them and I will do so.
 
TIA for any help you can provide.
 
Regards,
 
Peter

<html><head><meta name="Generator" content="PSI HTML/CSS Generator"/>
<style type="text/css"><!--
body{font-family:'Arial';font-size:10pt;font-color:'#000000';}
LI{display:list-item;margin:0.00in;}
p{display:block;margin:0.00in;}
body{}
--></style>
</head><BODY BGCOLOR="#F0F0F0" ><div><SPAN style="font-size:10pt;">Hi all,</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">I have been reading as many messages related to installation of msys as I can in the mingw-msys archive, but I did not see any posts that describe which MSYS-1.0.11 files should be installed in which order to update a base msys-1.0.10 system to whatever the current state of msys-1.0.11 may or should be.</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">I have used MinGW-5.1.3.exe to install gcc and g++, then installed MSYS-1.0.11.exe as recommended. &#160;My directory structure is also as recommended, c:\msys\1.0 for msys and c:\msys\1.0\mingw for gcc and g++. &#160;I DL'd and ran msysDTK-1.0.1.exe as well.</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">Now I would like to update to msys-1.0.11 as far as possible, so I DL'd all the "Technology Preview" *.tar.gz or *.tar.bz2 files on the download page under MSYS Base System, but there isn't a reference anywhere I could find that indicates in what order these archives should be installed, if any order is needed.</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">In particular, I now have both msysCORE-1.0.11-2007.01.19-1.tar.bz2 and coreutils-5.97-MSYS-1.0.11-snapshot.tar.bz2. &#160;The msysCORE archive seems to have about half the utilities dated 2002 and 2003 and the rest in January 2007, while the base msys-1.1.10 installed all the core utilities dated in March 2004. &#160;The coreutilis snapshot has many of the same utilities (but not all of them) dated in August 2007. &#160;Plus the coreutils snapshot has a different directory structure, with an extra level named "coreutils-5.97" above the bin/doc/info/lib directories.</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">So should the msysCORE be installed first and the coreutils snapshot laid over that? &#160;Should the coreutils contents be copied after extracting the archive to the regular msys directories?</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">What about the individual utility sets like findutils and diffutils? &#160;Should they be installed over the msysCORE and coreutils snapshot, or instead of one or both of them, or not at all?</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">And I have similar questions for the DTK utilities. &#160;Should I use autoconf-2.5-2.61 or autoconf-2.1-2.13? &#160;automake-1.9 or automake-1.10 or automake-3-1? &#160;Should I install gettext-1.16.1-1.bin or gettext-0.16.1-MSYS-1.0.11-1?</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">If there is a page or a message or set of messages I need to read to clear up my confusion, please point me to them and I will do so.</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">TIA for any help you can provide.</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">Regards,</SPAN></div>
<div>&nbsp;</div>
<div><SPAN style="font-size:10pt;">Peter</SPAN></div>
</body></html>

bas...@gm... wrote:

> How do I get these values: 'U:\msys\1.0', 'U:\MinGW'?
> For now three solutions come to mind: edit msys.bat or parse the second line of 'set' command output
> $ set
> !::='::\'
> !U:='U:\msys\1.0\bin'
> 
> or parse the 'mount' command output

You're overthinking it.  Path translation is MSYS' bread and butter.

msysroot=`cd / && pwd -W`
mingwroot=`cd /mingw && pwd -W`

Brian

How do I get these values: 'U:\msys\1.0', 'U:\MinGW'?
For now three solutions come to mind: edit msys.bat or parse the second line of 'set' command output
$ set
!::='::\'
!U:='U:\msys\1.0\bin'

or parse the 'mount' command output

Greg Chicares wrote:
> On 2008-04-08 18:51Z, bas...@gm... wrote:
>> command:
>> for i in ; do echo $i; done
>> works on linux and error on msys.
> 
> Reproduced with this MSYS shell:
>   GNU bash, version 2.04.0(1)-release (i686-pc-msys)
> 
> FWIW, it's not reproducible with these Cygwin shells:
>   GNU bash, version 2.05a.0(2)-release (i686-pc-cygwin)
>   GNU bash, version 3.2.33(18)-release (i686-pc-cygwin)
>   zsh 4.3.2 (i686-pc-cygwin)
> 
> You might like to try the MSYS bash-3.1 "technology preview".

That bash-3.1-MSYS-1.0.11-1.tar.bz2 does seem to work:
$ for i in ; do echo $i; done ; echo $?
0

...or you could just fix the offending scripts.


-- 
Tuomo

... dftpnkezln: For all of you reporting a score more than 100 as you iq
                 lol @ you. How can you possibly score more than 100%?
     dftpnkezln: I'm very happy with my score of 89.
                                                -- http://bash.org/?758032

anyone try building nano for msys? I would like to recommend this to some
classmates however they wouldn't want to learn vi(m) now. also I've been
thinking about doing some dev on msys (and the msys git project), has anyone
tried msys in wine? I don't actually use windows much out of class.

-- 
Caleb Cushing

This email was made using the gmail interface and is not pgp signed,
therefore is not an 'official' email.

On 2008-04-08 18:51Z, bas...@gm... wrote:
> command:
> for i in ; do echo $i; done
> works on linux and error on msys.

Reproduced with this MSYS shell:
  GNU bash, version 2.04.0(1)-release (i686-pc-msys)

FWIW, it's not reproducible with these Cygwin shells:
  GNU bash, version 2.05a.0(2)-release (i686-pc-cygwin)
  GNU bash, version 3.2.33(18)-release (i686-pc-cygwin)
  zsh 4.3.2 (i686-pc-cygwin)

You might like to try the MSYS bash-3.1 "technology preview".

command:
for i in ; do echo $i; done
works on linux and error on msys. it can be found in some makefiles
when a variable with a set is empty:
#Makefile
all-run:
        @for d in $(PHP_EXT_LIST); do \
           if [ -d $$d ]; then \
             export UNSAFE; \
             echo "making extension $$d ..."; \
             (cd $$d && $(MAKE) all-run); \
           fi \
        done