Re: Problems with compile-mode

[Oscar Fuentes]

address@hidden (Daniel Pfeiffer) writes:

Hi Daniel.

> Oscar Fuentes <address@hidden> skribis:
>
>> Symptoms:
>> 
>> The *compilation* buffer shows compiler messages before the initial
>> informative text, like this:
>> 
>> g++ -c -Wall -mthreads -g -O0  -It:/include -DLP0_STATIC_LIB -MMD -MF
>> build/mingw/debug/.deps/main.d -o build/mingw/debug/main.o
>> build/mingw/debug/../../../main.cpp In file included from api.h:5,
>>                  from main.cpp:3:
>> tipo.h: In constructor `lp0::Tipo::Tipo(lp0::Symbol*)':
>> tipo.h:65: error: `x' undeclared (first use this function)
>> tipo.h:65: error: (Each undeclared identifier is reported only once for each
>> 
>>    function it appears in.)
>> make: *** [build/mingw/debug/main.o] Error 1
>> cd t:\lp0\   # -*-compilation-*-
>> Entering directory `t:\lp0\'
>> make MINGW=1
>> 
>> Compilation exited abnormally with code 2 at Wed May 05 06:39:35
>
> This looks like either Emacs on Mingw gets mixed up between the subprocesses'
> stderr and stdout.  Or compile gets mixed up with its process marker (where
> the process writes into the buffer).
>
> Since this apparently only happens on Mingw, which I don't have, I don't know
> where to start looking.  As per etc/MACHINES Mingw is not even a supported
> plattform for Emacs...  I dare not even hope you have Cygwin, to see if the
> same thing happens there?

I'm downloading the Emacs CVS source tarball and I'll see what happens
with Cygwin. My 21.1.1 was built with MinGW and it works fine, but the
21.3.50.1 binary I'm testing was downloaded from the net and I don't
know which MinGW version was used.

>> At the beginning of compile-internal, I see this comment:
>> 
>> ;; This is a rough emulation of the old hack, until the transition to new
>> ;; compile is complete.
>> 
>> Are you interested on bugs like the above, then?
>
> This comment only pertains to one deprecated function.  I don't assume you
> have used that function, but from the Recent input section below, I can't
> determine what you did.

I was reading compile.el with 21.1.1 in mind. I assumed that the
function was still used. I invoked the compilation with the usual
command (M-x compile)

>> As a separate matter, error messages issued by EDG C/C++ compilers are
>> no longer recognised. Is this a bug or previous versions recognized
>> them by accident? Do I need to add a regexp to
>> compilation-error-regexp-alist-alist ?
>
> I'm not aware of having dropped any matchers.  The old compile.el didn't
> mention EDG as one of the things it matched.  Maybe you had some extra
> configuration from somewhere.

Nope. I see that the error message detection machinery changed since
21.1.1

> If you can send me a list with various kinds of messages from this
> compiler (fatal, error, warning, info ... as available), I'll try to
> match them.

You are very kind. Here it goes:

-----------------    An error message example:

build/intel/debug/../../../struct.cpp(42): error: identifier "foo" is undefined
    foo();
    ^


-----------------    A warning:

build/intel/debug/../../../struct.cpp(44): warning #1011: missing return 
statement at end of non-void function "lp0::DefstructCodeGenerator::GenCode"
  }
  ^


-----------------    A remark:

build/intel/debug/../../../iptr.h(302): remark #981: operands are evaluated in 
unspecified order
    return lhs.get() == rhs.get();
                     ^
          detected during instantiation of "bool={bool} lp0::operator==(const 
lp0::iptr<T> &, const lp0::iptr<U> &) [with T=lp0::LP0_Object, 
U=lp0::LP0_Object]" at line 62 of "build/intel/debug/../../../trace.h"

-----------------  End of examples.

The diagnostic number (the one that goes after #) can be
de/activated. Don't count with it on all cases.

>> In GNU Emacs 21.3.50.1 (i386-mingw-nt5.0.2195)
>>  of 2004-04-27 on BERATUNG4
>> configured using `configure --with-gcc (3.3) --cflags
>> -I../../jpeg-6b-1/include -I../../libpng-1.2.4-1/include
>> -I../../tiff-3.5.7/include -I../../xpm-nox-4.2.0/include
>> -I../../zlib-1.1.4-1/include'
>> 
>> Important settings:
>>   value of $LC_ALL: nil
>>   value of $LC_COLLATE: nil
>>   value of $LC_CTYPE: nil
>>   value of $LC_MESSAGES: nil
>>   value of $LC_MONETARY: nil
>>   value of $LC_NUMERIC: nil
>>   value of $LC_TIME: nil
>>   value of $LANG: ESN
>>   locale-coding-system: iso-latin-1
>>   default-enable-multibyte-characters: t
>> 
>> Major mode: Emacs-Lisp
>> 
>> Minor modes in effect:
>>   iswitchb-mode: t
>>   mouse-wheel-mode: t
>>   menu-bar-mode: t
>>   global-font-lock-mode: t
>>   font-lock-mode: t
>>   unify-8859-on-encoding-mode: t
>>   column-number-mode: t
>>   line-number-mode: t

[snip]

Regards,

-- 
Oscar