Mail Archives: djgpp/2000/12/19/06:47:42
On Mon, 18 Dec 2000 dcasale AT my-deja DOT com wrote:
> I _think_ I sent this before, but Dejanews says I didn't. *shrugs*
You did post it, at least 3 times. There are propagation delays that
you should account for before posting again.
> After some code changes and after installing some additional packages
> for DJGPP, I tried compiling the latest version of my compression
> program in RHIDE only to receive a "Command line too long" error.
>
> What might cause this?
I'm guessing that some package you installed changed PATH, so now some
of the programs invoked by RHIDE doesn't support the special way of
passing long command lines between DJGPP programs. (For details about
this special way, see section 16.4 of the FAQ.) Section 16.6 of the
FAQ mentions, near its end, possible problems like that.
> What can I do about it?
Find the offending program. One way to do that is to add -v to the
compilation switches, and see what program is invoked when this
message is printed. I'm guessing it's cpp, the preprocessor, but
that's a wild guess, as you didn't say what packages did you install.
When you find the offending program, adjust the PATH so that it is no
longer found before the correct program. Or perhaps the package in
question overwrote one of GCC's programs with an incompatible version,
in which case you will need to restore the original binary.
> I couldn't find any
> information in the RHIDE docs, although I haven't waded through the
> docs for _every_ program that RHIDE spawns to see if the error message
> is coming from there.
Did you include the FAQ in your search? Just pressing `i', then
typing "Command line TAB TAB" pops up a list of entries, one of which
says "Command lines, longer than 126 characters".
The error message comes from the DJGPP library's function `system',
that's why it is not documented in any specific program's docs. You
could use the `strings' program to find all the strings built into
rhide.exe (or any other program).
- Raw text -