ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> perl5-porters
perl5-porters
Re: dmake syntax, Win64 and MS compilers.
by Steve Hay other posts by this author
Nov 7 2009 7:09AM messages near this date
Re: dmake syntax, Win64 and MS compilers. | C++ fail with KeywordRPN
2009/11/7 Steve Hay <steve.m.hay@[...].com> :
>  2009/11/7 Sisyphus <sisyphus1@[...].au>:
> > Hi,
> >
> > In the win32/makefile.mk, pertaining to the building of perl with 64-bit
> > Microsoft compilers (in particular "Microsoft Platform SDK for Windows
> > Server 2003 R2"), we have:
> >
> > .IF "$(WIN64)" == "define"
> > LIBBASEFILES    = $(LIBBASEFILES) bufferoverflowU.lib
> > .ENDIF
> >
> > With nmake there's no problem with that but, to dmake, that middle line is
> > an error because of the circularity regarding LIBBASEFILES. (Sorry, I've
> > lost the exact error message, though I can easily re-create it if that's
> > important.)
> >
> > Is there a simple way of rewriting that middle line that both keeps dmake
> > happy && has the desired effect ?
> 
>  Yes, use +=, as is used elsewhere already.
> 
>  I'd commit it now, but by ssh doesn't seem to be working...
> 

It works again now after I set a push.default (not sure if that really
made the difference since it's been warning about not having one for a
while now...), so it's in as d541574574df104c39aaaba6d251728919eacd38.
Thread:
Sisyphus
Steve Hay
Steve Hay

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved