Re: [Fwd: How to handle "The following character string is too long... NMAKE : fatal error U1077: 'echo' : return code '0x1'" problem while compiling XEmacs?]
Emre Sevinç <[email protected]> Fri, 24 Feb 2006 15:32:13 +0200
| Newsgroups | gmane.emacs.xemacs.windows |
|---|---|
| Message-ID | <[email protected]> |
Stephen J. Turnbull wrote: >>>>>>"Emre" == Emre Sevin <[email protected]> writes: >>>>>> >>>>>> > > Emre> I'm trying to compile XEmacs on my MS Windows 2000 Server > Emre> system (using .NET framework). > >AFAIK, nobody in the dev team is using that configuration. Is there a >reason why you can't or don't want to use Visual C or Cygwin's GCC, >which are better supported? > Because E:\xemacs-21.5.24\nt\README says that: 1. You will need Visual C++ V6.0, Visual Studio .NET or later to compile everything. and I had Visual Studio on my machine, tools such as nmake, etc. That's why I followed that way. > > Emre> The following character string is too long: ... > >Unfortunately, the string in question is generated by an intermediate >program. We can probably deal with it, but it may take a little time >since we don't want to break other systems. > >For now, you could try editing the file dump-id.c. Find the string, >and in place of the space after "redisplay.obj" put ' " "' so that >that part of the file looks like > I have looked at: E:\xemacs-21.5.24\src\dump-id.c: ================================== extern #ifdef __cplusplus "C" #endif unsigned int dump_id; unsigned int dump_id = 1140258309U ================================== Unfortunately I couldn't understand which string you refer to, also I couldn't find anything relate do redisplay.obj in it. Am I looking at the wrong place? > >E:\xemacs-21.5.24\nt\obj\redisplay.obj " "E:\xemacs-21.5.24\nt\obj\regex.obj > >The space after "redisplay.obj" is necessary; don't omit it. We can >hope that it's just that the lexer buffer is of restricted size, but >the parser is able to concatenate the strings anyway. > >Then just restart the make, with the same command line. If that >works, we can think about what to do for the future. If it doesn't, >I'm not sure what we would do anyway. > > Emre> Then it just stopped building XEmacs. Did I do something > Emre> wrong? > >Besides using a Microsoft compiler[1], nothing. > As I said above, I have just followed the README file. Now I don't know if this error is about a compiler limitation or a command line character length limitation. Regards, Emre Sevinc Istanbul Bilgi University