Oberon Community Platform Forum
December 07, 2019, 08:30:30 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: compiling MyModule (22/51) not done  (Read 4066 times)
BohdanT
Sr. Member
****
Posts: 271


Life is difficult, but fortunately is short!


WWW
« on: February 15, 2010, 12:21:14 PM »

I'm getting compiler message:
compiling MyModule (22/51) not done

What is it?
I can not understand what to do ...
Logged
staubesv
Administrator
Sr. Member
*****
Posts: 387



« Reply #1 on: February 15, 2010, 01:51:08 PM »

Essentially, this means that PACO fails to compile your module and, unfortunately, also fails to provide an useful error message.

(22/51) means that PACO has started 51 threads to parse your module but 22 threads haven't reached the barrier (rsp. haven't finished their jobs) before the timeout occured (10 seconds).

If you're lucky, the new compiler is more precise about the problem (try Compiler.Compile MyModule.Mod). Otherwise,
you can either try to find the error in the code by looking at it or, if this fails, try to comment more and more parts of code until the compiler manages to compile the module (to find the place that confuses PACO).


Logged
BohdanT
Sr. Member
****
Posts: 271


Life is difficult, but fortunately is short!


WWW
« Reply #2 on: February 15, 2010, 02:55:44 PM »

Thank you for your reply.
New compiler works wonderfully.
Can I start using it on a regular basis?
How much he is ready?
Logged
staubesv
Administrator
Sr. Member
*****
Posts: 387



« Reply #3 on: February 15, 2010, 03:18:20 PM »

Hmm... maybe it is a bit too early to use it on regular basis. There are some issues as, for example, object files generated by the new compiler are not always compatible to object files generated by PACO (so mixing the compilers is not a good idea). The new compiler can compile the complete A2 releases, but last time I tried there were some stability issues when running the release using these object files.
Finally, these issues will be fixed and support for PACO will be discontinued... but "not tomorrow" ;-)
Logged
BohdanT
Sr. Member
****
Posts: 271


Life is difficult, but fortunately is short!


WWW
« Reply #4 on: February 15, 2010, 03:56:46 PM »

Quote
(22/51) means that PACO has started 51 threads to parse your module but 22 threads haven't reached the barrier (rsp. haven't finished their jobs) before the timeout occured (10 seconds).

perhaps this is related to this problem:
Re: Slow Aos.Exe
because I have an old computer, and a large module

We look forward to new compiler  Smiley
Logged
BohdanT
Sr. Member
****
Posts: 271


Life is difficult, but fortunately is short!


WWW
« Reply #5 on: February 15, 2010, 04:19:32 PM »

Yes, it is the reason why, as I can not compile for example:
 compiling SyntaxHighlighter (36/70) not done
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!