That is consistent with misunderstanding what is in Make.out.log.txt
and Make.error.log.txt.
In that make errors would appear in the same file as GCJ errors how do
you imagine that confusing the two would make any difference? I would
either have no error or both if GCJ had given an error. Grante
On 3/30/07, Mike Stump <[EMAIL PROTECTED]> wrote:
On Mar 30, 2007, at 12:32 PM, Null Heart wrote:
> I was just poking around with the latest snapshot for fun
Two thoughts come to mind. First, qualify your system with a known
to build, known to be good compiler. Build it 20 times, if
You could just remove the '##'.
Soma
On 3/30/07, JoseD <[EMAIL PROTECTED]> wrote:
Hi. Just wanted to share that the following macro gives an error on latest
versions of GCC, but is reported to work on 2.95.3 (tested on MorphOS but
should be the same for other OSses of course).
Both an old vers
I was just poking around with the latest snapshot for fun when I came
across a huge problem: the make would fail without reason. It wouldn't
give any actual reason at all. It would be building the HTML parser
and after a bit would just give up. make gave the error "[error 1]"
about the target file
