RE: Command line length on Win2000

[Geoffrey Tam]

There is a problem with the build.
- I had to add a "cl.exe" line for hash.c
- At the end of the build, after the "Linking WinRel/gnumake.exe" line is
displayed, I get a "Bad command or file name" error
- After this, it looks like the link.exe program is run. I get the following
message: "LINK : warning LNK4089: all references to "ADVAPI32.dll" discarded
by /OPT:REF"
- After this, the batch file informs me that "WinRel build failed"

> -----Original Message-----
> From: Shah Bijal [mailto:address@hidden
> Sent: Monday, May 12, 2003 1:41 PM
> To: Geoffrey Tam; address@hidden
> Subject: RE: Command line length on Win2000
> 
> 
> 
> You'll always have limitations running Win9x and NT based 
> systems - its advisable to upgrade if you can. Win 98 will 
> still use COMMAND.COM with all its problems. It sounds as 
> though you might be better off using one of the many UNIX 
> commands under windows systems such as cygwin or MINGW - 
> these will allow you to use the "sh" shell or similiar which 
> don't have as bad a set of command line limitations as DOS/WinNT.
> 
> That said, you can download the source code from the GNU 
> website and if you have visual C++ 6.0, it doesn't take any 
> time to compile at all - there is a batch file provided. I 
> would encourage this as it does allow you the get to grips 
> with make. I don't think the Win2000 exe will work under Win 
> 98 but I'm not sure.
> 
> Alternatively, there are implementations precompiled 
> downloadable from cygwin or MINGW - "google" it and you'll 
> find what you need, though you might find they are linked to 
> a larger environment.
> 
> -----Original Message-----
> From: Geoffrey Tam [mailto:address@hidden
> Sent: 12 May 2003 18:06
> To: Shah Bijal; address@hidden
> Subject: RE: Command line length on Win2000
> 
> 
> Here are the answers to your questions:
> - make was downloaded many, many years ago, so I *think* it 
> was a DOS build.
> - the COMSPEC environment variable points to CMD.EXE
> 
> Do you know where I can get the latest version of gmake in 
> executable form?
> Unfortunately, I don't have enough time in the day to build 
> it myself. I
> will need it to work in both Win98 and Win2000 as some 
> machines run Win98
> and others run Win2000. I'd prefer 1 executable, but if I need 2
> executables, so be it.
> 
> Your help is much appreciated.
> 
> > -----Original Message-----
> > From: Shah Bijal [mailto:address@hidden
> > Sent: Monday, May 12, 2003 12:39 PM
> > To: Geoffrey Tam; address@hidden
> > Subject: RE: Command line length on Win2000
> > 
> > 
> > 
> > This doesn't sound right.... I'm running win2k and can get 
> > command lines of well over 2000 characters.
> > 
> > Did you build your make or download it? Is it actually a DOS 
> > build of make or a Windows 2000 build?
> > 
> > Also, check COMSPEC and SHELL environment/make variables to 
> > see if they are pointing to CMD.EXE.
> > I would upgrade to the latest gmake too - 3.76.1 quite old in 
> > the scheme of things!
> > 
> > 
> > -----Original Message-----
> > From: Geoffrey Tam [mailto:address@hidden
> > Sent: 12 May 2003 17:14
> > To: 'address@hidden'
> > Subject: Command line length on Win2000
> > 
> > 
> > I am running into command line length problems on Win2000 
> when running
> > gmake. On Win98, I used command.com as my shell, and could 
> > use roughly 120
> > characters in my make commands. On Win2000, this has been 
> > reduced to about
> > 96 characters. Are there any shells out there that will 
> > greatly expand from
> > 120 the number of characters I can use in my make commands? I 
> > am currently
> > running version 3.76.1 of the make utility.
> > 
> > I have also noticed that hand typing in the make commands 
> > that don't work
> > from make works on Win2000.
> > 
> > 
> > _______________________________________________
> > Make-w32 mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/make-w32
> > 
> > --
> > This message and any attachments (the "message") is intended 
> > solely for the
> > addressees and is confidential. If you receive this message 
> > in error, please
> > delete it and immediately notify the sender.
> > Any use not in accordance with its purpose, any dissemination 
> > or disclosure,
> > either whole or partial, is prohibited except formal approval.
> > The E-Mail transmission can not guarantee the integrity of 
> > this message.
> > CANAL+TECHNOLOGIES will not therefore be liable for the 
> > message if modified.
> > 
> > 
> 
> --
> This message and any attachments (the "message") is intended 
> solely for the
> addressees and is confidential. If you receive this message 
> in error, please
> delete it and immediately notify the sender.
> Any use not in accordance with its purpose, any dissemination 
> or disclosure,
> either whole or partial, is prohibited except formal approval.
> The E-Mail transmission can not guarantee the integrity of 
> this message.
> CANAL+TECHNOLOGIES will not therefore be liable for the 
> message if modified.
> 
>