New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parallel building with Win32 dmake problems #14518
Comments
From @bulk88Created by @bulk88This really shouldn't be a ticket, but the mailing list server has a I decided to implement parallel building with dmake since nmake's clone I am using dmake that came with strawberry perl 5.18. It calls itself Default Configuration: Please read the NEWS file for the latest release notes. C:\perl521> But dmake parallel ("dmake -P2 all") has very bad design in finding C:\perl521\srcnewb4opt\win32>dmake -P2 all Creating library ntdllundec.lib and object ntdllundec.exp LIB : warning LNK4001: no object files specified; libraries used By my eye, "dmake -P2 ../mini/av.obj" is faster than "dmake -P2 I am thinking that the only way to hack fix the performance problem with Perl Info
|
From @bulk88[bad parallel dmake procs only.CSV](https://rt-archive.perl.org/perl5/Ticket/Attachment/1331679/711111/bad parallel dmake procs only.CSV) |
From @bulk88detailed IO log mentioned in OP -- |
From @bulk88[bad parallel dmake procs+disk IO.7z](https://rt-archive.perl.org/perl5/Ticket/Attachment/1331687/711117/bad parallel dmake procs+disk IO.7z) |
From @steve-m-hay[...]
I haven't looked through the details, but I have no particular problem Another option might be to put all the echo commands into a batch file |
The RT System itself - Status changed from 'new' to 'open' |
From @bulk88On Tue Feb 17 00:36:33 2015, shay wrote:
This idea was done in the patch in https://rt-archive.perl.org/perl5/Ticket/Display.html?id=123867 so this ticket can be closed if nobody else has objections. -- |
From @tonycozOn Tue Apr 28 12:40:02 2015, bulk88 wrote:
Done. Tony |
@tonycoz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#123854 (status was 'resolved')
Searchable as RT123854$
The text was updated successfully, but these errors were encountered: