Hi, On Mon, 21 Jan 2008, Dan Nicholson wrote:
> On Jan 21, 2008 5:20 PM, Johannes Schindelin <[EMAIL PROTECTED]> wrote: > > > On Mon, 21 Jan 2008, Dan Nicholson wrote: > > > > > On Jan 14, 12:40 pm, Johannes Schindelin <[EMAIL PROTECTED]> > > > wrote: > > > > > > On Mon, 14 Jan 2008, Juanma Barranquero wrote: > > > > > On Jan 14, 2008 4:51 PM, Johannes Schindelin <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > > > > > Windows experience is, and how to compile Perl modules for > > > > > > Windows. > > > > > > > > > Not much experience compiling Perl modules (outside of "perl > > > > > Makefile.PL; make; make test; make install"), but I have > > > > > experience as a C and Perl programmer on Windows. I can try. > > > > > Where to start from? > > > > > > > > First, get a full clone of msysgit.git (or update it if you have a > > > > partial one). > > > > > > > > I uploaded an intermediate state (not to be integrated as-is) to > > > > tmp/msys. But beware: you have to start msys.bat again after > > > > checking out tmp/msys, otherwise you will still be in a MinGW > > > > system, not an MSys one. > > > > > > > > After that, you can go to /src/perl and fetch&make&install perl > > > > 5.8.8 (For some strange reason, perl < 5.8 is not good enough for > > > > subversion). > > > > > > > > The next steps are to fetch&make&install expat, get subversion and > > > > subversion-deps, adjust subversion so it compiles with MSys (not > > > > MinGW), then make it, make "swig-pl-lib", "install-swig-pl-lib", > > > > and then the fun starts: > > > > > > > > In subversion/bindings/swig/perl/native, run "perl Makefile.PL". > > > > Find out why it creates the Makefiles in > > > > ../libswig_perl_lib/.libs/, or move them to the correct directory, > > > > and adjust them, because libsvn_* was not built shared, but > > > > static. > > > > > > Using subversion-1.4.x on linux, I've installed working svn perl > > > bindings many times with "make swig-pl && make install-swig-pl". No > > > extra steps should be required. I.e., you shouldn't have to run > > > "perl Makefile.PL" because the make target does that for you. > > > > As I described, it does not work. First, "install-swig-pl" does not > > fail (but does not install the modules either". Second, "perl > > Makefile.PL" creates the Makefiles in the _wrong_ directory, and I am > > not quite certain that the Makefiles are correct, either. > > I guess I'll have to go see for myself. I'm sorry... I should have been more verbose (but got distracted by this darned Ballard). The issue I see is that - the build process says that it would prefer dynamic libraries, but will go ahead and try static ones (for libsvn_*), - when I run "git svn", it works, - when I run "git svn clone <url>", it crashes, and the crashdump shows only _one_ hexadecimal address in the stackdump. No function name, no function name_s_. > > > However, I do happen to know that the build is broken in that it > > > relies on macros defined by `perl -V:cflags' to set what is needed > > > by `apr-1-config --cppflags'. > > > > > > If you can show more of an error, I might be able to suggest a fix. > > > I don't really have a Windows development machine, but I might be > > > able to figure something out and take a look. > > > > The easiest way would be to try for yourself. As you are on the > > msysgit list, I assume you have a clone of msysgit.git (probably by > > running the msysGit-netinstaller). > > No, I just cloned on a Linux machine and had a look around. But I've got > a windows partition on my laptop, so I'll try it from there. Wow, another Linux developer providing development assistance ;-) > > Just do a "cd / && git fetch", then. This should bring you all the > > current branches, and "temp/msys" is what you want. > > > > Check this branch out by "cd / && git checkout temp/msys". Now you > > need to run msys.bat again, or manually set "export MSYSTEM=MSYS", > > since Perl (and thus, the Perl bindings) need to be aware of MSys, not > > just MinGW32. > > > > Now you can run "/src/subversion/release.sh". Be sure to report any > > errors that you cannot fix, or to provide fixes for any errors you > > could fix (this is what Open Source is about; I worked _long_ and > > _hard_ to get it at the stage where it is, if other people bring it to > > perfection, I am just glad). > > > > Anybody who can fix it will be interviewed for the next Herald (this > > is not a threat, but a bonus ;-) > > I've fixed many build errors on Linux, but this would be my first > attempt on Windows. Thanks for the instructions. Thanks for your help! I really appreciate it! > > P.S.: Seems like my last P.S. on this list is unmerited... or _are_ > > you from central Europe? > > I'm not sure what your last P.S. was about. Possibly the time on my > mail? I'm not subscribed, so I just threw in a reply from Google Groups. > And I'm not from central Europe. California? (Just a guess from the timezone.) Ciao, Dscho
