Re: [Fwd: How to handle "The following character string is too long... NMAKE : fatal error U1077: 'echo' : return code '0x1'" problem while compiling XEmacs?]

"Stephen J. Turnbull" <[email protected]> Fri, 24 Feb 2006 22:15:16 +0900
Newsgroups gmane.emacs.xemacs.windows
Organization The XEmacs Project
Message-ID <[email protected]>
>>>>> "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?

    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

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.

Footnotes: 
[1]  There's nothing wrong with using a Microsoft compiler, but when
you encounter a compiler limitation like this one, nobody can help you
except Microsoft.

-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.