Sign in Join

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

Mailing lists / lazarus / 2015-02

while make lazarus x64, get i386 error

24 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

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

FreeMan

while lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt If ppc386 not in path, I get this error. ppcx64 is there, make fpc i386 then run again lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt IDE maked

Makefile:2332: warning: overriding commands for target `.' Makefile:2330: warning: ignoring old commands for target `.' Free Pascal Compiler version 3.1.1 [2015/02/22] for x86_64 Copyright (c) 1993-2015 by Florian Klaempfl and others (1002) Target OS: Darwin for x86_64
(3104) Compiling fcllaz.pas
(3104) Compiling registerfcl.pas
(3104) Compiling lazaruspackageintf.pas
(9009) Assembling lazaruspackageintf
/opt/lazarus/packager/registration/registerfcl.pas(45,22) Fatal: (10022) Can't find unit process used by RegisterFCL
Fatal: (1018) Compilation aborted
make[1]: *** [fcllaz.ppu] Error 1
make: *** [registration] Error 2

Reply by email

Mattias Gaertner
to FreeMan
Show quoted text 19 lines
while lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt If ppc386 not in path, I get this error. ppcx64 is there, make fpc i386 then run again lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt IDE maked Makefile:2332: warning: overriding commands for target `.' Makefile:2330: warning: ignoring old commands for target `.' Free Pascal Compiler version 3.1.1 [2015/02/22] for x86_64 Copyright (c) 1993-2015 by Florian Klaempfl and others (1002) Target OS: Darwin for x86_64 (3104) Compiling fcllaz.pas (3104) Compiling registerfcl.pas (3104) Compiling lazaruspackageintf.pas (9009) Assembling lazaruspackageintf /opt/lazarus/packager/registration/registerfcl.pas(45,22) Fatal: (10022) Can't find unit process used by RegisterFCL Fatal: (1018) Compilation aborted make[1]: *** [fcllaz.ppu] Error 1 make: *** [registration] Error 2

Where is the x86_64 process.ppu and have you added that to your /etc/fpc.cfg?

Mattias

Reply by email

zeljko
to Mattias Gaertner
Mattias Gaertner wrote 25 lines
On Sun, 22 Feb 2015 19:23:27 +0200 FreeMan wrote: > while lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt > If ppc386 not in path, I get this error. ppcx64 is there, make fpc i386 > then run again lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin > LCL_PLATFORM=qt IDE maked > > Makefile:2332: warning: overriding commands for target `.' > Makefile:2330: warning: ignoring old commands for target `.' > Free Pascal Compiler version 3.1.1 [2015/02/22] for x86_64 > Copyright (c) 1993-2015 by Florian Klaempfl and others > (1002) Target OS: Darwin for x86_64 > (3104) Compiling fcllaz.pas > (3104) Compiling registerfcl.pas > (3104) Compiling lazaruspackageintf.pas > (9009) Assembling lazaruspackageintf > /opt/lazarus/packager/registration/registerfcl.pas(45,22) Fatal: (10022) > Can't find unit process used by RegisterFCL > Fatal: (1018) Compilation aborted > make[1]: *** [fcllaz.ppu] Error 1 > make: *** [registration] Error 2 Where is the x86_64 process.ppu and have you added that to your /etc/fpc.cfg?

It is there where it should be. Such thing happens on osx 64bit only when lazarus is built from IDE and "Update revision.inc" is checked. Tested with CPU_TARGET=x86_64 OS_TARGET=darwin, and also setted up compiler in laz config to ppcx64 and without CPU_TARGET and OS_TARGET. From terminal it builds ok.
make bigide CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt

z.

Reply by email

Mattias Gaertner
to zeljko
Show quoted text 29 lines
On 02/22/2015 07:44 PM, Mattias Gaertner wrote: > On Sun, 22 Feb 2015 19:23:27 +0200 > FreeMan wrote: > >> while lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt >> If ppc386 not in path, I get this error. ppcx64 is there, make fpc i386 >> then run again lazarus make CPU_TARGET=x86_64 OS_TARGET=darwin >> LCL_PLATFORM=qt IDE maked >> >> Makefile:2332: warning: overriding commands for target `.' >> Makefile:2330: warning: ignoring old commands for target `.' >> Free Pascal Compiler version 3.1.1 [2015/02/22] for x86_64 >> Copyright (c) 1993-2015 by Florian Klaempfl and others >> (1002) Target OS: Darwin for x86_64 >> (3104) Compiling fcllaz.pas >> (3104) Compiling registerfcl.pas >> (3104) Compiling lazaruspackageintf.pas >> (9009) Assembling lazaruspackageintf >> /opt/lazarus/packager/registration/registerfcl.pas(45,22) Fatal: (10022) >> Can't find unit process used by RegisterFCL >> Fatal: (1018) Compilation aborted >> make[1]: *** [fcllaz.ppu] Error 1 >> make: *** [registration] Error 2 > > Where is the x86_64 process.ppu and have you added that to > your /etc/fpc.cfg? It is there where it should be. Such thing happens on osx 64bit only when lazarus is built from IDE and "Update revision.inc" is checked.

The above is a compiler error.
If "Update revision.inc" makes a difference for compiling fcl.lpk, that would be voodoo.

Tested with CPU_TARGET=x86_64 OS_TARGET=darwin, and also setted up compiler in laz config to ppcx64 and without CPU_TARGET and OS_TARGET. From terminal it builds ok. make bigide CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt

Please click on Messages / About / About compiling package FCL to find out the fpc parameters.
Compare that with the parameters used by "make". Do you see a difference?

Mattias

Reply by email

Juha Manninen
to Mattias Gaertner

I installed a 64 bit compiler on Windows using FPCUP and set it to path. I set it to Lazarus settings and tried to build clean. The IDE first complained about compiler not supporting i386 and then the build failed.
I had to do "make clean all" at cmd line first. After that I could build from IDE, too.
It is a bug but a minor one. Such changes do not happen often.

Juha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20150223/4c048b92/attachment.html>

Reply by email

Mattias Gaertner
to Juha Manninen
I installed a 64 bit compiler on Windows using FPCUP and set it to path.

What means "set it to path"?
Are now both 32bit and 64bit version in the PATH or only the 64bit?

And after doing that, you restarted the IDE, right?

Show quoted text 6 lines
I set it to Lazarus settings and tried to build clean. The IDE first complained about compiler not supporting i386 and then the build failed. I had to do "make clean all" at cmd line first. After that I could build from IDE, too. It is a bug but a minor one. Such changes do not happen often.

Mattias

Reply by email

Mattias Gaertner
to zeljko: It is there where it should be. Such thing happens on osx 64bit only when lazarus is…
Show quoted text 10 lines
[...] >> /opt/lazarus/packager/registration/registerfcl.pas(45,22) Fatal: (10022) >> Can't find unit process used by RegisterFCL >> Fatal: (1018) Compilation aborted >> make[1]: *** [fcllaz.ppu] Error 1 >> make: *** [registration] Error 2 > Where is the x86_64 process.ppu and have you added that to > your /etc/fpc.cfg? It is there where it should be.

If there is a process.ppu, then the IDE should have changed the message and added the path to the ppu.
The above is the raw output from "make".

FreeMan, in the Messages window, you should see a different line "Can't find unit process used". Do you see the path to the process.ppu?

Mattias

Reply by email

Juha Manninen
to Mattias Gaertner: On Mon, 23 Feb 2015 11:59:15 +0200 What means "set it to path"? Are now both 32bit and…
Mattias Gaertner wrote
What means "set it to path"? Are now both 32bit and 64bit version in the PATH or only the 64bit?

Windows PATH. When I type "fpc" on cmd line, it starts the new 3.0.1 64-bit compiler.
It is the only fpc in PATH.

And after doing that, you restarted the IDE, right?

Yes, actually many times.
I can do more tests later. I have FPC 2.6.4 installed and it works with Lazarus when I set it in environment options. I used to have a 32-bit FPC 2.7.1 and I could switch between 2.6.4 and 2.7.1 inside the IDE and rebuild. It worked beautifully. Now the 32-bit - 64-bit difference broke it a little.

Juha

Reply by email

Mattias Gaertner
to Juha Manninen
Show quoted text 8 lines
On Mon, Feb 23, 2015 at 12:10 PM, Mattias Gaertner wrote: > What means "set it to path"? > Are now both 32bit and 64bit version in the PATH or only the 64bit? Windows PATH. When I type "fpc" on cmd line, it starts the new 3.0.1 64-bit compiler. It is the only fpc in PATH.

ok.
You know, that you don't need to change the PATH to switch the compiler in the IDE, don't you?
And having both in the PATH allows fpc.exe to find both.

AFAIK under Windows you should built the IDE only 32bit.

> And after doing that, you restarted the IDE, right? Yes

The IDE was still 32bit after this, right?

How was the IDE built? IDE, lazbuild or "make"?

Mattias

Reply by email

Juha Manninen
to Mattias Gaertner
Mattias Gaertner wrote
ok. You know, that you don't need to change the PATH to switch the compiler in the IDE, don't you? And having both in the PATH allows fpc.exe to find both.

Switching in the IDE worked well with two 32-bit compilers. Not any more, based on this one experience. I wil test more later.

AFAIK under Windows you should built the IDE only 32bit.

Is this still a valid issue? I remember there was a bug but I though it got fixed in FPC 3. No sure...

The IDE was still 32bit after this, right? How was the IDE built? IDE, lazbuild or "make"?

Yes, that made the difference. It was built from the IDE itself, "Debug IDE" profile.

Juha

Reply by email

Mattias Gaertner
to Juha Manninen
Show quoted text 8 lines
On Mon, Feb 23, 2015 at 12:50 PM, Mattias Gaertner wrote: > AFAIK under Windows you should built the IDE only 32bit. What error should I see with a 64-bit IDE? So far it works very well. Lazarus version info copied from About dialog: Lazarus 1.5 r47418 FPC 3.0.1 x86_64-win64-win32/win64 So it really is a 64-bit version, isn't it.

Good.

Mattias

Reply by email

Giuliano Colla
to Mattias Gaertner: On Mon, 23 Feb 2015 12:33:24 +0200 ok. You know, that you don't need to change the PATH…

Il 23/02/2015 11:50, Mattias Gaertner ha scritto:

Show quoted text 24 lines
On Mon, 23 Feb 2015 12:33:24 +0200 Juha Manninen wrote: > On Mon, Feb 23, 2015 at 12:10 PM, Mattias Gaertner > wrote: >> What means "set it to path"? >> Are now both 32bit and 64bit version in the PATH or only the 64bit? > Windows PATH. When I type "fpc" on cmd line, it starts the new 3.0.1 > 64-bit compiler. > It is the only fpc in PATH. ok. You know, that you don't need to change the PATH to switch the compiler in the IDE, don't you? And having both in the PATH allows fpc.exe to find both. AFAIK under Windows you should built the IDE only 32bit. >> And after doing that, you restarted the IDE, right? > Yes The IDE was still 32bit after this, right? How was the IDE built? IDE, lazbuild or "make"?

Maybe it's completely unrelated, but just in case.

I made some quick test when checking your fix for "Clear all". At first glance, in case of a target directory which is neither the Lazarus tree nor the Primary Config Path set by pcp (as is the case of cross-compiling, I believe), it seems to me that in a Build from IDE: a) the target directory is not cleared
b) the target directory contains only "units", while "lib" (i.e. packages") defaults to either Lazarus tree or pcp=xxx.

I didn't check more accurately, because I'm not familiar with cross-compiling issues.

I'm completely off track, and this a different issue, or it's worth to investigate a bit deeper?

Giuliano

Reply by email

FreeMan
to Mattias Gaertner: On Mon, 23 Feb 2015 08:21:23 +0100 If there is a process.ppu, then the IDE should have…

Sorry I been late :(
*-) /freepascal/3.1.1/packages/fpmkunit/units_bs/i386-darwin this folder has many ppu and o files. is there process.ppu too.

*-)/freepascal/3.1.1/packages/fcl-process/units/x86_64-darwin/process.ppu *-)/Volumes/ram_disk/opt/freepascal/3.1.1/lib/fpc/3.1.1/units/x86_64-darwin/fcl-process/process.ppu

I'll lookin for i386-darwin and found this folders /freepascal/3.1.1/compiler/i386/units/i386-darwin
/freepascal/3.1.1/packages/fpmkunit/units_bs/i386-darwin /freepascal/3.1.1/rtl/units/i386-darwin
/freepascal/3.1.1/utils/fpcm/units/i386-darwin
and this file
/freepascal/3.1.1/rtl/darwin/fpcmade.i386-darwin

this my command line
make -s clean all install
INSTALL_PREFIX=/Volumes/ram_disk/opt/freepascal/3.1.1 CPU_TARGET=x86_64 definitelyI'm sure that folder not there before run make.

Mattias Gaertner wrote 9 lines
If there is a process.ppu, then the IDE should have changed the message and added the path to the ppu. The above is the raw output from "make". FreeMan, in the Messages window, you should see a different line "Can't find unit process used". Do you see the path to the process.ppu? Mattias

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20150224/727ad87c/attachment-0001.html>

Reply by email

FreeMan
to FreeMan
FreeMan wrote 8 lines
I'll lookin for i386-darwin and found this folders /freepascal/3.1.1/compiler/i386/units/i386-darwin /freepascal/3.1.1/packages/fpmkunit/units_bs/i386-darwin /freepascal/3.1.1/rtl/units/i386-darwin /freepascal/3.1.1/utils/fpcm/units/i386-darwin and this file /freepascal/3.1.1/rtl/darwin/fpcmade.i386-darwin

when I remove this folders then make lazarus and get this result (I remove a few same lines)
make: -iVSPTPSOTO: Command not found
make[1]: -iVSPTPSOTO: Command not found
make[1]: -iVSPTPSOTO: Command not found
make[1]: -iVSPTPSOTO: Command not found
make[2]: -iVSPTPSOTO: Command not found
make[3]: -iVSPTPSOTO: Command not found
make[2]: -iVSPTPSOTO: Command not found
make[3]: -iVSPTPSOTO: Command not found
..........
make[1]: -iVSPTPSOTO: Command not found
Makefile:2332: warning: overriding commands for target `.' Makefile:2330: warning: ignoring old commands for target `.' make[1]: -iVSPTPSOTO: Command not found
make[1]: -iVSPTPSOTO: Command not found
make[1]: Tdarwin: No such file or directory
make[1]: -iVSPTPSOTO: Command not found
make[1]: Tdarwin: No such file or directory
.........
make[1]: -iVSPTPSOTO: Command not found
make[2]: -iVSPTPSOTO: Command not found
make[2]: *** No rule to make target `svn2revisioninc'. Stop. make[1]: *** [revisioninc] Error 2
make: *** [ide] Error 2

I have to compile fpc i386 and x64 then make x64 lazarus lazarus IDE is i386 or x64 ?

Reply by email

Mattias Gaertner
to FreeMan: Sorry I been late :( *-) /freepascal/3.1.1/packages/fpmkunit/units_bs/i386-darwin this…
Sorry I been late :( *-) /freepascal/3.1.1/packages/fpmkunit/units_bs/i386-darwin this folder has many ppu and o files. is there process.ppu too.

Building FPC yourself normally contains two steps: "make all" and "make install". The "all" compiles all ppu files, putting them across the source directories. The "install" copies the files nicely to one directory with one level of sub directories. Typically this is /usr/lib/fpc/$fpcversion/units/$fpctarget/*.

The later structure is used by the paths in /etc/fpc.cfg.

*-)/freepascal/3.1.1/packages/fcl-process/units/x86_64-darwin/process.ppu *-)/Volumes/ram_disk/opt/freepascal/3.1.1/lib/fpc/3.1.1/units/x86_64-darwin/fcl-process/process.ppu

You combined FPC sources (/Volumes/ram_disk/opt/freepascal/3.1.1) with the FPC installation (/Volumes/ram_disk/opt/freepascal/3.1.1). Although this is possible, it makes it harder to spot misconfigurations, so it is not recommended.
If you are not an expert, do what all others do: Use different directories. For example

make distclean all install INSTALL_PREFIX=/Volumes/ram_disk/ CPU_TARGET=x86_64

This creates the files under
/Volumes/ram_disk/lib/fpc/3.1.1/units/x86_64-darwin

Don't forget to remove /Volumes/ram_disk/opt/freepascal/3.1.1/lib.

And then add to your /etc/fpc.cfg
-Fu/Volumes/ram_disk/lib/fpc/$fpcversion/units/$fpctarget/*.

After that click in the IDE menu Tools / Rescan FPC source directory.

Mattias

Reply by email

Mattias Gaertner
to FreeMan: when I remove this folders then make lazarus and get this result (I remove a few same…
Show quoted text 13 lines
On 24.02.2015 10:29, FreeMan wrote: > > I'll lookin for i386-darwin and found this folders > /freepascal/3.1.1/compiler/i386/units/i386-darwin > /freepascal/3.1.1/packages/fpmkunit/units_bs/i386-darwin > /freepascal/3.1.1/rtl/units/i386-darwin > /freepascal/3.1.1/utils/fpcm/units/i386-darwin > and this file > /freepascal/3.1.1/rtl/darwin/fpcmade.i386-darwin when I remove this folders then make lazarus and get this result (I remove a few same lines) make: -iVSPTPSOTO: Command not found

This typically means fpc is not in PATH.

Mattias

Reply by email

FreeMan
to Mattias Gaertner: On Tue, 24 Feb 2015 10:29:28 +0200 Building FPC yourself normally contains two steps:…

Thank you your suggestions Mattias.
If I'm not wrong, our result is same just way is little bit different. I don't like copy file every where, Examp.
my fpc and lazarus folders, under /opt/. fpc use this "/usr/lib/fpc/$fpcversion/units/$fpctarget/*" folder so copy files there. Same way, for binnary ppcxxx files copy to for /bin/ I prefer, make symbolic link, 'cos for remove or some time upgrade application (not just fpc & laz) need copy where to copied before, have to remember, but if its link can find easy, never mind this is how to use to.

in my script like this:
make -s clean all install INSTALL_PREFIX=$prefixVolume$fpc_prefix CPU_TARGET=$CPU_TARGET
after maked and add link to system
sudo ln -sf $prefixVolume$fpc_prefix"/share/doc/fpc-"$svnVer /usr/share/doc/fpc-"$svnVer"
sudo ln -sf $prefixVolume$fpc_prefix"/lib/fpc/" /usr/lib/ sudo ln -sf $prefixVolume$fpc_prefix"/bin/bin2obj" /bin --> here add other all files, I wrote one for example.

after then run this command:
sudo /usr/lib/fpc/"$svnVer"/samplecfg /usr/lib/fpc/"$svnVer"/ /private/etc

and this lines in created fpc.cfg,
# searchpath for units and other system dependent things -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget
-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/*
-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/rtl

sometime I run make command 10 times in day, maybe more. remove all files and rerun make command. I love my ssd :) so I add to my script "$prefixVolume" variable. This is for ram drive path, so all make job read write in ramdrive, so my ssd live not decrease.

Mattias Gaertner wrote 21 lines
You combined FPC sources (/Volumes/ram_disk/opt/freepascal/3.1.1) with the FPC installation (/Volumes/ram_disk/opt/freepascal/3.1.1). Although this is possible, it makes it harder to spot misconfigurations, so it is not recommended. If you are not an expert, do what all others do: Use different directories. For example make distclean all install INSTALL_PREFIX=/Volumes/ram_disk/ CPU_TARGET=x86_64 This creates the files under /Volumes/ram_disk/lib/fpc/3.1.1/units/x86_64-darwin Don't forget to remove /Volumes/ram_disk/opt/freepascal/3.1.1/lib. And then add to your /etc/fpc.cfg -Fu/Volumes/ram_disk/lib/fpc/$fpcversion/units/$fpctarget/*. After that click in the IDE menu Tools / Rescan FPC source directory. Mattias

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20150224/fa69ab16/attachment.html>

Reply by email

FreeMan
to Mattias Gaertner: On Tue, 24 Feb 2015 12:11:32 +0200 This typically means fpc is not in PATH. Mattias

Yes you right but
make -s clean all PREFIX=$prefixVolume$laz_prefix CPU_TARGET=x86_64 OS_TARGET=darwin LCL_PLATFORM=qt OPT="-k'-framework' -k'ApplicationServices' -dUSE_QT_45 -g -gl"

*CPU_TARGET=x86_64*
one more time I remove all fpc and lazarus files, re download from svn and maked fpc first. Than check one more time.
type in terminal
? fpc
Free Pascal Compiler version 3.1.1 [2015/02/24] for x86_64 ? ppcx64
Free Pascal Compiler version 3.1.1 [2015/02/24] for x86_64 ? ppc386
zsh: command not found: ppc386

yes ppc386 not found 'cos I'm not use it with lazarus

and result:
Free Pascal Compiler version 3.1.1 [2015/02/24] for x86_64 Copyright (c) 1993-2015 by Florian Klaempfl and others (1002) Target OS: Darwin for x86_64
(3104) Compiling fcllaz.pas
(3104) Compiling registerfcl.pas
(3104) Compiling lazaruspackageintf.pas
(9009) Assembling lazaruspackageintf
/Volumes/ram_disk/opt/lazarus/packager/registration/registerfcl.pas(45,22) Fatal: (10022) Can't find unit process used by RegisterFCL Fatal: (1018) Compilation aborted
make[1]: *** [fcllaz.ppu] Error 1
make: *** [registration] Error 2

Mattias Gaertner wrote 5 lines
> remove a few same lines) > >make: -iVSPTPSOTO: Command not found This typically means fpc is not in PATH. Mattias

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20150224/f12c24f7/attachment.html>

Reply by email

Mattias Gaertner
to FreeMan: Thank you your suggestions Mattias. If I'm not wrong, our result is same just way is…
[...] I don't like copy file every where,

That was not my point.
My point was that you should not install FPC into itself.

Show quoted text 6 lines
[...] and this lines in created fpc.cfg, # searchpath for units and other system dependent things -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/* -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/rtl

ok, so process.ppu should be in the unit path.
Try to compile this:

uses process;
begin
end.
sometime I run make command 10 times in day, maybe more. remove all files and rerun make command. I love my ssd :) so I add to my script "$prefixVolume" variable. This is for ram drive path, so all make job read write in ramdrive, so my ssd live not decrease.

If your ssd does not support writing 20GB per day, you should buy another one.

Mattias

Reply by email

FreeMan
to Mattias Gaertner
Mattias Gaertner wrote 6 lines
ok, so process.ppu should be in the unit path. Try to compile this: uses process; begin end.

Yes you right, unit not found. 'cos fpc not make all application for x64???

command line:
make -s distclean all install INSTALL_PREFIX=$prefixVolume$fpc_prefix CPU_TARGET=x86_64
fpc bin folder just this binnary files, not check others but many application not compiled for x64 too.
fpc, mkarmins, mkx86ins, ppudump, ppufiles, ppumove

ofcourse in my script this line gives error. And error mean fpc.cfg not created and lib paths can not find anymore
sudo /usr/lib/fpc/"$svnVer"/samplecfg /usr/lib/fpc/"$svnVer"/ /private/etc

result :
Running on darwin
Write permission in /private/etc.
Writing sample configuration file to /private/etc/fpc.cfg /usr/lib/fpc/3.1.1/samplecfg: line 77: fpcmkcfg: command not found

Reply by email

FreeMan
to FreeMan

fpc not make all application for x64, is this bug ?

FreeMan wrote 37 lines
On 24.02.2015 15:00, Mattias Gaertner wrote: > ok, so process.ppu should be in the unit path. > Try to compile this: > > uses process; > begin > end. Yes you right, unit not found. 'cos fpc not make all application for x64??? command line: make -s distclean all install INSTALL_PREFIX=$prefixVolume$fpc_prefix CPU_TARGET=x86_64 fpc bin folder just this binnary files, not check others but many application not compiled for x64 too. fpc, mkarmins, mkx86ins, ppudump, ppufiles, ppumove ofcourse in my script this line gives error. And error mean fpc.cfg not created and lib paths can not find anymore sudo /usr/lib/fpc/"$svnVer"/samplecfg /usr/lib/fpc/"$svnVer"/ /private/etc result : Running on darwin Write permission in /private/etc. Writing sample configuration file to /private/etc/fpc.cfg /usr/lib/fpc/3.1.1/samplecfg: line 77: fpcmkcfg: command not found -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Mattias Gaertner
to Juha Manninen: On Mon, Feb 23, 2015 at 12:50 PM, Mattias Gaertner Switching in the IDE worked well with…
Show quoted text 9 lines
On Mon, Feb 23, 2015 at 12:50 PM, Mattias Gaertner wrote: > ok. > You know, that you don't need to change the PATH to switch the compiler > in the IDE, don't you? > And having both in the PATH allows fpc.exe to find both. Switching in the IDE worked well with two 32-bit compilers. Not any more, based on this one experience. I wil test more later.

Fixed.

Mattias

Reply by email