Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 1999-12

Cycling compiler on win32

6 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Snijders, V.
I can remove the usage of the envvar for 0.99.12b, but then there is the 128 byte cmdline limit.

I would like to try that, because I think that in make cycle, the command line limit doesn't reach 128 bytes. I think (but I want to verify that), that the command line limit doesn't come into action when doing a make cycle, but only when you try to compile the packages or lcl, which needs gtk, fcl and rtl (a lot of unit and inc-paths).

What do I need to change to turn of the usage of envvar for 0.99.12b?

Reply by email

Vincent Snijders

Since abaout a week, I get the following error when cycling the compiler on my win98 computer

asw -o wprt0.ow wprt0.as
asw -o wdllprt0.ow wdllprt0.as
ppc386.exe !FPCEXTCMD -Us -Sg syswin32.pp
syswin32.pp(25,2) Fatal: Can't open include file systemh.inc

It happens right at the beginning when the RTL gets compiled for the first time.

I am wondering what the !FPCEXTCMD is doing in the command line. Is FPCEXTCMD an environment variable which needs to be set?

I have read on this list that setting the environment variable FPCDIR is not neccesary anymore. Is that true?

By the way, I am impressed by the progress which has been made lately. Good job, Marc and Shane! I hope I can find some time to join in in the coming months, but I guess I am not as committed as you guys.

Reply by email

Peter Vreman
you wrote 28 lines
> At 08:20 13-12-99 , you wrote: > >Since abaout a week, I get the following error when cycling the compiler on > >my win98 computer > > > >asw -o wprt0.ow wprt0.as > >asw -o wdllprt0.ow wdllprt0.as > >ppc386.exe !FPCEXTCMD -Us -Sg syswin32.pp > >syswin32.pp(25,2) Fatal: Can't open include file systemh.inc > > > Try compiling with 'make OPT=-vt' I did just that and the result is the same as above. > >I am wondering what the !FPCEXTCMD is doing in the command line. Is > >FPCEXTCMD an environment variable which needs to be set? > > It's a variable set internaly in the Makefile to overcome the 128 byte > commandline limit. I think the above problem is caused by the fact that ppc386.exe 0.99.12b, which I use to start the make cycle, does not recognize the !FPCEXTCMD option on the command-line. I downloaded the last snapshot and used that to cycle the compiler and worked. Can you confirm my suspicion that 0.99.12b is not good enough anymore to cycle the compiler?

I can remove the usage of the envvar for 0.99.12b, but then there is the 128 byte cmdline limit.

Is there a workaround or do I have to download a snapshot and just take my chances that is not too buggy (as could happen with snapshots) to cycle a new compiler?

Use the go32v2 compiler, which doesn't have the commandline limit.

Peter

Reply by email

Vincent Snijders
At 08:20 13-12-99 , you wrote: >Since abaout a week, I get the following error when cycling the compiler

on

Show quoted text 9 lines
>my win98 computer > >asw -o wprt0.ow wprt0.as >asw -o wdllprt0.ow wdllprt0.as >ppc386.exe !FPCEXTCMD -Us -Sg syswin32.pp >syswin32.pp(25,2) Fatal: Can't open include file systemh.inc Try compiling with 'make OPT=-vt'

I did just that and the result is the same as above.

Show quoted text 5 lines
>I am wondering what the !FPCEXTCMD is doing in the command line. Is >FPCEXTCMD an environment variable which needs to be set? It's a variable set internaly in the Makefile to overcome the 128 byte commandline limit.

I think the above problem is caused by the fact that ppc386.exe 0.99.12b, which I use to start the make cycle, does not recognize the !FPCEXTCMD option on the command-line.
I downloaded the last snapshot and used that to cycle the compiler and worked.

Can you confirm my suspicion that 0.99.12b is not good enough anymore to cycle the compiler?
Is there a workaround or do I have to download a snapshot and just take my chances that is not too buggy (as could happen with snapshots) to cycle a new compiler?

Thanks in advance,

Vincent Snijders

Reply by email

Florian Klaempfl
Vincent Snijders wrote 5 lines
I downloaded the last snapshot and used that to cycle the compiler and worked. Can you confirm my suspicion that 0.99.12b is not good enough anymore to cycle the compiler?

I'am still using 0.99.12b and make cycle works fine for go32v2

Is there a workaround or do I have to download a snapshot and just take my chances that is not too buggy (as could happen with snapshots) to cycle a new compiler?

Just keep some older versions, so it shouldn't be a problem :)

Reply by email

Peter Vreman
to Vincent Snijders: Since abaout a week, I get the following error when cycling the compiler on my win98…
you wrote 7 lines
Since abaout a week, I get the following error when cycling the compiler on my win98 computer asw -o wprt0.ow wprt0.as asw -o wdllprt0.ow wdllprt0.as ppc386.exe !FPCEXTCMD -Us -Sg syswin32.pp syswin32.pp(25,2) Fatal: Can't open include file systemh.inc

Try compiling with 'make OPT=-vt'

Show quoted text 5 lines
It happens right at the beginning when the RTL gets compiled for the first time. I am wondering what the !FPCEXTCMD is doing in the command line. Is FPCEXTCMD an environment variable which needs to be set?

It's a variable set internaly in the Makefile to overcome the 128 byte commandline limit.

I have read on this list that setting the environment variable FPCDIR is not neccesary anymore. Is that true?

Yes. If the makefile has a correct value for fpcdir (all things in CVS have this) it's not needed anymore. Also the compiler includes by default /usr/lib/fpc/<VERSION>/{rtl,units}/<TARGET>

Peter

Reply by email