No idea, why it doesn't work any longer, but after the mentioned date, I can't compile aMule-Snapshots on any of my machines!
With Debian 4 I have the same error in Scanner.l.../Scanner.l:195: error: 'yylex_destroy' was not declared in this scope
as with MingW. It occurred on August, 10th 2008 without me making any changes in the development environment (except maybe some security update or other under Debian).
Today I experimented a little with the arguments to configure but to no avail (debug on/off, optimization on/off, and so on)...
I tried with fresh directories, unpacking under Debian and under Win$, ...
I did not try the mentioned patch for Scanner.l! If such a thing is really still necessary, there is something wrong with the sources and/or the configure process!
....
Update:
For some dependencies I had to use flex 2.3.4 on Debian4. I now installed version 2.5.33 and tried compilation again: same error! I first had to delete Scanner.cpp manually to force flex to regenerate it! After that, compilation went through!
For Debian4 the problem is solved now, as it seems. But still I wonder why it occurred at all?!
Next step: another make in MingW...
I share the same source directory for Debian and Win$. Scanner.cpp was regenerated by my Debian-based compilation. And now I also can compile the Win$-binaries again!
Just amazing!
But ok, I will not think too much about it. Scanner did make trouble some time before, as I remember.
Now I have the problem, that the freshly compiled amuled won't let me connect to it with amuleweb or amulecmd. One problem solved, next problem at the door step :-)
Cheers,
Radek