To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=43077 Issue #:|43077 Summary:|Backwards-compatibility issue with mktmp Component:|tools Version:|current Platform:|PC URL:| OS/Version:|Windows XP Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|dmake Assigned to:|hjs Reported by:|shay
------- Additional comments from [EMAIL PROTECTED] Fri Feb 18 05:44:39 -0800 2005 ------- I have an existing makefile.mk for a project that I'm involved in which has long been working with dmake 4.1. I've just tried upgrading to dmake 4.3, and I now find that something doesn't work. I've reduced the problem to the following sample makefile.mk: .USESHELL : FOO = C:\foo BAR = $(FOO:s,\,\\,) all : @echo FOO=$(FOO) @echo BAR=$(BAR) @type $(mktmp $(FOO)) @type $(mktmp $(BAR)) Running this under dmake 4.1 produces this output: FOO=C:\foo BAR=C:\\foo C:♀ooC:\foo As you can see, outputting data containing backslashes to a mktmp file doesn't work unless the backslashes are doubled-up first. My real makefile.mk therefore employs exactly that strategy -- doubling-up the backslashes. However, running the above under dmake 4.3 (current CVS version) produces this: FOO=C:\foo BAR=C:\\foo C:\foo C:\\foo Now we see that outputting single backslashes works fine, so doubling them up actually results in double backslashes in the mktmp file. I have two questions about this change in behaviour: 1. Is it deliberate? It looks like a fix for a bug in dmake 4.1, but I couldn't see any mention of it in the NEWS file, so perhaps the change was not intended and is hence actually a bug in dmake 4.3? 2. If it is deliberate, then what should I do in my makefile.mk so that it can output data containing backslashes to a mktmp file in such a way that it works with both dmake 4.1 and dmake 4.3? Thanks, - Steve --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]