public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Buglist
@ 1997-04-03 17:13 Tim Iverson
  0 siblings, 0 replies; 6+ messages in thread
From: Tim Iverson @ 1997-04-03 17:13 UTC (permalink / raw)
  To: gnu-win32

Well, things work now, but if you've also been having problems self-hosting
a build under Windows-95, note that it's rather important to extract
the all tarball with the Cygwin32 tar, and not some other tar.

I have three different tars, and all of them skip over hard links when
extracting 'cuz W95 doesn't support 'em.  Normally, one might catch this
right away when running configure -- missing commands and such.  However,
my system is sufficiently Unix-like that this didn't happen.  Instead I got
all manner of strange behavior.

It would be *very* nice if Cygnus could maintain a public buglist for this
project (buglist and FAQ should be a part of the all tarball).  I don't
know about the rest of y'all, but my first thought before I even decided to
download anything, was "Wow, this sounds great, but what doesn't work?"  ;-)

Here are the few caveats I've collected so far (btw, not all of these
are bugs, but all are odd enough to note):

 . Proper extraction of tarballs requires Cygwin32's tar.exe -- other
   tar's may not extract the hard links.

 . Control-C will always crash bash.

 . Bash does not interoperate well with non-cygnus tools, especially when
   piping or arg-sub'ing; eg. try ">foo; test 0 -eq `grep -c . foo`" with
   any working, but non-cygnus, grep.

 . Gas produced PE objects cannot be linked with a commercial linker;
   there is a patch for this, though.

 . Don't put your source more than two levels deep or configure
   will not function properly.  [Not completely verified, could
   also have been a tar extraction error].

 . Bash can't run many .com programs and won't automatically feed
   .bat files to command.com.

 . Bash doesn't understand drive letters, multi-dot relative paths
   (eg. "cd ..."), or UNC pathnames (eg. //host/resource).

 . Bash's glob'ing is case dependent, W95's filesystem isn't (quite).

 . You will need to copy gcc.exe to cc.exe to build gcc.exe.
   Passing CC=gcc to configure may also work.

 . "make install" is broken.  You will need to hunt down and manually
   install the binaries if you rebuild.

 . It has man and info pages, but neither man nor info commands.


- Tim Iverson
  iverson@cisco.com
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Buglist
@ 1997-04-07 18:53 dahms
  0 siblings, 0 replies; 6+ messages in thread
From: dahms @ 1997-04-07 18:53 UTC (permalink / raw)
  To: jqb; +Cc: gnu-win32, dahms

Hi Jim, you wrote:

: Under win32, paths consisting of only dots, with the exception of .
: and .., are illegal.  This is along with a number of other
: illegal characters and combinations, including such winners as
: mkdir -p "abcde/xyz/con/ffo/bar" hanging as it tries to do I/O to the
: "con" device; lots of fun when you untar a 500Meg tar tape from
: some other system that was designed on less ad hoc principles.

Yeah, a collegue of mine tried to get com961231.tgz via FTP, after a while
I figured out that specifying a harmless local filename works (I guess there's
no box with >100000 serial ports on the market 8-).

Did you finally got cygwin tar to work? Another collegue gave my an NT tar
binary but which handles only a blocksize of 512, not the standard 10kB,
while the manual of our fine new DDS3 says it works best with 32kB...
And is there any decent "mt" for NT, preferably with sources to spy at?


Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: Buglist
@ 1997-04-07 12:09 Stephan Mueller
  0 siblings, 0 replies; 6+ messages in thread
From: Stephan Mueller @ 1997-04-07 12:09 UTC (permalink / raw)
  To: 'Jim Balter', dahms; +Cc: iverson, gnu-win32

On NT, what Jim says is correct.  The 'multi-dot' paths being discussed
are probably a special bonus feature (ahem) of the DOS and Windows 95
command.com shells.

In a Windows 95 command.com box, a reference to a directory name
consisting of n dots means the n-1st parent directory.  Thus
	cd ...
is equivalent to
	cd ..\..

It is interesting that this notation works with non-command.com exes as
well, so it may be that the Win95 implementation of Win32 generally
supports this.

stephan();

> -----Original Message-----
> From:	Jim Balter [SMTP:jqb@netcom.com]
> Sent:	Friday, April 04, 1997 7:10 PM
> To:	dahms@ifk20.mach.uni-karlsruhe.de
> Cc:	iverson@cisco.com; gnu-win32@cygnus.com
> Subject:	Re: Buglist
> 
> dahms@ifk20.mach.uni-karlsruhe.de wrote:
> > 
> > Hi Tim, you wrote:
> > 
> > :  . Bash doesn't understand drive letters, multi-dot relative paths
> > :    (eg. "cd ..."), or UNC pathnames (eg. //host/resource).
> > 
> > What is a multi-dot path, please? I never saw ... only know . and ..
> > Under Unix ... has no reserved meaning, and AFAIK neither under NT.
> 
> Under win32, paths consisting of only dots, with the exception of .
> and .., are illegal.  This is along with a number of other
> illegal characters and combinations, including such winners as
> mkdir -p "abcde/xyz/con/ffo/bar" hanging as it tries to do I/O to the
> "con" device; lots of fun when you untar a 500Meg tar tape from
> some other system that was designed on less ad hoc principles.
> 
> --
> <J Q B>
> -
> For help on using this list, send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Buglist
  1997-04-04 14:27 Buglist dahms
@ 1997-04-04 19:15 ` Jim Balter
  0 siblings, 0 replies; 6+ messages in thread
From: Jim Balter @ 1997-04-04 19:15 UTC (permalink / raw)
  To: dahms; +Cc: iverson, gnu-win32

dahms@ifk20.mach.uni-karlsruhe.de wrote:
> 
> Hi Tim, you wrote:
> 
> :  . Bash doesn't understand drive letters, multi-dot relative paths
> :    (eg. "cd ..."), or UNC pathnames (eg. //host/resource).
> 
> What is a multi-dot path, please? I never saw ... only know . and ..
> Under Unix ... has no reserved meaning, and AFAIK neither under NT.

Under win32, paths consisting of only dots, with the exception of .
and .., are illegal.  This is along with a number of other
illegal characters and combinations, including such winners as
mkdir -p "abcde/xyz/con/ffo/bar" hanging as it tries to do I/O to the
"con" device; lots of fun when you untar a 500Meg tar tape from
some other system that was designed on less ad hoc principles.

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Buglist
@ 1997-04-04 16:05 Scott Mintz
  0 siblings, 0 replies; 6+ messages in thread
From: Scott Mintz @ 1997-04-04 16:05 UTC (permalink / raw)
  To: gnu-win32, Tim Iverson

     Tim,
     
     There is a bug list being kept at:
     < http://www.cs.mu.oz.au/~fjh/gnu-win32/bugs-list.html >.
     
     +------------------------------+------------------------------------+
     | Scott A. Mintz               | voice: (216) 646-4805              |
     | Allen-Bradley Company        | fax:   (216) 646-4961              |
     | 1 Allen-Bradley Drive        | email: scott.mintz@po.cle.ab.com   |
     | Mayfield Hts., OH 44124-6118 | CIS:   71461,632                   |
     +------------------------------+------------------------------------+

-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: Buglist
@ 1997-04-04 14:27 dahms
  1997-04-04 19:15 ` Buglist Jim Balter
  0 siblings, 1 reply; 6+ messages in thread
From: dahms @ 1997-04-04 14:27 UTC (permalink / raw)
  To: iverson; +Cc: gnu-win32, dahms

Hi Tim, you wrote:

:  . Bash doesn't understand drive letters, multi-dot relative paths
:    (eg. "cd ..."), or UNC pathnames (eg. //host/resource).

What is a multi-dot path, please? I never saw ... only know . and ..
Under Unix ... has no reserved meaning, and AFAIK neither under NT.


Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~1997-04-07 18:53 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-04-03 17:13 Buglist Tim Iverson
1997-04-04 14:27 Buglist dahms
1997-04-04 19:15 ` Buglist Jim Balter
1997-04-04 16:05 Buglist Scott Mintz
1997-04-07 12:09 Buglist Stephan Mueller
1997-04-07 18:53 Buglist dahms

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).