Wednesday, October 6, 2004, 10:13:35 PM, Khairul Azhar wrote:
> On Wed, 6 Oct 2004 13:38:45 -0400, John Szakmeister
> <john@szakmeister.net> wrote:
>
>> > Hmm...Isn't GetModuleFileNameW (the Unicode version of
>> > GetModuleFileName) only implemented under Windows NT-based systems?
>> > What is it doing in a Win98 MBCS-based system?
>>
>> I forgot that you were running on Win 98. This may be a problem.
>
> Can you confirm this problem? Are you planning to solve this problem
> anytime soon? Do I need to file a bug report?
Unfortunately, I cannot confirm it. I don't have access to a Win 98
machine. Every machine I can touch is an NT derivative. :-( With
that said, it would be hard to solve a problem when I can recreate it.
Before you file a bug report, I think we need to set up a reproduction
recipe. Can you provide a transcript of what you're doing? Can you
also include the path of where you installed Subversion, and the path
for where you're running svnadmin from?
However, the more I think about this, the more I think
GetModuleFileNameW() isn't necessarily to blame. If Win 98 didn't have
this function at all, the loader would fail to start the executable
altogether because it wouldn't be able to resolve the reference to
GetModuleFileNameW(). It's not failing in that regard, so there
*must* be something there... I just can't tell what it should do by
default.
>> ... The BDB backend doesn't work on Win 98
>
> I knew this the hard way. For a while, the 1.1.0-rc3 version of
> svnadmin worked. Now I think it's because the alignment of the planets
> were correct, and that the (uninitialized) ucs2_path wasn't corrupted
> with non-UTF-8 garbage.
I think there is something else going on here... I'm not sure what
though. Every command-line utility is calling this routine, we should
be seeing the same failure in other tools.
BTW, I compared the source tree for 1.1.0-rc3 and 1.1.0, and I don't
see a difference that would've all of sudden made svnadmin stop
working.
>> > > This is what I find perplexing. 'svn', 'svnlook', 'svnversion', and
>> > > 'svndumpfilter' all call svn_cmdline_init(), and they're fine. What
>> > > in the world is making 'svnadmin' and 'svnserve' work differently?
>
> It probably explains why 'svn', 'svnlook', 'svnversion' and
> 'svndumpfilter' (seemed to) worked. They simply got lucky.
No, unfortunately, it doesn't. All of those function call this routine
too... there is something else wrong here. All of those files should be
in the bin/ directory of the installation, and therefore, should all be
manipulating similar paths. The only part that changes in is the
executable name at the end.
> BTW, what is Subversion doing with the module path anyway?
It appears to be setting up a path to the locale files, and I'm
guessing that's to support internationalization.
>> > Anyway, I'll be downloading the Microsoft Layer for Unicode (MSLU) for
>> > Windows 95/98/Me. I'll let you know whether it solves the problem when
>> > I get back to work tomorrow.
>>
>> Let me know if that works, but looking at the documentation, it appears
>> that you the binaries need to be linked against another DLL. I don't
>> think our Win32 binaries are linked against that particular DLL. :-(
>
> You're right. It's for developers only. I've been living in Java for
> too long... :-(
I figured as much.
If you can, try to get a reproduction recipe going. I'm going to see
if I can dig up an old Win 98 CD... I have VMWare, so I can install a
copy under a virtual machine temporarily. If I can reproduce the
problem, then we can enter it into the issue tracker, and get this
problem resolved.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 7 05:28:15 2004