Sign in Join

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

Mailing lists / lazarus / 2020-04

Can't build fpc trunk x64 win32/64

18 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

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

leyba bronstain

Hi guys. I need your help.

I try build trunk compiler x64 for windows. I was extract stable release fpc_x64 form lazarus-2.0.8-fpc-3.0.4-win64.exe installer and put it to separate folder fpc_stable_x64. Also I put into fpc_stable_x64 folder bingw64 folder and fixed the file fpc.cfg as follows:

--- code --
    # searchpath for tools
-FDD:\Archive\development\fpc_stable_x64/bin/$FPCTARGET

    # it's doesn't work!
    -FDD:\Archive\development\fpc_stable_x64/binw64/ --- code ---

Then I run the bat-file as follows:

--- code ---
    set FPC_source={<fpc trunk root directory path>}     set FPC_binutils={<fpc trunk root directory path>}\bin\x86_64-win64     set FPC_stable_binutils={fpc_stable_x64 root directory path}\bin\x86_64-win64

    :: so it works!
    set binw64_path={fpc_stable_x64 root directory path}/binw64     set path=<bla-bla-bla>;%path%

    ...
    cd /d %FPC_source%
    make clean all install INSTALL_PREFIX=%FPC_source% PP=%FPC_stable_binutils%\ppcx64.exe DATA2INC=%FPC_source%\utils\data2inc.exe     ...
--- code ---

During compilation I get an error:

--- code ---
    ...
d:/Archive/development/fpc_stable_x64/bin/x86_64-win64/mv.exe -f x86_64/bin/x86_64-win64/pp.exe ppcx64.exe
    make[5]: Leaving directory
`d:/Archive/development/fpc_331_r44725_x64/compiler'     make echotime
    make[5]: Entering directory
`d:/Archive/development/fpc_331_r44725_x64/compiler'     process_begin: CreateProcess((null), echo Start now 19:52:42, ...) failed.
    make (e=2): Не удается найти указанный файл. <english translation: The system cannot find the file specified>
    make[5]: *** [echotime] Error 2
    make[5]: Leaving directory
`d:/Archive/development/fpc_331_r44725_x64/compiler'     make[4]: *** [next] Error 2
    make[4]: Leaving directory
`d:/Archive/development/fpc_331_r44725_x64/compiler'     make[3]: *** [ppc1.exe] Error 2
    make[3]: Leaving directory
`d:/Archive/development/fpc_331_r44725_x64/compiler'     make[2]: *** [cycle] Error 2
    make[2]: Leaving directory
`d:/Archive/development/fpc_331_r44725_x64/compiler'     make[1]: *** [compiler_cycle] Error 2
    make[1]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64'     make: *** [build-stamp.x86_64-win64] Error 2     ...
--- code ---

What am I doing wrong?  Can someone tell me a link to a detailed manual?

with best regards, Zoltanleo aka Док

Reply by email

Sven Barth
to leyba bronstain
leyba bronstain wrote 73 lines
Hi guys. I need your help. I try build trunk compiler x64 for windows. I was extract stable release fpc_x64 form lazarus-2.0.8-fpc-3.0.4-win64.exe installer and put it to separate folder fpc_stable_x64. Also I put into fpc_stable_x64 folder bingw64 folder and fixed the file fpc.cfg as follows: --- code --     # searchpath for tools -FDD:\Archive\development\fpc_stable_x64/bin/$FPCTARGET     # it's doesn't work!     -FDD:\Archive\development\fpc_stable_x64/binw64/ --- code --- Then I run the bat-file as follows: --- code ---     set FPC_source={<fpc trunk root directory path>}     set FPC_binutils={<fpc trunk root directory path>}\bin\x86_64-win64     set FPC_stable_binutils={fpc_stable_x64 root directory path}\bin\x86_64-win64     :: so it works!     set binw64_path={fpc_stable_x64 root directory path}/binw64     set path=<bla-bla-bla>;%path%     ...     cd /d %FPC_source%     make clean all install INSTALL_PREFIX=%FPC_source% PP=%FPC_stable_binutils%\ppcx64.exe DATA2INC=%FPC_source%\utils\data2inc.exe     ... --- code --- During compilation I get an error: --- code ---     ... d:/Archive/development/fpc_stable_x64/bin/x86_64-win64/mv.exe -f x86_64/bin/x86_64-win64/pp.exe ppcx64.exe     make[5]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64/compiler'     make echotime     make[5]: Entering directory `d:/Archive/development/fpc_331_r44725_x64/compiler'     process_begin: CreateProcess((null), echo Start now 19:52:42, ...) failed.     make (e=2): Не удается найти указанный файл. <english translation: The system cannot find the file specified>     make[5]: *** [echotime] Error 2     make[5]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64/compiler'     make[4]: *** [next] Error 2     make[4]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64/compiler'     make[3]: *** [ppc1.exe] Error 2     make[3]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64/compiler'     make[2]: *** [cycle] Error 2     make[2]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64/compiler'     make[1]: *** [compiler_cycle] Error 2     make[1]: Leaving directory `d:/Archive/development/fpc_331_r44725_x64'     make: *** [build-stamp.x86_64-win64] Error 2     ... --- code --- What am I doing wrong?  Can someone tell me a link to a detailed manual?

As I have written on the forum there seems to be some problem with "echo" as this is the line the makefile intends to execute:

echotime:
    @echo Start $(STARTTIME) now $(ENDTIME)

Would you please go to the compiler directory and manually execute "make echotime" to see whether this works in principle?

Regards,
Sven

Reply by email

leyba bronstain
to Sven Barth

30.04.2020 8:30, Sven Barth via lazarus пишет:

Show quoted text 11 lines
As I have written on the forum there seems to be some problem with "echo" as this is the line the makefile intends to execute: echotime:     @echo Start $(STARTTIME) now $(ENDTIME) Would you please go to the compiler directory and manually execute "make echotime" to see whether this works in principle? Regards, Sven

Hi Sven.

Thank U for te answer.

I tried using your advice. Here's what I got (the compiler revision number is specified in the paths)

d:\Archive\development\fpc_331_r45198>set path=<path to make.exe x64 file>;%path%

d:\Archive\development\fpc_331_r45198>@echo Start $(STARTTIME) now $(ENDTIME)
Start $(STARTTIME) now $(ENDTIME)

d:\Archive\development\fpc_331_r45198>make echotime make: *** No rule to make target `echotime'.  Stop.

with best regards, Zoltanleo aka Док

Reply by email

Sven Barth
to leyba bronstain

leyba bronstain via lazarus schrieb am Do.,
30. Apr. 2020, 23:22:

Show quoted text 30 lines
30.04.2020 8:30, Sven Barth via lazarus пишет: > As I have written on the forum there seems to be some problem with > "echo" as this is the line the makefile intends to execute: > > echotime: > @echo Start $(STARTTIME) now $(ENDTIME) > > Would you please go to the compiler directory and manually execute > "make echotime" to see whether this works in principle? > > Regards, > Sven Hi Sven. Thank U for te answer. I tried using your advice. Here's what I got (the compiler revision number is specified in the paths) d:\Archive\development\fpc_331_r45198>set path=<path to make.exe x64 file>;%path% d:\Archive\development\fpc_331_r45198>@echo Start $(STARTTIME) now $(ENDTIME) Start $(STARTTIME) now $(ENDTIME) d:\Archive\development\fpc_331_r45198>make echotime make: *** No rule to make target `echotime'. Stop.

You did read the part where I said "go to the compiler directory"? ;)

Regards,
Sven

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20200430/32e58f93/attachment-0001.html>

Reply by email

leyba bronstain
to Sven Barth

01.05.2020 0:25, Sven Barth via lazarus пишет:

Show quoted text 6 lines
You did read the part where I said "go to the compiler directory"? ;) Regards, Sven

Hi Sven.

In a previous post, I went to the root directory of the compiler trunk(d:\Archive\development\fpc_331_r45198) and called "make echotime". Perhaps I misinterpreted your words :)

OK. Now I went to the root directory of the stable version of the x64 compiler (d:\Archive\development\fpc_stable_x64\bin\x86_64-win64) and got the same error:

C:\Users\leyba>cd /d d:\Archive\development\fpc_stable_x64\bin\x86_64-win64

d:\Archive\development\fpc_stable_x64\bin\x86_64-win64>make echotime make: *** No rule to make target `echotime'.  Stop.

I'm sorry, again, something I misunderstood?

with best regards, Zoltanleo aka Док

Reply by email

Sven Barth
to leyba bronstain
leyba bronstain wrote 27 lines
01.05.2020 0:25, Sven Barth via lazarus пишет: > You did read the part where I said "go to the compiler directory"? ;) > > Regards, > Sven > > Hi Sven. In a previous post, I went to the root directory of the compiler trunk(d:\Archive\development\fpc_331_r45198) and called "make echotime". Perhaps I misinterpreted your words :) OK. Now I went to the root directory of the stable version of the x64 compiler (d:\Archive\development\fpc_stable_x64\bin\x86_64-win64) and got the same error: C:\Users\leyba>cd /d d:\Archive\development\fpc_stable_x64\bin\x86_64-win64 d:\Archive\development\fpc_stable_x64\bin\x86_64-win64>make echotime make: *** No rule to make target `echotime'.  Stop. I'm sorry, again, something I misunderstood?

I meant the literal "compiler" directory.

Regards,
Sven

Reply by email

leyba bronstain
to Sven Barth

01.05.2020 0:46, Sven Barth via lazarus пишет:

I meant the literal "compiler" directory. Regards, Sven

Directory d:\Archive\development\fpc_stable_x64\bin\x86_64-win64 is the compiler directory where fpc and ppcx4 are located.

Let's leave it until better times. Apparently I'm just an impassable dumbass :)

with best regards, Zoltanleo aka Док

Reply by email

Martin Frb
to leyba bronstain
leyba bronstain wrote 12 lines
01.05.2020 0:46, Sven Barth via lazarus пишет: > I meant the literal "compiler" directory. > > Regards, > Sven Directory d:\Archive\development\fpc_stable_x64\bin\x86_64-win64 is the compiler directory where fpc and ppcx4 are located. Let's leave it until better times. Apparently I'm just an impassable dumbass :)

in your svn checkout dir, is a sub-directory called /compiler It has the sources for the compiler.

And you should run that particular make command in that dir.

Reply by email

leyba bronstain
to Martin Frb

01.05.2020 1:45, Martin Frb via lazarus пишет:

in your svn checkout dir, is a sub-directory called /compiler It has the sources for the compiler. And you should run that particular make command in that dir.

OMG! I thank you for the detailed explanation. Forgive me my misunderstanding. I don't really distinguish the subtleties of English ¯\_(ツ)_/¯

So:

C:\Users\leyba>set
path=d:\Archive\development\fpc_stable_x64\bin\x86_64-win64;%path% C:\Users\leyba>cd /d d:\Archive\development\fpc_331_r45198\compiler d:\Archive\development\fpc_331_r45198\compiler>make echotime process_begin: CreateProcess((null), echo Start 02:10:01 now 02:10:01, ...) failed.
make (e=2): Не удается найти указанный файл. (eng: can't find the file specified////)
make: *** [echotime] Error 2

I start compiler building like this

make clean all install INSTALL_PREFIX=%FPC_source% PP=%FPC_stable_binutils%\ppcx64.exe DATA2INC=%FPC_source%\utils\data2inc.exe

Probably the build options should be different. I looked at the command line fpcupdeluxe. It applies the patch for Makefile (fpcpatch_all_makesearchpath_stable_3_0_4.patch)  and the command line options look something like this:

[2020-05-01 01:42:30.296 Info] FPCNativeInstaller (CleanModule: FPC): Execute: C:\fpcup\fpcbootstrap\make.exe. Params:
--jobs=1,FPC=C:\fpcup\fpcbootstrap\ppcx64.exe,--directory=C:\fpcup\fpcsrc,FPCMAKE=C:\fpcup\fpc\bin\x86_64-win64\fpcmake.exe,PPUMOVE=C:\fpcup\fpc\bin\x86_64-win64\ppumove.exe,FPCDIR=C:\fpcup\fpcsrc,PREFIX=C:\fpcup\fpc,INSTALL_PREFIX=C:\fpcup\fpc,UPXPROG=echo,COPYTREE=echo,CPU_SOURCE=x86_64,OS_SOURCE=win64,CPU_TARGET=x86_64,OS_TARGET=win64,distclean

I might experiment with command line options.

with best regards, Zoltanleo aka Док

Reply by email

Martin Frb
to leyba bronstain
leyba bronstain wrote 10 lines
I start compiler building like this make clean all install INSTALL_PREFIX=%FPC_source% PP=%FPC_stable_binutils%\ppcx64.exe DATA2INC=%FPC_source%\utils\data2inc.exe Probably the build options should be different. I looked at the command line fpcupdeluxe. It applies the patch for Makefile (fpcpatch_all_makesearchpath_stable_3_0_4.patch)  and the command line options look something like this:

I am not too much of an expert on this. And probably Sven (or others) will have more advice.

But when I build, I add the appropriate path from within the build svn https://svn.freepascal.org/svn/fpcbuild/trunk (or fixes_....) something like  (on windows)
PATH=<build_svn>\install\binw64;%PATH%;
or
PATH=<build_svn>\install\binw32;%PATH%;

No idea, if that is related to your problem.

Reply by email

Sven Barth
to leyba bronstain: 01.05.2020 1:45, Martin Frb via lazarus пишет: OMG! I thank you for the detailed…
leyba bronstain wrote 9 lines
01.05.2020 1:45, Martin Frb via lazarus пишет: > in your svn checkout dir, is a sub-directory called /compiler > It has the sources for the compiler. > > And you should run that particular make command in that dir. OMG! I thank you for the detailed explanation. Forgive me my misunderstanding. I don't really distinguish the subtleties of English ¯\_(ツ)_/¯

Sorry for being unclear here...

Show quoted text 30 lines
So: C:\Users\leyba>set path=d:\Archive\development\fpc_stable_x64\bin\x86_64-win64;%path% C:\Users\leyba>cd /d d:\Archive\development\fpc_331_r45198\compiler d:\Archive\development\fpc_331_r45198\compiler>make echotime process_begin: CreateProcess((null), echo Start 02:10:01 now 02:10:01, ...) failed. make (e=2): Не удается найти указанный файл. (eng: can't find the file specified////) make: *** [echotime] Error 2 I start compiler building like this make clean all install INSTALL_PREFIX=%FPC_source% PP=%FPC_stable_binutils%\ppcx64.exe DATA2INC=%FPC_source%\utils\data2inc.exe Probably the build options should be different. I looked at the command line fpcupdeluxe. It applies the patch for Makefile (fpcpatch_all_makesearchpath_stable_3_0_4.patch)  and the command line options look something like this: [2020-05-01 01:42:30.296 Info] FPCNativeInstaller (CleanModule: FPC): Execute: C:\fpcup\fpcbootstrap\make.exe. Params: --jobs=1,FPC=C:\fpcup\fpcbootstrap\ppcx64.exe,--directory=C:\fpcup\fpcsrc,FPCMAKE=C:\fpcup\fpc\bin\x86_64-win64\fpcmake.exe,PPUMOVE=C:\fpcup\fpc\bin\x86_64-win64\ppumove.exe,FPCDIR=C:\fpcup\fpcsrc,PREFIX=C:\fpcup\fpc,INSTALL_PREFIX=C:\fpcup\fpc,UPXPROG=echo,COPYTREE=echo,CPU_SOURCE=x86_64,OS_SOURCE=win64,CPU_TARGET=x86_64,OS_TARGET=win64,distclean I might experiment with command line options.

Can you please try to execute "make echotime" (in the "fpc_331_r45198\compiler" directory ;) ) without any changes to the PATH variable?

You also said that when compiling for i386 this worked correctly. Would you please "echo %PATH%" before executing "make" in the directory with the source for both variants (i386 and x86_64)?

Regards,
Sven

Reply by email

leyba bronstain
to Sven Barth

Hi Sven.

01.05.2020 17:10, Sven Barth via lazarus пишет:

Can you please try to execute "make echotime" (in the "fpc_331_r45198\compiler" directory ;) ) without any changes to the PATH variable?

C:\Users\leyba>cd /d d:\Archive\development\fpc_331_r45227_x64\compiler

d:\Archive\development\fpc_331_r45227_x64\compiler>make echotime "make" не является внутренней или внешней командой, исполняемой программой или пакетным файлом. (ENG: 'make' is not recognized as an internal or external command, operable program or batch file)

Show quoted text 6 lines
You also said that when compiling for i386 this worked correctly. Would you please "echo %PATH%" before executing "make" in the directory with the source for both variants (i386 and x86_64)? Regards, Sven

for x32

C:\Users\leyba>echo %path%
c:\;d:\;C:\Program
Files\Pandoc\;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;c:\Program Files\TortoiseSVN\bin;c:\Windows\System32\;c:\Program Files\Git\bin\

C:\Users\leyba>cd /d d:\Archive\development\fpc_331_r45227_x32\compiler

d:\Archive\development\fpc_331_r45227_x32\compiler>make echotime "make" не является внутренней или внешней командой, исполняемой программой или пакетным файлом. (ENG: 'make' is not recognized as an internal or external command, operable program or batch file)

d:\Archive\development\fpc_331_r45227_x32\compiler>path=d:\Archive\development\fpc_stable_x32\bin\i386-win32;%path% d:\Archive\development\fpc_331_r45227_x32\compiler>echo %path% d:\Archive\development\fpc_stable_x32\bin\i386-win32;c:\;d:\;C:\Program Files\Pandoc\;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;c:\Program Files\TortoiseSVN\bin;c:\Windows\System32\;c:\Program Files\Git\bin\

d:\Archive\development\fpc_331_r45227_x32\compiler>make echotime Start 22:52:28 now 22:52:28

----------------------------------------------------------------

for x64
C:\Users\leyba>echo %path%
c:\;d:\;C:\Program
Files\Pandoc\;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;c:\Program Files\TortoiseSVN\bin;c:\Windows\System32\;c:\Program Files\Git\bin\

C:\Users\leyba>cd /d d:\Archive\development\fpc_331_r45227_x64\compiler

d:\Archive\development\fpc_331_r45227_x64\compiler>make echotime "make" не является внутренней или внешней командой, исполняемой программой или пакетным файлом.

d:\Archive\development\fpc_331_r45227_x64\compiler>path=d:\Archive\development\fpc_stable_x64\bin\x86_64-win64;%path%

d:\Archive\development\fpc_331_r45227_x64\compiler>echo %path% d:\Archive\development\fpc_stable_x64\bin\x86_64-win64;c:\;d:\;C:\Program Files\Pandoc\;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;c:\Program Files\TortoiseSVN\bin;c:\Windows\System32\;c:\Program Files\Git\bin\

d:\Archive\development\fpc_331_r45227_x64\compiler>make echotime process_begin: CreateProcess((null), echo Start 22:55:53 now 22:55:53, ...) failed.
make (e=2): Не удается найти указанный файл. make: *** [echotime] Error 2

with best regards, Zoltanleo aka Док

Reply by email

Sven Barth
to leyba bronstain
leyba bronstain wrote 8 lines
for x32 d:\Archive\development\fpc_331_r45227_x32\compiler>path=d:\Archive\development\fpc_stable_x32\bin\i386-win32;%path% d:\Archive\development\fpc_331_r45227_x32\compiler>echo %path% d:\Archive\development\fpc_stable_x32\bin\i386-win32;c:\;d:\;C:\Program Files\Pandoc\;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;c:\Program Files\TortoiseSVN\bin;c:\Windows\System32\;c:\Program Files\Git\bin\

[snip]

Show quoted text 9 lines
for x64 d:\Archive\development\fpc_331_r45227_x64\compiler>path=d:\Archive\development\fpc_stable_x64\bin\x86_64-win64;%path% d:\Archive\development\fpc_331_r45227_x64\compiler>echo %path% d:\Archive\development\fpc_stable_x64\bin\x86_64-win64;c:\;d:\;C:\Program Files\Pandoc\;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;c:\Program Files\TortoiseSVN\bin;c:\Windows\System32\;c:\Program Files\Git\bin\

Would you please provide a directory listing (using "dir" should be enough) of the fpc_stable_x32\bin\i386-win32 and
fpc_stable_x64\bin\x86_64-win64 directories? I have the feeling that something in there leads to this difference as that is the only thing you add to PATH.

Regards,
Sven

Reply by email

leyba bronstain
to Sven Barth

03.05.2020 0:05, Sven Barth пишет:

Show quoted text 8 lines
Would you please provide a directory listing (using "dir" should be enough) of the fpc_stable_x32\bin\i386-win32 and fpc_stable_x64\bin\x86_64-win64 directories? I have the feeling that something in there leads to this difference as that is the only thing you add to PATH. Regards, Sven

Hi Sven.

I have attached the result in two files, so that it is convenient for you to compare.

with best regards, Zoltanleo aka Док -------------- next part -------------- Том в устройстве D не имеет метки. Серийный номер тома: E862-4779 Содержимое папки d:\Archive\development\fpc_stable_x32\bin\i386-win32 20.04.2020 01:42 <DIR> . 20.04.2020 01:42 <DIR> .. 07.04.2012 14:39 599 566 ar.exe 07.04.2012 14:39 1 028 110 as.exe 06.10.2017 19:35 199 680 bin2obj.exe 06.10.2017 19:33 453 632 chmcmd.exe 06.10.2017 19:33 254 976 chmls.exe 30.05.2005 21:05 6 144 cmp.exe 30.05.2005 21:05 22 528 cp.exe 30.05.2005 21:05 91 136 cpp.exe 16.05.2005 20:37 426 cvsco.tdf 22.01.2007 06:03 672 cvsdiff.tdf 16.05.2005 20:37 323 cvsup.tdf 06.10.2017 19:35 46 080 data2inc.exe 06.10.2017 19:35 98 816 delp.exe 30.05.2005 21:05 32 768 diff.exe 09.03.2011 12:17 689 664 dlltool.exe 16.05.2005 20:37 4 515 fp.ans 20.04.2020 01:41 756 fp.cfg 06.10.2017 19:36 9 794 048 fp.exe 20.04.2020 01:41 1 090 fp.ini 27.05.2006 18:58 4 286 fp32.ico 20.04.2020 11:16 8 185 fpc.cfg 06.10.2017 19:32 95 744 fpc.exe 06.10.2017 19:35 284 160 fpcmake.exe 06.10.2017 19:35 221 184 fpcmkcfg.exe 06.10.2017 19:35 327 168 fpcres.exe 06.10.2017 19:35 184 832 fpcsubst.exe 06.10.2017 19:35 838 656 fpdoc.exe 06.10.2017 19:35 181 248 fpmc.exe 06.10.2017 19:35 891 392 fppkg.exe 06.10.2017 19:35 186 880 fprcp.exe 30.05.2005 21:05 68 608 gcc.exe 30.05.2005 21:05 19 456 gdate.exe 30.01.2011 21:43 3 598 848 gdb.exe 30.05.2005 21:05 4 608 gecho.exe 30.05.2005 21:05 18 944 ginstall.exe 21.05.2009 11:36 388 ginstall.exe.manifest 30.05.2005 21:05 13 824 gmkdir.exe 07.06.2005 11:47 660 gplprog.pt 07.06.2005 11:47 694 gplunit.pt 30.05.2005 21:05 64 000 grep.exe 16.05.2005 20:37 732 grep.tdf 06.10.2017 19:35 307 200 h2pas.exe 06.10.2017 19:35 36 864 h2paspp.exe 06.10.2017 19:35 200 704 instantfpc.exe 07.04.2012 14:39 838 670 ld.exe 30.01.2011 21:43 165 513 libexpat-1.dll 15.08.2012 20:36 188 942 make.exe 06.10.2017 19:35 470 016 makeskel.exe 30.05.2005 21:05 31 744 mv.exe 07.04.2012 14:39 586 766 nm.exe 07.04.2012 14:39 726 030 objcopy.exe 07.04.2012 14:39 1 092 622 objdump.exe 06.10.2017 19:35 413 184 pas2jni.exe 30.05.2005 21:05 28 160 patch.exe 21.01.2010 18:23 388 patch.exe.manifest 06.10.2017 19:35 120 832 plex.exe 06.10.2017 19:35 47 616 postw32.exe 06.10.2017 19:33 2 387 968 ppc386.exe 06.10.2017 19:46 2 281 472 ppcrossx64.exe 06.10.2017 19:35 40 960 ppdep.exe 06.10.2017 19:32 353 280 ppudump.exe 06.10.2017 19:32 95 232 ppufiles.exe 06.10.2017 19:32 109 568 ppumove.exe 16.05.2005 20:37 63 program.pt 06.10.2017 19:35 192 512 ptop.exe 30.05.2005 21:05 2 560 pwd.exe 06.10.2017 19:35 136 192 pyacc.exe 30.05.2005 21:05 30 720 rm.exe 06.10.2017 19:35 89 600 rmcvsdir.exe 06.10.2017 19:35 345 600 rstconv.exe 07.04.2012 14:39 726 030 strip.exe 16.05.2005 20:37 1 059 tpgrep.tdf 16.05.2005 20:37 96 unit.pt 06.10.2017 19:35 371 200 unitdiff.exe 30.05.2005 21:05 41 472 unzip.exe 01.10.2011 23:34 662 542 windres.exe 30.05.2005 21:05 141 200 windres.h 09.03.2014 12:43 828 430 x86_64-win64-ar.exe 09.03.2014 12:43 1 399 822 x86_64-win64-as.exe 09.03.2014 12:43 1 179 662 x86_64-win64-ld.exe 09.03.2014 12:43 815 630 x86_64-win64-nm.exe 09.03.2014 12:43 965 646 x86_64-win64-objcopy.exe 09.03.2014 12:43 1 469 966 x86_64-win64-objdump.exe 09.03.2014 12:43 965 646 x86_64-win64-strip.exe 09.03.2014 12:43 927 246 x86_64-win64-windres.exe 25.02.2009 21:36 1 345 yylex.cod 25.02.2009 21:36 4 334 yyparse.cod 30.05.2005 21:05 32 256 zip.exe 88 файлов 42 193 987 байт 2 папок 122 994 081 792 байт свободно -------------- next part -------------- Том в устройстве D не имеет метки. Серийный номер тома: E862-4779 Содержимое папки d:\Archive\development\fpc_stable_x64\bin\x86_64-win64 20.04.2020 11:18 <DIR> . 20.04.2020 11:18 <DIR> .. 06.01.2011 18:22 2 898 013 ar.exe 06.01.2011 18:22 3 635 109 as.exe 11.04.2020 20:45 272 384 bin2obj.exe 11.04.2020 20:44 629 760 chmcmd.exe 11.04.2020 20:44 349 696 chmls.exe 11.04.2020 20:45 875 008 cldrparser.exe 04.11.2010 17:56 6 144 cmp.exe 30.10.2006 11:39 22 528 cp.exe 11.04.2020 19:43 91 136 cpp.exe 11.04.2020 20:45 59 392 data2inc.exe 11.04.2020 20:45 128 000 delp.exe 30.10.2006 11:39 32 768 diff.exe 30.04.2020 22:39 8 200 fpc.cfg 11.04.2020 20:45 123 904 fpc.exe 11.04.2020 20:45 355 840 fpcjres.exe 11.04.2020 20:45 675 328 fpclasschart.exe 11.04.2020 20:45 376 832 fpcmake.exe 11.04.2020 20:45 305 664 fpcmkcfg.exe 11.04.2020 20:45 450 048 fpcres.exe 11.04.2020 20:45 256 512 fpcsubst.exe 11.04.2020 20:45 1 202 688 fpdoc.exe 11.04.2020 20:45 252 416 fpmc.exe 11.04.2020 20:45 1 154 048 fppkg.exe 11.04.2020 20:45 272 384 fprcp.exe 11.04.2020 19:43 68 608 gcc.exe 30.10.2006 11:39 19 456 gdate.exe 29.11.2019 05:45 7 750 144 gdb.exe 30.10.2006 11:39 4 608 gecho.exe 30.10.2006 11:39 18 944 ginstall.exe 06.11.2010 15:03 388 ginstall.exe.manifest 30.10.2006 11:39 13 824 gmkdir.exe 11.04.2020 20:45 389 632 h2pas.exe 11.04.2020 20:45 50 176 h2paspp.exe 11.04.2020 21:07 599 566 i386-win32-ar.exe 11.04.2020 21:07 1 028 110 i386-win32-as.exe 11.04.2020 21:07 689 664 i386-win32-dlltool.exe 11.04.2020 21:07 3 598 848 i386-win32-gdb.exe 11.04.2020 21:07 838 670 i386-win32-ld.exe 11.04.2020 21:07 586 766 i386-win32-nm.exe 11.04.2020 21:07 726 030 i386-win32-objcopy.exe 11.04.2020 21:07 1 092 622 i386-win32-objdump.exe 11.04.2020 21:07 726 030 i386-win32-strip.exe 11.04.2020 21:07 662 542 i386-win32-windres.exe 11.04.2020 20:45 430 080 importtl.exe 11.04.2020 20:45 281 600 instantfpc.exe 30.04.2019 19:40 135 168 LazGDeBugControl.exe 06.01.2011 18:22 3 923 605 ld.exe 11.04.2020 19:43 782 336 make.exe 11.04.2020 20:45 668 672 makeskel.exe 11.04.2020 20:45 2 248 makeskel.rsj 11.04.2020 20:45 53 248 mkarmins.exe 11.04.2020 20:45 62 464 mkinsadd.exe 11.04.2020 20:45 57 344 mkx86ins.exe 30.10.2006 11:39 31 744 mv.exe 06.01.2011 18:22 4 014 087 objdump.exe 11.04.2020 20:45 526 336 pas2fpm.exe 11.04.2020 20:45 568 832 pas2jni.exe 11.04.2020 20:45 529 920 pas2ut.exe 11.04.2020 20:45 153 088 plex.exe 11.04.2020 20:45 57 344 postw32.exe 11.04.2020 21:05 2 387 968 ppc386.exe 11.04.2020 20:45 2 829 824 ppcx64.exe 11.04.2020 20:45 54 784 ppdep.exe 11.04.2020 20:45 459 264 ppudump.exe 11.04.2020 20:45 122 880 ppufiles.exe 11.04.2020 20:45 141 312 ppumove.exe 11.04.2020 20:45 268 288 ptop.exe 11.04.2020 20:45 789 ptop.rsj 30.10.2006 11:39 2 560 pwd.exe 11.04.2020 20:45 170 496 pyacc.exe 30.10.2006 11:39 30 720 rm.exe 11.04.2020 20:45 116 224 rmcvsdir.exe 11.04.2020 20:45 68 608 rmwait.exe 11.04.2020 20:45 461 824 rstconv.exe 06.01.2011 18:22 3 441 283 strip.exe 11.04.2020 20:45 343 552 unihelper.exe 11.04.2020 20:45 527 872 unitdiff.exe 11.04.2020 19:43 662 542 windres.exe 11.04.2020 19:43 141 200 windres.h 25.02.2009 21:36 1 345 yylex.cod 25.02.2009 21:36 4 334 yyparse.cod 81 файлов 57 814 215 байт 2 папок 122 993 942 528 байт свободно

Reply by email

leyba bronstain
to Sven Barth: [snip] Would you please provide a directory listing (using "dir" should be enough) of the…

03.05.2020 0:05, Sven Barth пишет:

Show quoted text 8 lines
Would you please provide a directory listing (using "dir" should be enough) of the fpc_stable_x32\bin\i386-win32 and fpc_stable_x64\bin\x86_64-win64 directories? I have the feeling that something in there leads to this difference as that is the only thing you add to PATH. Regards, Sven

Do I understand correctly that the ppcx64 files and other files of the stable release of the x64 compiler are built from the stable release of the x32 compiler and other utilities of the binw64 folder?

Maybe you will tell me the right way, how can I build stable binutils x64 using stable binutils x32?

with best regards, Zoltanleo aka Док

Reply by email

Sven Barth
to leyba bronstain: 03.05.2020 0:05, Sven Barth пишет: Hi Sven. I have attached the result in two files,…
leyba bronstain wrote 15 lines
03.05.2020 0:05, Sven Barth пишет: > Would you please provide a directory listing (using "dir" should be > enough) of the fpc_stable_x32\bin\i386-win32 and > fpc_stable_x64\bin\x86_64-win64 directories? I have the feeling that > something in there leads to this difference as that is the only thing > you add to PATH. > > Regards, > Sven Hi Sven. I have attached the result in two files, so that it is convenient for you to compare.

From what I can see you should be able to simply use the fpc_stable_x32\bin\i386-win32 directory for building the 64-bit trunk version as it contains a ppcrossx64.exe and the binutils (though they aren't used by FPC on Windows anyway).

Regards,
Sven

Reply by email

Sven Barth
to leyba bronstain: 03.05.2020 0:05, Sven Barth пишет: Do I understand correctly that the ppcx64 files…
leyba bronstain wrote 16 lines
03.05.2020 0:05, Sven Barth пишет: > Would you please provide a directory listing (using "dir" should be > enough) of the fpc_stable_x32\bin\i386-win32 and > fpc_stable_x64\bin\x86_64-win64 directories? I have the feeling that > something in there leads to this difference as that is the only thing > you add to PATH. > > Regards, > Sven Do I understand correctly that the ppcx64 files and other files of the stable release of the x64 compiler are built from the stable release of the x32 compiler and other utilities of the binw64 folder? Maybe you will tell me the right way, how can I build stable binutils x64 using stable binutils x32?

FPC only provides a 32-bit -> 64-bit cross compiler as installer and that is indeed made using the 32-bit compiler. Lazarus however ships with a native 64-bit compiler.

I don't know how you created your fpc_stable_x64\bin\x86_64-win64 directory, but maybe that some utilities have different versions than the ones in the fpc_stable_x32\bin\i386-win32 directory might explain the problems you experience.

Regards,
Sven

Reply by email

Leyba Bronstain
to Sven Barth

03.05.2020 19:23, Sven Barth пишет:

Show quoted text 11 lines
FPC only provides a 32-bit -> 64-bit cross compiler as installer and that is indeed made using the 32-bit compiler. Lazarus however ships with a native 64-bit compiler. I don't know how you created your fpc_stable_x64\bin\x86_64-win64 directory, but maybe that some utilities have different versions than the ones in the fpc_stable_x32\bin\i386-win32 directory might explain the problems you experience. Regards, Sven

Hi Sven.

I tried to get a ready-made stable version of fpc 3.0.4 x64 in different ways (this could be the Lazarus 2.0.8 installer or fpcupdeluxe). This was not a success.

After your assumptions, I decided to use only the compiler sources from the standard x32 package and the cross-compilation package. As a result, I followed several steps and managed to get a positive result. I have done the following:

1. I ran fpc-3.0.4.i386-win32.exe and
fpc-3.0.4.i386-win32.cross.android.exe and installed the compiler sources and binutils

2. I executed the following commands in cmd:

set path=d:\Archive\development\fpc_stable\3.0.4\bin\i386-win32;%path%

make install OS_TARGET=win64 CPU_TARGET=x86_64 CPU_SOURCE=x86_64 OS_SOURCE=win64 INSTALL_PREFIX=d:\Archive\development\fpc_trunk_x64 PP=d:\Archive\development\fpc_stable\3.0.4\bin\i386-win32\ppcrossx64.exe DATA2INC=d:\Archive\development\fpc_trunk_x64\utils\data2inc.exe

fpcmkcfg -d basepath=d:\Archive\development\fpc_trunk_x64 -o .\bin\x86_64-win64\fpc.cfg

replace d:\Archive\development\fpc_stable\3.0.4\binw64\*.* d:\Archive\development\fpc_trunk_x64\bin\x86_64-win64 /a

3. Congratulation! Now I have a live compiler trunk revision. :)

Do I used the command line switches for the make command correctly? Tell me pls...

with best regards, Zoltanleo aka Док -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20200504/297da2b2/attachment.html>

Reply by email