On 16 August 2012 10:55, Thomas Schatzl wrote:
> No, if no FPC or PP option is set, the makefiles always use a compiler
> executable in the path. This is typically the installed compiler.
That would explain in then. The FPC in my path is always the fixes
branch compiler - thus not the version re
On 08/16/2012 10:34 AM, Michael Schnell wrote:
I'll give it a try.
Using fpc 2.6.0 I could compile the compiler, but now it does not
compile Lazarus any more :(.
I'll wait some revisions and retry...
-Michael
___
fpc-devel maillist - fpc-devel@lis
Hi,
On 16 August 2012 10:53, Thomas Schatzl wrote:
>
> Actually, the speedup due to use of -T is not much anyway, because the
> effort for packages are relatively minor to compiling the rtl and
> compiler six times (during the "cycle" :).
Ever bit helps. :) Thanks for all the information.
At t
In our previous episode, Sven Barth said:
> >> to install the just compiled version to make it usable with Lazarus
> >>
> >> This does work, but i understand that this does not do any compiling.
> >
> > AFAIK it does do some compiling... e.g. the fpc utility is compiled in
> > that case.
>
> Just
In our previous episode, Sven Barth said:
> > After compiling I do
> >
> > make FPC=`pwd`/compiler/ppc386 install INSTALL_PREFIX=/usr
> >
>
> You don't need to specify the compiler here as "install" uses the
> compiled compiler (AFAIK).
IIRC it used to work if the all and install targets are in
Graeme Geldenhuys wrote on Thu, 16 Aug 2012:
On 16 August 2012 10:12, Jonas Maebe wrote:
make FPC=latest-release all -j ncpus FPMAKEOPT="-T ncpus"
Two questions...
1) Is the -j option still needed, now that we moved to fpmake with
the -T option? Sven said the -j option isn't usable any mo
Hi,
On Thu, 2012-08-16 at 10:23 +0100, Graeme Geldenhuys wrote:
> On 16 August 2012 09:34, Sven Barth wrote:
> >> make FPC=`pwd`/compiler/ppc386 install INSTALL_PREFIX=/usr
> >>
> >
> > You don't need to specify the compiler here as "install" uses the compiled
> > compiler (AFAIK).
>
>
No, if
Hi,
On Thu, 2012-08-16 at 10:36 +0100, Graeme Geldenhuys wrote:
> On 16 August 2012 10:12, Jonas Maebe wrote:
> > make FPC=latest-release all -j ncpus FPMAKEOPT="-T ncpus"
>
> Two questions...
>
> 1) Is the -j option still needed, now that we moved to fpmake with
> the -T option? Sven said the
On 16 August 2012 10:12, Jonas Maebe wrote:
> make FPC=latest-release all -j ncpus FPMAKEOPT="-T ncpus"
Two questions...
1) Is the -j option still needed, now that we moved to fpmake with
the -T option? Sven said the -j option isn't usable any more.
2) Does the value passed to -j or -T differ?
On 16 August 2012 09:34, Sven Barth wrote:
>> make FPC=`pwd`/compiler/ppc386 install INSTALL_PREFIX=/usr
>>
>
> You don't need to specify the compiler here as "install" uses the compiled
> compiler (AFAIK).
I have had problems before which forced me to start specifying the
compileradmittedly
Am 16.08.2012 10:34, schrieb Sven Barth:
to install the just compiled version to make it usable with Lazarus
This does work, but i understand that this does not do any compiling.
AFAIK it does do some compiling... e.g. the fpc utility is compiled in
that case.
Just checked... no it doesn't.
On Thu, 16 Aug 2012, Jonas Maebe wrote:
Michael Van Canneyt wrote on Thu, 16 Aug 2012:
When using a trunk compiler (that was a given from OP) the only way to
update is the following:
# update rtl & compiler to latest trunk.
svn update rtl compiler
# run cycle using latest release.
make cy
Michael Van Canneyt wrote on Thu, 16 Aug 2012:
When using a trunk compiler (that was a given from OP) the only way
to update is the following:
# update rtl & compiler to latest trunk.
svn update rtl compiler
# run cycle using latest release.
make cycle PP=latest-release # now you have latest
On Thu, 16 Aug 2012, Sven Barth wrote:
Am 16.08.2012 10:32, schrieb Michael Van Canneyt:
On Thu, 16 Aug 2012, Sven Barth wrote:
Am 16.08.2012 09:56, schrieb Graeme Geldenhuys:
On 16 August 2012 08:37, Michael Van Canneyt
wrote:
make cycle PP=ppcx64-2.6.0
I always do...
make cl
On 16 August 2012 09:30, Michael Schnell wrote:
> After compiling I do
>
> make FPC=`pwd`/compiler/ppc386 install INSTALL_PREFIX=/usr
'make install' doesn't compile anything, it just copies the already
compiled unit and executables in the correct location.
My own FPC usage:
I never install FPC
Am 16.08.2012 10:32, schrieb Michael Van Canneyt:
On Thu, 16 Aug 2012, Sven Barth wrote:
Am 16.08.2012 09:56, schrieb Graeme Geldenhuys:
On 16 August 2012 08:37, Michael Van Canneyt
wrote:
make cycle PP=ppcx64-2.6.0
I always do...
make clean
make all FPC=
This always see
Am 16.08.2012 10:30, schrieb Michael Schnell:
On 08/16/2012 10:21 AM, Thomas Schatzl wrote:
"make cycle" is for compiling the compiler itself, to be started in the
"compiler" subdirectory.
I see.
"Cycling" in this context means that the
compiler compiles itself a few times, each time with the
On 08/16/2012 10:27 AM, Michael Van Canneyt wrote:
Install in a temp location from the tar.gz archive, copy binary to the
place of your choice.
This one for X86 Linux?
http://sourceforge.net/projects/freepascal/files/Linux/2.6.0/fpc-2.6.0.i386-linux.tar/download
I'll give it a try.
Thanks
On Thu, 16 Aug 2012, Sven Barth wrote:
Am 16.08.2012 09:56, schrieb Graeme Geldenhuys:
On 16 August 2012 08:37, Michael Van Canneyt
wrote:
make cycle PP=ppcx64-2.6.0
I always do...
make clean
make all FPC=
This always seems to work. I assume 'make all' gets translated to
On Thu, 16 Aug 2012, Graeme Geldenhuys wrote:
On 16 August 2012 08:37, Michael Van Canneyt wrote:
make cycle PP=ppcx64-2.6.0
I always do...
make clean
make all FPC=
This always seems to work. I assume 'make all' gets translated to a
'make cycle' somehow? Or have I just been lucky
On 08/16/2012 10:21 AM, Thomas Schatzl wrote:
"make cycle" is for compiling the compiler itself, to be started in the
"compiler" subdirectory.
I see.
"Cycling" in this context means that the
compiler compiles itself a few times, each time with the recently
compiled compiler, to make sure that
Am 16.08.2012 09:56, schrieb Graeme Geldenhuys:
On 16 August 2012 08:37, Michael Van Canneyt wrote:
make cycle PP=ppcx64-2.6.0
I always do...
make clean
make all FPC=
This always seems to work. I assume 'make all' gets translated to a
'make cycle' somehow? Or have I just been
On Thu, 16 Aug 2012, Michael Schnell wrote:
On 08/16/2012 09:57 AM, Graeme Geldenhuys wrote:
ALWAYS, ALWAYS, ALWAYS USE THE LATEST ***RELEASED*** FPC TO COMPILE TRUNK.
I see that does make sense.
Is there a chance to just put the appropriate executable somewhere without
doing a real insta
On 08/16/2012 09:56 AM, Graeme Geldenhuys wrote:
I always do...
make clean
make all FPC=
This always seems to work. I assume 'make all' gets translated to a
'make cycle' somehow? Or have I just been lucky for the last 5 years
doing it my way?
This is exactly what I did until my ra
On 08/16/2012 09:57 AM, Graeme Geldenhuys wrote:
ALWAYS, ALWAYS, ALWAYS USE THE LATEST ***RELEASED*** FPC TO COMPILE
TRUNK.
I see that does make sense.
Is there a chance to just put the appropriate executable somewhere
without doing a real installation ?
Thanks,
-Michael
_
hi,
On Thu, 2012-08-16 at 09:50 +0200, Michael Schnell wrote:
> On 08/16/2012 09:37 AM, Michael Van Canneyt wrote:
> >
> > You must do a "make cycle" in the main or compiler directory, with as
> > a starting compiler version 2.6.0.
> Never heard of this one =-O
> What does it do ?
"make cycle"
Am 16.08.2012 09:50, schrieb Michael Schnell:
On 08/16/2012 09:37 AM, Michael Van Canneyt wrote:
You must do a "make cycle" in the main or compiler directory, with as
a starting compiler version 2.6.0.
Never heard of this one =-O
What does it do ?
Usually, I do a
make cycle PP=ppcx64-2.6.0
On 16 August 2012 08:50, Michael Schnell wrote:
> Right now, for compiling I do
>
> make clean all FPC=/usr/local/bin/fpc
>
> and
>
> /usr/local/bin/fpc is
> Free Pascal Compiler version 2.7.1 [2012/07/16] for i386
Your commands seem correct to me, but ALWAYS, ALWAYS, ALWAYS USE
THE LAT
On 16 August 2012 08:37, Michael Van Canneyt wrote:
> make cycle PP=ppcx64-2.6.0
I always do...
make clean
make all FPC=
This always seems to work. I assume 'make all' gets translated to a
'make cycle' somehow? Or have I just been lucky for the last 5 years
doing it my way?
What's
Am 16.08.2012 09:12, schrieb Michael Schnell:
On 08/15/2012 06:03 PM, Michael Van Canneyt wrote:
Fixed in rev. 22092.
22097:
Since several versions I get multiple of those:
make -C linux all
make[7]: Entering directory
`/home/mschnell/Downloads/svn/fpc/trunk/rtl/linux'
/bin/mkdir -p /home/m
On 08/16/2012 09:37 AM, Michael Van Canneyt wrote:
You must do a "make cycle" in the main or compiler directory, with as
a starting compiler version 2.6.0.
Never heard of this one =-O
What does it do ?
Usually, I do a
make cycle PP=ppcx64-2.6.0
should I PP the compiler to be used to comp
On Thu, 16 Aug 2012, Michael Schnell wrote:
On 08/15/2012 06:03 PM, Michael Van Canneyt wrote:
Fixed in rev. 22092.
22097:
Since several versions I get multiple of those:
make -C linux all
make[7]: Entering directory
`/home/mschnell/Downloads/svn/fpc/trunk/rtl/linux'
/bin/mkdir -p /hom
On 08/15/2012 06:03 PM, Michael Van Canneyt wrote:
Fixed in rev. 22092.
22097:
Since several versions I get multiple of those:
make -C linux all
make[7]: Entering directory
`/home/mschnell/Downloads/svn/fpc/trunk/rtl/linux'
/bin/mkdir -p /home/mschnell/Downloads/svn/fpc/trunk/rtl/units/i38
On 15 August 2012 17:03, Michael Van Canneyt wrote:
>
> Fixed in rev. 22092.
Thanks Michael, it's compiling 100% now.
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://fpgui.sourceforge.net
__
On Wed, 15 Aug 2012, Graeme Geldenhuys wrote:
Hi,
I just got an FPC 2.7.1 update (r22088) and tried to do a new compile.
Yes, I am using the released 2.6.0 as starting compiler. I get the
following error in the fpdoc code.
Fixed in rev. 22092.
I am working on the fcl-passrc pascal source s
Hi,
I just got an FPC 2.7.1 update (r22088) and tried to do a new compile.
Yes, I am using the released 2.6.0 as starting compiler. I get the
following error in the fpdoc code.
Using Linux 64-bit with FPC 2.6.0 64-bit as starting compiler.
===
...snip...
make[3]: Enteri
36 matches
Mail list logo
