From: Robert Hoehne Newsgroups: comp.os.msdos.djgpp Subject: Re: Rhide:long command lines problem Date: Thu, 27 Mar 1997 12:14:42 +0100 Organization: TU Chemnitz-Zwickau Lines: 38 Message-ID: <333A56A2.6FCE@Mathematik.tu-chemnitz.de> References: <5g92lk$p0a$1 AT ict DOT cec DOT uchile DOT cl> <33293102 DOT 5829 AT Mathematik DOT tu-chemnitz DOT de> <01bc3a1e$957601a0$ee0b1d26 AT ghost DOT artnet DOT net> NNTP-Posting-Host: process.hrz.tu-chemnitz.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Sean L. Palmer wrote: > > I have about 300 files that need to be compiled. I put them all in the > project and do a build, and voila I get "Command line too long" in the info > window back. This message is produced by the DJGPP system function and can have several reasons: 1) The length of the commandline together with the size of your environment is bigger than your transfer buffer. This buffer is normaly 16K (until you cnaged it manually). But this reason I cant imagine except the names of the object files are realy very long names. You can check the length of the commandline when you run RHIDE with the '-dc' switch and redirecting the output to a file. redir -e err rhide -dc YOUR_PROJECT Now run the link stage (Compile/Link) and exit RHIDE. Look at the file 'err' and see, how long the commandline is. If it is realy longer than 16k, then you should stubedit rhide.exe to give it a bigger transfer buffer. 2) You are using an other shell than command.com and as far as I know, there are some limitations. Have you set the SHELL environment variable? Robert -- ***************************************************************** * Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau * * Post: Am Berg 3, D-09573 Dittmannsdorf * * e-Mail: Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE * * WWW: http://www.tu-chemnitz.de/~rho * *****************************************************************