23.12.2011 1:26, Joost van der Sluis пишет:
What I did was this: 'make install PREFIX=c:\lazarus\fpc\2.7.1\' the
trailing backslash is important...
Then make runs (among others) the following command:
.\fpmake.exe install --localunitdir=../.. --globalunitdir=.. --os=win32
--cpu=i386 -o -Ur -o -Xs -o -O2 -o -n -o
-FuC:/svn/fpc-trunk/rtl/units/i386-win32 -o
-FuC:/svn/fpc-trunk/packages/hash/units/i386-win32 -o
-FuC:/svn/fpc-trunk/packages/paszlib/units/i386-win32 -o
-FuC:/svn/fpc-trunk/packages/fcl-process/units/i386-win32 -o
-FuC:/svn/fpc-trunk/packages/fpmkunit/units/i386-win32 -o -FE. -o
-FUunits/i386-win32 -o -di386 -o -dRELEASE
--compiler=C:/svn/fpc-trunk/compiler/ppc386.exe --prefix=c:\lazarus\fpc\2.7.1\
--unitinstalldir=c:\lazarus\fpc\2.7.1\/units/i386-win32/fcl-base -ie -d
Note the two spaces after the prefix. Which result in the error message
that the directory "c:\lazarus\fpc\2.7.1 \bin" coudn't be created. (Note
the space)
Can you reproduce that? I tried with a simple hello-world kind of
application and in that case I can't reproduce it either.
This is on Windows 7 in a virtual machine. (kvm)
Just some notes:
- syswin.inc code looks like any number of delimiters between parameters are
skipped.
- this extra whitespace is added by the makefile, suggesting some buggy/incorrect processing in
make.exe or makefile itself.
- the extra character may be not a whitespace (#32), but something looking like one (e.g.
non-breaking space with code #160)
Sergei
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
