Greetings.

When running 'make zipinstall' under Win32, the process ends with the following error:

cp.exe: cannot remove old link to
`D:/fpc/../fpc-pack/examples/oracle/.svn/text-

base/Makefile.fpc.svn-base': Permission denied

cp.exe: cannot remove old link to
`D:/fpc/../fpc-pack/examples/oracle/.svn/text-

base/Makefile.svn-base': Permission denied

cp.exe: cannot remove old link to
`D:/fpc/../fpc-pack/examples/oracle/.svn/text-

base/oraclew.pp.svn-base': Permission denied

cp.exe: cannot remove old link to
`D:/fpc/../fpc-pack/examples/oracle/.svn/text-

base/test01.pp.svn-base': Permission denied

make[7]: *** [fpc_exampleinstall] Error 1

make[7]: Leaving directory `D:/fpc/packages/base/oracle'

make[6]: *** [oracle_distinstall] Error 2

make[6]: Leaving directory `D:/fpc/packages/base'

make[5]: *** [base_distinstall] Error 2

make[5]: Leaving directory `D:/fpc/packages'

make[4]: *** [packages_distinstall] Error 2

make[4]: Leaving directory `D:/fpc'

make[3]: *** [installother] Error 2

make[3]: Leaving directory `D:/fpc'

make[2]: *** [install] Error 2

make[2]: Leaving directory `D:/fpc'

make[1]: *** [fpc_zipinstall] Error 2

make[1]: Leaving directory `D:/fpc'

make: *** [zipinstall] Error 2

This is being built on a Windows 2003 SBS setup with all the latest fixes, etc. I am logged in with the Administrator username so I have full rights to this machine.

Robert Wolfe ( / )
Computer Programmer/Analyst & Web Programmer
SRDAR, Roswell Park Cancer Institute, Buffalo, New York 716-845-5788 | http://www.srdar.org

This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.

This is a know issue. It is a bug in the non-fpc cp.exe for win32. We can't fix this. Use a svn export instead of svn checkout.

The daily v211 & v20 win32 snapshots are currently working ok - they are done on winme which doesn't have this problem, so you could download the snapshot from ftp.freepascal.org .../snapshots/ if that's what you want.

Regards John

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

Does this mean we can't do snapshot on win32? Is there a fix planned? Eg couldn't we write a fpc version of cp - guess this would only be a few lines or is it more complicated than this?

Regards John

John wrote

Does this mean we can't do snapshot on win32? Is there a fix planned? Eg couldn't we write a fpc version of cp - guess this would only be a few lines or is it more complicated than this?

1) Do you get this error too when building Win32 snapshots?

2) It certainly doesn't mean that it isn't possible to create Win32 snapshots. It just means exactly what Peter stated - one needs to use exported sources (obtained using "svn export") rather than svn checkout. Note that this can be done even locally when having checked out sources.

Tomas

Does this mean we can't do snapshot on win32? Is there a fix planned? Eg couldn't we write a fpc version of cp - guess this would only be a few lines or is it more complicated than this?

This situation is there already for years.

> Does this mean we can't do snapshot on win32? Is there a fix planned? Eg > couldn't we write a fpc version of cp - guess this would only be a few > lines or is it more complicated than this? This situation is there already for years.

If I get it right, one is supposed to have CYGWIN for win32 anyway: FP IDE absolutely doesn't run without it (it's bad, because, for example, running two applications using different CYGWIN libraries simultaneously makes fail at least one of them and so on). CYGWIN includes these UNIX style thingies (pwd.exe, cp.exe etc.). So that's it (if CYGWIN binaries directory is in the search path).

I compile 2.1.x with this batch file:

d:
cd \fpc
ren lastd _lastd // compiled compiler, previous build ren tmpsrc _tmpsrc // exported sources of the previous build

cd fpcSVN // local repository
svn update // updating repository svn export . d:\fpc\tmpsrc // exporting sources, if I mess with local repository, I run "svn cleanup" to remove junk

cd ..\tmpsrc // exported sources, first make will produce (not so) junk here d:\fpc\2.0.4.rc2\bin\i386-win32\make clean all FPC=d:\fpc\2.0.4.rc2\bin\i386-win32\ppc386.exe

  // running some other make may be bad, and I still use 2.0.4rc2 for no reason,

d:\fpc\2.0.4.rc2\bin\i386-win32\make install INSTALL_PREFIX=d:/fpc/lastd FPC=d:\fpc\tmpsrc\compiler\ppc386.exe

  // now there must be all native FPC files in d:\fpc\lastd\ (and FP IDE won't run without some tuning)

And "make" uses d:\cygwin\bin\ utilities heavily.

Technically, this should not happen on ANY version of Windows. But, I digress. I'll just sit here building my Sparc Linux builds and making them available for download from my site :)

Robert Wolfe ( / )
Computer Programmer/Analyst & Web Programmer
SRDAR, Roswell Park Cancer Institute, Buffalo, New York 716-845-5788 | http://www.srdar.org

are

done on winme which doesn't have this problem, so you could download

the

snapshot from ftp.freepascal.org .../snapshots/ if that's what you

want.

We

copied,

This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.

This is not correct. You don't need cygwin, we provide all the require unix tools. The makefiles even don't work in cygwin. They can only be run from the CMD prompt.

That the FP IDE requires the cygwin1.dll is simply because the mingw32 gdb was not working. If you can remove the dependency on gdb for debugging you are welcome to provide patches.