Hi
From several days I've try to make all fpc myself, but to do this under WIN98 is not so clear that it can be.
I've found some bugs in makefile, and somebody may change FPCM to be generated proper MAKEFILE
my 4 suggestion:

--------1--------
/* current MAKEFILE
ifdef PWD
BASEDIR:=$(subst \,/,$(shell $(PWD)))
ifdef inCygWin
ifneq ($(findstring /cygdrive/,$(BASEDIR)),)
BASENODIR:=$(patsubst /cygdrive%,%,$(BASEDIR))
BASEDRIVE:=$(firstword $(subst /, ,$(BASENODIR)))
BASEDIR:=$(subst /cygdrive/$(BASEDRIVE)/,$(BASEDRIVE):/,$(BASEDIR)) endif
endif
else
BASEDIR=.
endif
/** in last line change to ..,like FPCDIR
BASEDIR=c:/pp
--------2-----------
/* current MAKEFILE
ifdef INSTALL_FPCPACKAGE
INSTALL_BASEDIR:=/pp
/* I change to .., but I don't know, how it be under Linux INSTALL_BASEDIR:=c:/pp
------------3--------------
please remove line:
override DEFAULT_FPCDIR=..
because it can't be pass from command line f.e: 'make all DEFAULT_FPCDIR=c:\fp'
--------4-----------

ifdef DEFAULT_FPCDIR
ifeq ($(FPCDIR),wrong)
override FPCDIR:=$(subst \,/,$(DEFAULT_FPCDIR))
ifeq ($(wildcard $(addprefix $(FPCDIR)/,rtl units)),) override FPCDIR=wrong
endif
endif
endif
/* change to :
ifdef DEFAULT_FPCDIR
override FPCDIR:=$(subst \,/,$(DEFAULT_FPCDIR))
endif

Darek

What is proper? Windows is so broken for command line support, we try to support it as best as possible, but not to make it work less under the unix platforms.

Why? Fixing it to c:/pp is also not good. And it means that PWD is not installed so it should already give an error.

Why fix it to c:/ ?

This is taken from the Makefile.fpc and is only used to be able to build the tree without needing FPCDIR set.

Why remove the safety check? There must be a rtl or units dir else your installation is broken.

Peter

I agree with you. make cycle works ok for me for go32v2 and win32 on win95 and winme and I'd guess for win98 too, but the full make go32v2zip and win32zip don't! I've sent the logs to core but... Apparently the problem is with redirection? I was told that they'd work on win98- but it sounds as if they don't! The strange thing is that they used to work ok for me on win95 and me, I think until the modifications were made for cross compilation a few months ago. They are now IMHO just much too complicated - maybe removing the checking would be a solution and just getting them to do what you tell them to do. What happens for me is that the win32 version under win95 does what's shown below, the go32v2 version come up with a lot of make error messages . Any ideas re the problem welcome...

Sigh...

Regards John

command line...
MAKE win32zip OPT="-Xs" SNAPSHOT=1 D:\FPK &> C:\MAKEW.TMP

o/p to screen
snip of process creates...

process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -iTO, ...) f
ailed.
process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -iVSPTPSOTO,
...) failed.
process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -iSP, ...) f
ailed.
process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -iTP, ...) f
ailed.
process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -iSO, ...) f
ailed.
process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -iTO, ...) f
ailed.
process_begin: CreateProcess((null), D:/fpk/compiler/ppcross386.exe -Ur -Twin32
-Xs -OG2p3 -n -Fi../inc -Fi../i386 -FE. -Xs -di386 -dRELEASE -Us -Sg syswin32.pp
, ...) failed.
make (e=2): The system cannot find the file specified. MAKE.EXE[6]: *** [syswin32.ppu] Error 2
MAKE.EXE[5]: *** [win32_all] Error 2
MAKE.EXE[4]: *** [rtl_install] Error 2
MAKE.EXE[3]: *** [installbase] Error 2
MAKE.EXE[2]: *** [fpc_zipinstall] Error 2
MAKE.EXE[1]: *** [zipinstall] Error 2
C:\PP\BIN\WIN32\MAKE.EXE: *** [win32zip] Error 2

makew.tmp
C:/PP/BIN/WIN32/MAKE.EXE zipinstall OS_TARGET=win32 MAKE.EXE[1]: Entering directory `D:/fpk'
C:/PP/BIN/WIN32/MAKE.EXE fpc_zipinstall ZIPTARGET=installbase ZIPNAME=basew32 FPC=D:/fpk/compiler/ppc386.exe ZIPDESTDIR=D:/fpk FPCMAKE=D:/fpk/utils/fpcm/fpcmake.exe
MAKE.EXE[2]: Entering directory `D:/fpk'
C:/PP/BIN/WIN32/MAKE.EXE installbase INSTALL_PREFIX=D:/fpk/../fpc-pack ZIPINSTALL=1
MAKE.EXE[3]: Entering directory `D:/fpk'
C:/PP/BIN/WIN32/ginstall.exe -m 755 -d D:/fpk/../fpc-pack C:/PP/BIN/WIN32/ginstall.exe -m 755 -d D:/fpk/../fpc-pack/doc/fpc C:/PP/BIN/WIN32/ginstall.exe -m 755 -d
D:/fpk/../fpc-pack/cross/i386-win32/bin/win32
C:/PP/BIN/WIN32/MAKE.EXE compiler_install FPC=D:/fpk/compiler/ppcross386.exe ZIPDESTDIR=D:/fpk FPCMAKE=fpcmake
MAKE.EXE[4]: Entering directory `D:/fpk'
C:/PP/BIN/WIN32/MAKE.EXE -C compiler install
MAKE.EXE[5]: Entering directory `D:/fpk/compiler'
C:/PP/BIN/WIN32/MAKE.EXE -C utils install
MAKE.EXE[6]: Entering directory `D:/fpk/compiler/utils' C:/PP/BIN/WIN32/ginstall.exe -m 755 -d
D:/fpk/../fpc-pack/cross/i386-win32/bin/win32
C:/PP/BIN/WIN32/upx.exe fpc.exe ppufiles.exe ppudump.exe ppumove.exe Ultimate Packer for eXecutables
Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001
UPX 1.20w Markus F.X.J. Oberhumer & Laszlo Molnar May 23rd 2001

File size Ratio Format Name
-------------------- ------ ----------- -----------

Packed 0 files.
C:/PP/BIN/WIN32/cp.exe -fp fpc.exe ppufiles.exe ppudump.exe ppumove.exe D:/fpk/../fpc-pack/cross/i386-win32/bin/win32
MAKE.EXE[6]: Leaving directory `D:/fpk/compiler/utils' C:/PP/BIN/WIN32/upx.exe ppc386.exe
Ultimate Packer for eXecutables
Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001
UPX 1.20w Markus F.X.J. Oberhumer & Laszlo Molnar May 23rd 2001

File size Ratio Format Name
-------------------- ------ ----------- -----------

Packed 0 files.
C:/PP/BIN/WIN32/ginstall.exe -m 755 -d
D:/fpk/../fpc-pack/cross/i386-win32/bin/win32
C:/PP/BIN/WIN32/cp.exe -fp ppc386.exe
D:/fpk/../fpc-pack/cross/i386-win32/bin/win32
C:/PP/BIN/WIN32/ginstall.exe -m 755 -d D:/fpk/../fpc-pack/msg C:/PP/BIN/WIN32/cp.exe -fp msg/errord.msg msg/errore.msg msg/errores.msg msg/errorf.msg msg/errorn.msg msg/errorpl.msg msg/errorpli.msg msg/errorr.msg msg/errorrw.msg D:/fpk/../fpc-pack/msg MAKE.EXE[5]: Leaving directory `D:/fpk/compiler'
MAKE.EXE[4]: Leaving directory `D:/fpk'
C:/PP/BIN/WIN32/MAKE.EXE rtl_install FPC=D:/fpk/compiler/ppcross386.exe ZIPDESTDIR=D:/fpk FPCMAKE=fpcmake
MAKE.EXE[4]: Entering directory `D:/fpk'
C:/PP/BIN/WIN32/MAKE.EXE -C rtl install
MAKE.EXE[5]: Entering directory `D:/fpk/rtl'
C:/PP/BIN/WIN32/MAKE.EXE -C win32 all
MAKE.EXE[6]: Entering directory `D:/fpk/rtl/win32' as -o wprt0.o wprt0.as
as -o wdllprt0.o wdllprt0.as
as -o gprt0.o gprt0.as
D:/fpk/compiler/ppcross386.exe -Ur -Twin32 -Xs -OG2p3 -n -Fi../inc -Fi../i386 -FE. -Xs -di386 -dRELEASE -Us -Sg syswin32.pp MAKE.EXE[6]: Leaving directory `D:/fpk/rtl/win32'
MAKE.EXE[5]: Leaving directory `D:/fpk/rtl'
MAKE.EXE[4]: Leaving directory `D:/fpk'
MAKE.EXE[3]: Leaving directory `D:/fpk'
MAKE.EXE[2]: Leaving directory `D:/fpk'
MAKE.EXE[1]: Leaving directory `D:/fpk'
settings pp=C:/V10NW/BIN/PPC386 path=C:\PP\BIN\WIN32; comspec=C:\WINDOWS\COMMAND.COM

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.

What is proper? Windows is so broken for command line support, we try to support it as best as possible, but not to make it work less under the

unix

platforms.

of course

Why? Fixing it to c:/pp is also not good. And it means that PWD is not installed so it should already give an error.

if PWD is not installed -> error is at begin
ifeq ($(PWD),)
$(error You need the GNU utils package to use this Makefile)

and why is fixing at line and its good:
override FPCDIR=c:/pp

Why fix it to c:/ ?

I don't test in detail, but I do this.

Why remove the safety check? There must be a rtl or units dir else your >

installation is broken.
If I set something manual, that is not need safety check, but it may left.

I must test Your previous fix.

Darek

I have:

C:/PP/BIN/WIN32/MAKE.EXE -C compiler distinstall
MAKE.EXE[5]: Entering directory `C:/pp/source/compiler' C:/PP/BIN/WIN32/MAKE.EXE -C utils install
MAKE.EXE[6]: Entering directory `C:/pp/source/compiler/utils' C:/PP/BIN/WIN32/ginstall.exe -m 755 -d C:/pp/source/../fpc-pack/bin/win32 C:/PP/BIN/WIN32/upx.exe fpc.exe ppufiles.exe ppudump.exe ppumove.exe Ultimate Packer for eXecutables
Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001
UPX 1.20w Markus F.X.J. Oberhumer & Laszlo Molnar May 23rd 2001

File size Ratio Format Name
-------------------- ------ ----------- ----------- 176640 -> 55808 31.59% win32/pe fpc.exe 105984 -> 36864 34.78% win32/pe ppufiles.exe 155648 -> 48128 30.92% win32/pe ppudump.exe 117760 -> 40448 34.34% win32/pe ppumove.exe -------------------- ------ ----------- ----------- 556032 -> 181248 32.59% [ 4 files ]

Packed 4 files.
C:/PP/BIN/WIN32/cp.exe -fp fpc.exe ppufiles.exe ppudump.exe ppumove.exe C:/pp/source/../fpc-pack/bin/win32
MAKE.EXE[6]: Leaving directory `C:/pp/source/compiler/utils'

maybe You must change then
BASEDIR
INSTALL_BASEDIR

I move all to C:\pp

and all name of file in bin\win32\*.exe change to small

Darek

Darek, these are the make scripts that I have trouble with under win95 and ME- I don't have are supposed to work under win98 - but I suspect they don't. What should happen is a complete make, from scratch, of the compiler, rtl, ide and other units of the distribution and then they should all be zipped into the 5-8 distribution files. As you saw, what happens for me (and you) for win32 is something else. The go32v2 also doesn't work!

Peter says that the problem with ME is redirection - strangely it often fails because echo xxx > jim doesn't create a file - but I think that there are other problems too. Also he doesn't test makefile modifications on win9x because he doesn't have it... but that doesn't explain why it doesn't work on win95. Also the very strange thing is that these used to work for me on win95 and ME until the makefiles became more complex recently and do more detection of what already exists than before.

I'd be grateful if you can try them under win98, and if they don't work send the logs to [devel] and if you can suggest what's wrong with the makefile.

I each case I unzip the v11 fpc.zip (from ftp.freepascal.org) into d:\fpk. The unzipped utilities from the v10 distribution are in c:\pp\bin\win32 or go32v2, and the starting v10 compiler is in c:/v10nw/bin/win32 or go32v2

TIA for any help.

Regards John

rem for win32 snapshots
set PP=C:/V10NW/BIN/PPC386
set path=C:\PP\BIN\WIN32;
d:
d:\fpk
MAKE win32zip OPT="-Xs" SNAPSHOT=1 D:\FPK &> C:\MAKEW.TMP

rem for go32 snapshot
set PP=C:/V10N/BIN/PPC386
set path=C:\PP\BIN\GO32V2;
D:
CD\FPK
MAKE go32v2zip OPT="-Xs" SNAPSHOT=1 D:\FPK &> C:\MAKE.TMP

Hi
For me that was not depend on case of Win,
I write my configurations:
command line:
c:\pp\bin\win32\make win32zip >rri
You can use --debug :
c:\pp\bin\win32\make win32zip --debug >rri

snapshot is in c:\pp\source
compiler c:\pp\bin\win32

all directory like from install FPC 1.0.10
I notice that best directory for make is c:\pp
I don't use PATH command in autoexec, make can use start directory &> don't work
I change BASEDIR and INSTALL_BASEDIR in all makefile, but must try witch is obsolete,

If You want , send me full detail log from MAKE (on private mail), I can