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

Quoting "Schwarz, Konrad" <kon...@si...>:

>
> By the way, any idea why //localhost/C$ doesn't work?
>

You need to define it in your $SYSTEMROOT/system32/drivers/etc/hosts file.

Earnie Boyd

http://shop.siebunlimited.com

Quoting "Schwarz, Konrad" <kon...@si...>:

>> Quoting "Schwarz, Konrad" <kon...@si...>:
>>
>> > MinGW: `/d/dir1/../../c/dir2/file' fails.  For the cross-generation
>>
>> Since it works for me with ls, I need a reduced example that
>> fails.
>
> I apologize for this misinformation.  MinGW handles it correctly.  It
> doesn't show the volumes as subdirectories of / though, which `ls
> /cygdrive' or `ls /dev/fs' does on Cygwin/Interix.
>

A workaround would be to create the mount point directories for each 
drive letter in your MSYS root.  Assuming your root is c:/msys/1.0, you 
can create /c, /d, etc by ``mkdir /c/msys/1.0/c''.

Earnie Boyd

http://shop.siebunlimited.com

> > > The proposed mapping for directory `C:\' is `//./C$/' (or perhaps=20
> > > `//./C/').
>=20
> > So... why exactly do you need this? The only thing I might actually=20
> > support here (keeping in mind Eric's comments and CGF's clear=20
> > agreement with them) would be treating '//./' as a special case of=20
> > '//127.0.0.1/', at which point '//./C$/' is the UNC mapping of the=20
> > default 'C$' share on the local machine. But I still fail=20
> to see why=20
> > that is useful.

For the record, the //127.0.0.1/C$ solution is probably good enough for
me.  I therefore retract my proposal.

By the way, any idea why //localhost/C$ doesn't work?

Also, someone called Interix a POS, which I can't find on
http://cygwin.com/acronyms, but I guess is derogatory (I originally
though "POsix Simulation" or something, to tell the truth).  Is there a
list of reasons of the drawbacks of Interix somewhere?

Regards,

Konrad Schwarz

> Quoting "Schwarz, Konrad" <kon...@si...>:
>=20
> > MinGW: `/d/dir1/../../c/dir2/file' fails.  For the cross-generation
>=20
> Since it works for me with ls, I need a reduced example that=20
> fails.

I apologize for this misinformation.  MinGW handles it correctly.  It
doesn't show the volumes as subdirectories of / though, which `ls
/cygdrive' or `ls /dev/fs' does on Cygwin/Interix.

Regards,

Konrad Schwarz

Earnie Boyd wrote, quoting me:
>>
>>  bind '"\e[A":history-search-backward'
>>  bind '"\e[B":history-search-forward'
>>
>> to emulate the history search behaviour of the `4DOS' shell I used
>> at one time with MS-DOS: type the first few characters of a command,
>> then use <Cursor-Up> and <Cursor-Down> to find and replay matching
>> commands in the history.
>
> I like to set my command mode vi style ``set -o vi'' and then use 
> ``<esc>/stringToSearch'' to enter search mode.  I can then use ``n''
> to search forward and ``N'' to search reverse.  You can even use the
> <esc> key to enter a substitution command.

I used to have `set -o vi' for Korn shell, on a Solaris box I administer,
but with bash, I find the `emacs' style works better for me, (even though
I much prefer `vi' to `emacs' as my working editor).

I liked the 4DOS history search method, when I used that, and the two
bindings above emulate it in `readline'; these are complementary to the
preconfigured bindings for `<CTRL-R>' and `<CTRL-S>', which are analogues
for the `vi' mode `<ESC>/SearchString', followed by `n' or 'N' mechanism,
and which continue to work as configured.

Readline is an exceptionally flexible beast, and the choice between its
`vi' and `emacs' emulation modes is always going to come down to 
individual
preference.  The beauty is that we have that choice; experiment and choose
whatever suits *you* best.

Regards,
Keith.

Quoting Keith MARSHALL <kei...@to...>:

>
>  bind '"\e[A":history-search-backward'
>  bind '"\e[B":history-search-forward'
>
> to emulate the history search behaviour of the `4DOS' shell I used
> at one time with MS-DOS: type the first few characters of a command,
> then use <Cursor-Up> and <Cursor-Down> to find and replay matching
> commands in the history.
>

I like to set my command mode vi style ``set -o vi'' and then use 
``<esc>/stringToSearch'' to enter search mode.  I can then use ``n'' to 
search forward and ``N'' to search reverse.  You can even use the <esc> 
key to enter a substitution command.

Earnie Boyd

http://shop.siebunlimited.com

Richard Haney wrote:
> I have tried using Msys 1.0.8 in the past and have just now tried
> using Msys 1.0.10, but what originally persuaded me to continue with
> Cygwin bash is the fact that there is no obvious way to set the
> default window parameters for the Msys bash shell.

Others have already suggested the elimination of rxvt, either using
MSYS-1.0.11's `--norxvt' option, or by deleting/renaming rxvt.exe in
the MSYS /bin directory; this lets you run the MSYS bash shell in a
native Woe32 console, which is what you get by default with Cygwin.

> The Cygwin bash window's system menu (obtained by clicking on the
> icon in the upper lest corner) has a "Defaults" menu item that allows
> setting the default window size...

That's nothing peculiar to Cygwin, nor even provided by Cygwin; it is
simply the standard Woe32 native console window behaviour.

Julien Lecomte replied:
>> Also, I would like to know how I can insert text from the clipboard
>> and how I can at least instantly move the cursor to the beginning or
>> the end of the current command line.  And if more refined cursor
>> keyboard control is available, I'd like to know about that as well.
>>

For `copy-and-paste', I use the mouse.  In the `Properties' dialogue
for that native console window, under the `Options' tab, select both
`Quick Edit Mode' and `Insert Mode'.  Now, hold the left button and
drag the mouse to highlight text; while it remains highlighted, a
single click of the right button copies it to the clipboard, and
subsequent right button clicks paste it, as many times as you like,
at the cursor position.

>> (...)
>>
>> More refined command-line controls such as the Windows ("DOS")
>> command-line-shell's "Ctrl+'right_arrow'" or "Ctrl+'left_arrow'"
>> to skip groups of characters would also be nice (even in the
>> Cygwin shell as well).
>>
>> Is that possible?
>
> Yes, by using inputrc files.

That's certainly the generic way to do it, providing settings which
propagate to all installed `readline' aware apps--which in the MSYS
world, are few and far between.

For settings which you would prefer to restrict to the shell, you
can also use the built-in `bind' command; e.g. I have the following
in my ~/.bashrc, (which I source from my ~/.profile):

  bind 'set completion-ignore-case on'
  bind '"\e[A":history-search-backward'
  bind '"\e[B":history-search-forward'
  bind '"\e[7~":beginning-of-line'
  bind '"\e[8~":end-of-line'
  bind '"\e[3~":delete-char'

> I've pasted the contents of my /etc/inputrc and ~/.inputrc files
> [snipped]. They aren't perfect, "delete" key doesn't delete,

You can use `cat -v', to check what the appropriate keyboard scan
code is.  In my case, when I hit the `delete' key, followed by the
<RETURN> key, I see:

  $ cat -v

  ^[[3~

(Check the codes for other keys, by hitting each in turn, with each
 followed by <RETURN>; hit <CTRL-D> when done).

Now, the `^[' represents the ASCII <ESC> code, while the `[3~' simply
represents the three byte sequence of their respective ASCII codes.
Thus, I deduce the `.inputrc' or `bind' configuration string:

  "\e[3~":delete-char

which makes the `delete' key work for me.

> but the "home" and "end" keys work.

As they do for me, with the configuration:

  bind '"\e[7~":beginning-of-line'
  bind '"\e[8~":end-of-line'

> They are a good starting point to have similar behavior between
> console and rxvt.

My other configuration settings are:

  bind 'set completion-ignore-case on'

to make <TAB> completion work in the most logical fashion, on the
Woe32 case-insensitive file system, and:

  bind '"\e[A":history-search-backward'
  bind '"\e[B":history-search-forward'

to emulate the history search behaviour of the `4DOS' shell I used
at one time with MS-DOS: type the first few characters of a command,
then use <Cursor-Up> and <Cursor-Down> to find and replay matching
commands in the history.

You will also find that the standard `readline' <CTRL> and <ESC>
sequences work, without any additional configuration, e.g.:

  <CTRL-K>   deletes from cursor to end of line
  <CTRL-U>   deletes from cursor to beginning of line

  <ESC>-<F>  move cursor to end of word
  <ESC>-<B>  move cursor to beginning of word
  <ESC>-<D>  delete from cursor to end of word

among others; try `bind -p' to see what's currently mapped, and
Google for `readline' documentation, for an explanation of the
available functions.

HTH,
Keith.

Quoting "Schwarz, Konrad" <kon...@si...>:

> MinGW: `/d/dir1/../../c/dir2/file' fails.  For the cross-generation

Since it works for me with ls, I need a reduced example that fails.  I 
can imagine that the path is ending up somethng like 
d:/dir1/../../c/dir/file to a native gcc which isn't going to work.  I 
can't imagine that your semantics will work well on Windows with native 
programs.  I also suggest that you check out autoconf to configure your 
build system; it does a good job of creating normalized Makefiles on a 
various of differing systems.

Earnie Boyd

http://shop.siebunlimited.com

> -----Original Message-----
> From: min...@li...=20
> [mailto:min...@li...] On Behalf=20
> Of mwoehlke

> > The proposed mapping for directory `C:\' is `//./C$/' (or perhaps=20
> > `//./C/').

> So... why exactly do you need this? The only thing I might=20
> actually support here (keeping in mind Eric's comments and=20
> CGF's clear agreement with them) would be treating '//./' as=20
> a special case of '//127.0.0.1/', at which point '//./C$/' is=20
> the UNC mapping of the default 'C$' share on the local=20
> machine. But I still fail to see why that is useful.

My program constructs file names.  Specificially, for code generation,
it outputs `# include' statements, which reference pre-installed header
files.  To maximize the portability of the code, I would like to use
relative paths wherever possible, so that the generated code can more
easily be moved to a different location, assuming that the referenced
files are moved too.  A related and perhaps more pertinent example is to
be able to compile the generated code on a second computer that shares a
network drive with the original computer and/or under a different
operating system, such as Win32.

For that, I need to know when it is possible to construct a relative
path, which is when the two files are on the same drive.  As a matter of
fact, for Cygwin and for Interix, `/cygdrive/D/dir1/../../C/dir2/file'
and `/dev/fs/D/dir1/../../C/dir2/file' works, but it does not work for
MinGW: `/d/dir1/../../c/dir2/file' fails.  For the cross-generation
example, it is debatable if `/cygdrive/D/../C' is helpful since it
imposes strong constraints on the name of the drive mount point on the
remote machine and fails for Win32.

Thus my suggestion of using a name prefixed with two slashes to indicate
a path that does not fully comply with the ordinary name-resolution
rules, as sanctioned by POSIX.  The code that does the file name
normalization can remain largely platform independent and refer to files
outside of the current file system hierarchy by extra linguistic means
such as `# include <>' and `-I' flags.

On 25/08/2006 01:41, Richard Haney wrote:
  > Also, I would like to know how I can insert text from the clipboard and
> how I can at least instantly move the cursor to the beginning or the
> end of the current command line.  And if more refined cursor keyboard
> control is available, I'd like to know about that as well.
> 
> (...)
> 
> More refined command-line controls such as the Windows ("DOS")
> command-line-shell's "Ctrl+'right_arrow'" or "Ctrl+'left_arrow'" to
> skip groups of characters would also be nice (even in the Cygwin shell
> as well).
> 
> Is that possible?

Yes, by using inputrc files. I've pasted the contents of my /etc/inputrc 
and ~/.inputrc files below. They aren't perfect, "delete" key doesn't 
delete, but the "home" and "end" keys work. They are a good starting 
point to have similar behavior between console and rxvt.
Julien

<begin file=~/.inputrc>
# Include system wide settings which are ignored
# by default if one has their own .inputrc
$include /etc/inputrc

set completion-query-items 20

set show-all-if-ambiguous on

$if mode=emacs
	$if term=msys # RXVT
		# "\e[12~": "Function Key 2"
		# "\e[13~": "Function Key 3"
		# "\e[14~": "Function Key 4"
		# "\e[17~": "Function Key 6"
		# "\e[18~": "Function Key 7"
		# "\e[19~": "Function Key 8"
		# "\e[20~": "Function Key 9"
		# "\e[21~": "Function Key 10"
	$endif
	$if term=cygwin # Console
		# "\e[17~": "Function Key 6"
		# "\e[18~": "Function Key 7"
		# "\e[19~": "Function Key 8"
		# "\e[20~": "Function Key 9"
		# "\e[21~": "Function Key 10"
		# "\e[23~": "Function Key 11"
	$endif
$endif
<end file=~/.inputrc>


<begin file=/etc/inputrc>
# Ask before displaying >50 items
# Since $WINDIR $PATH var can be in $PATH, this could list
# all window executables in C:\WINDOWS
set completion-query-items 50

# Ignore case for the command-line-completion functionality
# on:  default on a Windows style console
# off: default on a *nix style console
set completion-ignore-case on

# none, visible or audible
set bell-style visible

# disable/enable 8bit input
set meta-flag on
set input-meta on
set output-meta off
set convert-meta on

# visible-stats
# Append a mark according to the file type in a listing
set visible-stats off
set mark-directories on

# Show all instead of beeping first
set show-all-if-ambiguous off

# MSYSTEM is emacs based
$if mode=emacs
	# Common to Console & RXVT
	"\C-?": backward-kill-line     		# Ctrl-BackSpace
	"\e[2~": paste-from-clipboard  		# "Ins. Key"
	"\e[5~": beginning-of-history  		# Page up
	"\e[6~": end-of-history        		# Page down
	
	$if term=msys # RXVT
		"\e[7~": beginning-of-line      # Home Key
		"\e[8~": end-of-line            # End Key
		"\e[11~": display-shell-version # F1
		"\e[15~": re-read-init-file     # F5
	$endif
	$if term=cygwin # Console
		"\e[1~": beginning-of-line      # Home Key
		"\e[4~": end-of-line            # End Key
	$endif
$endif
<end file=/etc/inputrc>

Schwarz, Konrad wrote:
> Hi,
> 
> I know that it is kind of late :-), but I would like to suggest an
> alternative/additional mapping of drive letters to the MinGW and Cygwin
> file-system name space.
> 
> The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
> `//./C/').
> 
> The reasons for this mapping are:
> [snip]

So... why exactly do you need this? The only thing I might actually 
support here (keeping in mind Eric's comments and CGF's clear agreement 
with them) would be treating '//./' as a special case of '//127.0.0.1/', 
at which point '//./C$/' is the UNC mapping of the default 'C$' share on 
the local machine. But I still fail to see why that is useful.

Or you could change your mount prefix to '/dev/fs', and have 
'/dev/fs/c', etc, which seems more "natural" and is also what Interix 
uses (so you have compatibility in case you ever use that POS).

-- 
Matthew
'$ time make world' -> real 5d:14h:37m:5.291s  user 0m:0.000s  sys 
4d:2h:14m:43.712s

Quoting "Schwarz, Konrad" <kon...@si...>:

>> -----Original Message-----
>> From: min...@li...
>> [mailto:min...@li...] On Behalf
>> Of Richard Haney
>> Sent: Friday, August 25, 2006 1:42 AM
>> To: min...@li...
>> Subject: [Mingw-msys] Msys customization: default window
>> parameters: windowsize, font, colors; and more
>>
>
> Quoting msys/1.0/msys.bat:
>
> rem If you don't want to use rxvt then rename the file rxvt.exe to
> something
> rem else.  Then sh.exe will be used instead.
>
> MSYS then uses a Windows console as the user interface, just as with
> Cygwin.
>

And with the 1.0.11 version of MSYS you will be able to specify 
--norxvt in the command execution parameter of the desktop icon.  You 
can get the bleeding edge version of msys.bat file from CVS and just 
replace the c:/msys/1.0/msys.bat with it for this to work.

Earnie Boyd

http://shop.siebunlimited.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Schwarz, Konrad on 8/25/2006 1:57 AM:
> Hi,
> 
> I know that it is kind of late :-), but I would like to suggest an
> alternative/additional mapping of drive letters to the MinGW and Cygwin
> file-system name space.
> 
> The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
> `//./C/').

Sorry, but I don't like this for cygwin (I don't care how msys decides on
the issue, though).  Cygwin already has /cygdrive/c mapping to c:\ in a
default installation, and that is configurable through mount to be
whatever a user wants (even /c).  Cygwin also already has support for
//server/share, and mixing in //./c would make that code path much more
difficult to maintain.

You probably won't get very far with this proposal in cygwin without
actual patches and a LOT more convincing.

- --
Life is short - so eat dessert first!

Eric Blake             eb...@by...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE7ulu84KuGfSFAYARAlLKAJ93RP1wysFqN0icYugjY2tOtPm6WwCgndPN
+w0eOK25ljfNfJAyL2+STAQ=
=m7fj
-----END PGP SIGNATURE-----

> -----Original Message-----
> From: min...@li...=20
> [mailto:min...@li...] On Behalf=20
> Of Richard Haney
> Sent: Friday, August 25, 2006 1:42 AM
> To: min...@li...
> Subject: [Mingw-msys] Msys customization: default window=20
> parameters: windowsize, font, colors; and more
>=20

Quoting msys/1.0/msys.bat:

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

MSYS then uses a Windows console as the user interface, just as with
Cygwin.

This is also explained in the documentation.

Regards,

Konrad Schwarz

Hi,

I know that it is kind of late :-), but I would like to suggest an
alternative/additional mapping of drive letters to the MinGW and Cygwin
file-system name space.

The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
`//./C/').

The reasons for this mapping are:

* POSIX allows paths that begin with exactly two slashes to be
"special": they do not have to obey normal file system path semantics
(see XBD 4.11).  E.g., POSIX requires `/x/my_file' to be referenced from
`/y/my_dir' as `../../x/my_file', but this is does not work in MinGW.
By beginning the path with two slashes, POSIX compliant code knows that
this transformation should not be attempted in general.

* The notation `//./something' is in line with standard Windows API
names for system devices.  See the documentation for the CreateFile()
function in the Windows SDK for those names.  In particular,
CreateFile() uses `\\.\C:\' to represent the root directory of that
volume and `\\.\C:' to represent the volume (raw device).  Since colon
is used in POSIX to separate paths in the PATH environment variable,
`//./C:/' is not a good mapping.

* The notation is in line with the Windows Universal Naming Convention
(UNC) insofar as it consists of two components and begins with two
directory separation characters.  Therefore, Windows-special cased code
that does not need to differentiate between "local" and "network" drives
(which should be the majority of cases) can stay unaware of the
differentiation.

* `//host/C$' is the standard share name for drives under Windows that
are mounted from a different machine.

* Shells do not attempt to expand the substring `$/' as a variable.
Other languages, e.g., make(1), will attempt to expand such a reference,
so `//./C/' might be better than `//./C$/'.  `//./C/' also has the
benefit of using only letters from the POSIX portable filename character
set.  However, `//./C/' might be used by Microsoft for some different
purpose in the future.

Note that for Windows, `/' is a reserved letter in the file system.  It
is, as far as I know, never a problem to replace `\' with `/' in paths
when dealing directly with the operating system (cmd.exe is something
else), and the Windows SDK functions will even do this for you, except
for paths prefixed with '\\?\'.

Regards,

Konrad Schwarz

I have been using cygwin bash (in C:\cygwin\bin ) for (autoconf's)
configure and make building of ported packages, along with MinGW gcc
(and associated utilities such as as, ld, ... -- all in C:\Dev-Cpp\bin
), and it has been suggested that this combination is "tricky".  So
I've decided to take another look at Msys.

I have tried using Msys 1.0.8 in the past and have just now tried using
Msys 1.0.10, but what originally persuaded me to continue with Cygwin
bash is the fact that there is no obvious way to set the default window
parameters for the Msys bash shell.  The Cygwin bash window's system
menu (obtained by clicking on the icon in the upper lest corner) has a
"Defaults" menu item that allows setting the default window size,
default position, default font, and default color scheme (and I think
even the "Properties" menu item also has a closing dialog that asks if
you want to make any parameter changes to be the default).

But when I open the Msys shell and click on the Msys system icon,
"Defaults" is not among the menu items displayed, nor is there any
"Properties" menu item.  I can of course click and drag the window
boundaries, but this does not result in any default for the next time I
open the shell window.

I have tried looking at the various files involved in opening the Msys
shell to see if there is some way I can set the default parameters
desired, but there seems to be several layers of indirection in the
invoking of executables to get the window displayed.  As best as I can
figure it, this seems to be something like msys.bat -> [sh.exe ->] cmd
"/"c -> rxtv.exe (or alternatively msys.bat -> [sh.exe ->] cmd "/"c ->
sh.exe if rxtv.exe does not exist).

I've also tried executing various of the intermediate executables with
"--help" (with the idea of also trying "/?" or "//?" instead of
"--help"), but although I can get some "help" information for sh.exe, I
generally run into a maze of problems, at least for the other
executables.

So my question is this:  How can I set the default values for these
parameters: window size, window position, font, and color scheme?

Also, I would like to know how I can insert text from the clipboard and
how I can at least instantly move the cursor to the beginning or the
end of the current command line.  And if more refined cursor keyboard
control is available, I'd like to know about that as well.

Presently with the Cygwin shell I can insert text from the Windows
clipboard with the "Insert" key or do so via opening the system menu
and pasting with the shortcut keys "Alt+Space e p", and I can move the
cursor to the beginning or end of the command line by using the "Home"
or "End" keys.

So I would like to at least get all those capabilities with Msys.

More refined command-line controls such as the Windows ("DOS")
command-line-shell's "Ctrl+'right_arrow'" or "Ctrl+'left_arrow'" to
skip groups of characters would also be nice (even in the Cygwin shell
as well).

Is that possible?

Richard Haney


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Earnie Boyd wrote:
> Quoting Lennart Borgman <len...@st...>:
>
>   
>> Is there any plan to update to Perl 5.8 soon?
>>
>>     
>
> I plan to take a look at building a more current version after I create 
> a 1.0.11 release candidate.  It will first appear as a snapshot file in 
> the Snapshot package under the MSYS release as package and release are 
> defined by the SF FRS.
>
> Earnie Boyd
>   
Thanks.

Quoting Lennart Borgman <len...@st...>:

> Is there any plan to update to Perl 5.8 soon?
>

I plan to take a look at building a more current version after I create 
a 1.0.11 release candidate.  It will first appear as a snapshot file in 
the Snapshot package under the MSYS release as package and release are 
defined by the SF FRS.

Earnie Boyd

http://shop.siebunlimited.com

Is there any plan to update to Perl 5.8 soon?



-------- Original Message --------
Subject: 	Re: [gimpwin-users] Re: Gimp and Gimp-Perl
Date: 	Tue, 22 Aug 2006 21:35:37 +0200
From: 	Michael Schumacher <sch...@gm...>
Reply-To: 	gim...@ya...
To: 	gim...@ya...
References: 	<ecc...@eG...>
<Pin...@sa...>
<1estco2j8le3s.1azuvce1aqnea$.dl...@40...>
<44E...@st...>



Lennart Borgman wrote:
> Jernej Simončič wrote:

>> Last time I tried compiling gimp-perl, it used a weird mix of perl
>> Makefiles and sh scripts, making it impossible to configure (because native
>> win32 perl uses cmd.exe as shell, and mixing cygwin and native binaries is
>> a bad idea).
>>   
> Did you try MSYS?

Yes. Problem #1 is that the Perl shipped with MSYS (or one of the
support packages, at least) is version 5.6. Gimp-Perl needs 5.8. I'm not
aware of any updates.

Maybe you should really give it a try yourself, there shouldn't be any C
knowledge needed in order to get a basic build (or build attempt) going.


HTH,
Michael

Members,

I have uploaded gawk-3.1.5 snapshot for MSYS-1.0.11 and it is now 
available for your use.


Earnie Boyd

http://shop.siebunlimited.com

Members,

I have uploaded the snapshot for findutils-4.3.0 for MSYS-1.0.11 and it 
is now available for your use.


Earnie Boyd

http://shop.siebunlimited.com

Members,

I've uploaded the diffutils-2.8.7 snapshot for MSYS-1.0.11 for your use.

Earnie Boyd

http://shop.siebunlimited.com

MSYS Users,

I've uploaded the bzip2 snapshot for MSYS-1.0.11 and have it ready for 
your use.


Earnie Boyd

http://shop.siebunlimited.com

Quoting Earnie Boyd <ea...@us...>:

> Quoting Adam Doppelt <am...@gu...>:
>
>> Done - let me know if there's anything else you need.
>>

I've just discovered that ``rm -rf dirfoo'' from coreutils 5.97 doesn't 
remove the specified directory.  It gives "No such file or directory" 
error.  The contents of the directory itself are removed.  I've 
uploaded coreutils to CVS; can you please check into src/remove.c and 
try to discover why?

The way I upload the changes I start with the pristine version in 
-r1.1, commit the CYGWIN specific changes and then commit the MSYS 
changes.  So you can see the differences in pristine by doing ``cvs 
diff -r1.1'' once you've checked out the HEAD.

TIA,
Earnie Boyd

http://shop.siebunlimited.com

Quoting Adam Doppelt <am...@gu...>:

> Done - let me know if there's anything else you need.
>

Yesterday when building coreutils I found that freopen is broken at 
least for stdin.  I will eventually look at updating the newlib 
libc/stdio/freopen.c to the most current newlib version to see if doing 
just that much resolves the issue.  If you want to get your feet wet 
with the MSYS runtime code it may be a good place to start.

Earnie Boyd

http://shop.siebunlimited.com