Sign in Join

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

Mailing lists / lazarus / 2013-09

Add package

8 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

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

Antonio Fortuny

Hi All.

I run into a Lazarus package install that I've had some months ago but on Win64. This time problem araises into my new Lazarus 1.0.12 in a Linux x86_64 box
The package is Indy. The package compilation itself runs OK, no problem. It hes been compiled with -fPIC because it is used in a shared library. When rebuilding the IDE, the following messages are displayed: make: Entering directory `/usr/lib64/lazarus'
/usr/bin/make -C ide idepkg
make[1]: Entering directory `/usr/lib64/lazarus/ide' /usr/bin/make --assume-new=lazarus.pp lazarus OPT=' -O2 -g- -Xs @/home/sita/.lazarus/idemake.cfg
-FU/home/sita/.lazarus/units/x86_64-linux/gtk2
-FE/home/sita/.lazarus/bin -o/home/sita/.lazarus/bin/lazarus' make[2]: Entering directory `/usr/lib64/lazarus/ide' /usr/bin/fpc -gl -Sci -dlclgtk2 -Fu../designer -Fu../debugger -Fu../debugger/frames -Fu../converter -Fu../packager -Fu../packager/frames -Fu../components/custom -Fuframes -Fu. -Fiinclude -Fiinclude/linux -Fi../images -FE.. -FU../units/x86_64-linux/gtk2 -Cg -Fl/usr/lib64/gcc/x86_64-suse-linux/4.7 -Fl/usr/local/lib64 -Fl/usr/local/lib -Flinclude -Fl/etc/ld.so.conf.d/*.conf -O2 -g- -Xs @/home/sita/.lazarus/idemake.cfg
-FU/home/sita/.lazarus/units/x86_64-linux/gtk2
-FE/home/sita/.lazarus/bin -o/home/sita/.lazarus/bin/lazarus -dx86_64 lazarus.pp
Free Pascal Compiler version 2.6.2 [2013/03/17] for x86_64 Copyright (c) 1993-2012 by Florian Klaempfl and others Target OS: Linux for x86-64
Compiling lazarus.pp
PPU Loading
/home/sources/packages/Indy10/lib/lib/x86_64-linux/IdStreamVCL.ppu PPU Source: IdStreamVCL.pas not found
PPU Source: IdCompilerDefines.inc not found
Recompiling IdStreamVCL, checksum changed for IdGlobal IdStream.pas(29,3) Fatal: Can not find unit IdStreamVCL used by IdStream.

All units (*.o and *.ppu) have been compiled with the package itself and are visible in the ./lib/x86_64-linux folder
I couldn't find something similar in the history.

Antonio.
.

Reply by email

Mattias Gaertner
to Antonio Fortuny
Show quoted text 40 lines
Hi All. I run into a Lazarus package install that I've had some months ago but on Win64. This time problem araises into my new Lazarus 1.0.12 in a Linux x86_64 box The package is Indy. The package compilation itself runs OK, no problem. It hes been compiled with -fPIC because it is used in a shared library. When rebuilding the IDE, the following messages are displayed: make: Entering directory `/usr/lib64/lazarus' /usr/bin/make -C ide idepkg make[1]: Entering directory `/usr/lib64/lazarus/ide' /usr/bin/make --assume-new=lazarus.pp lazarus OPT=' -O2 -g- -Xs @/home/sita/.lazarus/idemake.cfg -FU/home/sita/.lazarus/units/x86_64-linux/gtk2 -FE/home/sita/.lazarus/bin -o/home/sita/.lazarus/bin/lazarus' make[2]: Entering directory `/usr/lib64/lazarus/ide' /usr/bin/fpc -gl -Sci -dlclgtk2 -Fu../designer -Fu../debugger -Fu../debugger/frames -Fu../converter -Fu../packager -Fu../packager/frames -Fu../components/custom -Fuframes -Fu. -Fiinclude -Fiinclude/linux -Fi../images -FE.. -FU../units/x86_64-linux/gtk2 -Cg -Fl/usr/lib64/gcc/x86_64-suse-linux/4.7 -Fl/usr/local/lib64 -Fl/usr/local/lib -Flinclude -Fl/etc/ld.so.conf.d/*.conf -O2 -g- -Xs @/home/sita/.lazarus/idemake.cfg -FU/home/sita/.lazarus/units/x86_64-linux/gtk2 -FE/home/sita/.lazarus/bin -o/home/sita/.lazarus/bin/lazarus -dx86_64 lazarus.pp Free Pascal Compiler version 2.6.2 [2013/03/17] for x86_64 Copyright (c) 1993-2012 by Florian Klaempfl and others Target OS: Linux for x86-64 Compiling lazarus.pp PPU Loading /home/sources/packages/Indy10/lib/lib/x86_64-linux/IdStreamVCL.ppu PPU Source: IdStreamVCL.pas not found PPU Source: IdCompilerDefines.inc not found Recompiling IdStreamVCL, checksum changed for IdGlobal IdStream.pas(29,3) Fatal: Can not find unit IdStreamVCL used by IdStream. All units (*.o and *.ppu) have been compiled with the package itself and are visible in the ./lib/x86_64-linux folder I couldn't find something similar in the history.

Last time I tried Indy it had some circular dependencies in units, which fpc had problems with. This can be remedied by compiling a second, sometimes a third time.
Open the Indy package and use the "Compile" button to compile it three times.
Then build the IDE.

Mattias

Reply by email

Antonio Fortuny
to Graeme Geldenhuys

Le 18/09/2013 17:03, Graeme Geldenhuys a ?crit :

On 2013-09-18 11:09, Antonio Fortuny wrote: > The package is Indy. On a different subject. What is the latest Indy version that works with FPC? I have 10.5.8 here, is that the latest for FPC?

I'm currently working with 10.6.0 on Win32, Win64, Linux x86_64 and WinCE

Antonio.

Show quoted text 5 lines
Regards, - Graeme -
Sita Software *Antonio Fortuny* Senior Software engineer 220, avenue de la Libert? L-4602 Niederkorn Tel.: +352 58 00 93 - 93 www.sitasoftware.lu <http://www.sitasoftware.lu> Your IT Partner -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130919/e47de14d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: fbdfhfji.jpg Type: image/jpeg Size: 2306 bytes Desc: not available URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130919/e47de14d/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: hdijache.jpg Type: image/jpeg Size: 921 bytes Desc: not available URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130919/e47de14d/attachment-0001.jpg>

Reply by email

Marco van de Voort
to Mattias Gaertner: On Wed, 18 Sep 2013 12:09:50 +0200 Last time I tried Indy it had some circular…
Mattias Gaertner wrote 10 lines
> All units (*.o and *.ppu) have been compiled with the package itself and > are visible in the ./lib/x86_64-linux folder > I couldn't find something similar in the history. Last time I tried Indy it had some circular dependencies in units, which fpc had problems with. This can be remedied by compiling a second, sometimes a third time. Open the Indy package and use the "Compile" button to compile it three times. Then build the IDE.

The last time I worked with Indy, deduping the .inc files resolved the the circular dependency problem. They had multiple, not exactly the same copies.

Reply by email

Mattias Gaertner
to Marco van de Voort
Show quoted text 14 lines
On Wed, Sep 18, 2013 at 01:01:59PM +0200, Mattias Gaertner wrote: > > All units (*.o and *.ppu) have been compiled with the package itself and > > are visible in the ./lib/x86_64-linux folder > > I couldn't find something similar in the history. > > Last time I tried Indy it had some circular dependencies in units, which > fpc had problems with. This can be remedied by compiling a > second, sometimes a third time. > Open the Indy package and use the "Compile" button to compile it three > times. > Then build the IDE. The last time I worked with Indy, deduping the .inc files resolved the the circular dependency problem. They had multiple, not exactly the same copies.

Why does the Delphi compiler eat multiple include files with same name?

Mattias

Reply by email

Marco van de Voort
to Mattias Gaertner
Mattias Gaertner wrote 8 lines
> > times. > > Then build the IDE. > > The last time I worked with Indy, deduping the .inc files resolved the the > circular dependency problem. They had multiple, not exactly the same copies. Why does the Delphi compiler eat multiple include files with same name?

Delphi is less strict with dependencies on .inc files. (no CRC?, only timestamping?)

Reply by email