problems compiling FPC

classic Classic list List threaded Threaded
45 messages Options
123
Reply | Threaded
Open this post in threaded view
|

problems compiling FPC

Darius Blaszyk

Hi,

 

I am trying to update my FPC from SVN, but for some reason I keep on getting a compilation error. The last build was from 21955 (23rd July 2012). See below for the makefile output.

 

Regards, Darius

 


 

C:\lazarus\fpc\trunk>make all
make compiler_cycle RELEASE=1
make[1]: Entering directory `C:/lazarus/fpc/trunk'
make -C compiler cycle
make[2]: Entering directory `C:/lazarus/fpc/trunk/compiler'
make tempclean ppc3.exe
make[3]: Entering directory `C:/lazarus/fpc/trunk/compiler'
/pp/bin/i386-win32/rm.exe -f ppcross386.exe ppc.exe ppc1.exe ppc2.exe ppc3.exe ./msg2inc.exe pp1.wpo pp2.wpo
make 'OLDFPC=' next CYCLELEVEL=1
make[4]: Entering directory `C:/lazarus/fpc/trunk/compiler'
make rtlclean rtl
make[5]: Entering directory `C:/lazarus/fpc/trunk/compiler'
make -C C:/lazarus/fpc/trunk/rtl clean
make[6]: Entering directory `C:/lazarus/fpc/trunk/rtl'
/pp/bin/i386-win32/rm.exe -f fpcmade.i386-win32 Package.fpc ppas.sh script.res link.res
/pp/bin/i386-win32/rm.exe -f *.s *_ppas.bat
make -C win32 clean
make[7]: Entering directory `C:/lazarus/fpc/trunk/rtl/win32'
/pp/bin/i386-win32/rm.exe -f C:/lazarus/fpc/trunk/rtl/units/i386-win32/system.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/uuchar.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/objpas.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/macpas.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/iso7185.ppu C:/l
zarus/fpc/trunk/rtl/units/i386-win32/buildrtl.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/lineinfo.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/lnfodwrf.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/sysinitpas.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/sysinitcyg.ppu C:/lazarus/fpc/trunk/rtl/
nits/i386-win32/sysinitgprof.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/ctypes.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/strings.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/heaptrc.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/matrix.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/windows.pp
 C:/lazarus/fpc/trunk/rtl/units/i386-win32/winsock.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/winsock2.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/initc.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/cmem.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/dynlibs.ppu C:/lazarus/fpc/trunk/rtl/units/i
86-win32/signals.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/dos.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/crt.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/objects.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/messages.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/rtlconsts.ppu C:/lazarus/fp
/trunk/rtl/units/i386-win32/sysconst.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/sysutils.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/math.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/types.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/strutils.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/dat
utils.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/varutils.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/variants.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/typinfo.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/fgl.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/classes.ppu C:/lazarus/fpc/trunk/
tl/units/i386-win32/convutils.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/stdconvs.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/cpu.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/mmx.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/charset.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/character.ppu
:/lazarus/fpc/trunk/rtl/units/i386-win32/ucomplex.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/getopts.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/winevent.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/sockets.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/printer.ppu C:/lazarus/fpc/trunk/rtl/uni
s/i386-win32/video.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/mouse.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/keyboard.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/fmtbcd.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/winsysut.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/sharemem.ppu C:/laz
rus/fpc/trunk/rtl/units/i386-win32/exeinfo.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/fpintres.ppu C:/lazarus/fpc/trunk/rtl/units/i386-win32/windirs.ppu
/pp/bin/i386-win32/rm.exe -f C:/lazarus/fpc/trunk/rtl/units/i386-win32/math.rst C:/lazarus/fpc/trunk/rtl/units/i386-win32/varutils.rst C:/lazarus/fpc/trunk/rtl/units/i386-win32/typinfo.rst C:/lazarus/fpc/trunk/rtl/units/i386-win32/variants.rst C:/lazarus/fpc/trunk/rtl/units/i386-win32/classes.rst C
/lazarus/fpc/trunk/rtl/units/i386-win32/dateutils.rst C:/lazarus/fpc/trunk/rtl/units/i386-win32/sysconst.rst
/pp/bin/i386-win32/rm.exe -f fpcmade.i386-win32 Package.fpc ppas.sh script.res link.res
/pp/bin/i386-win32/rm.exe -f *.s *_ppas.bat
make[7]: Leaving directory `C:/lazarus/fpc/trunk/rtl/win32'
make[6]: Leaving directory `C:/lazarus/fpc/trunk/rtl'
make -C C:/lazarus/fpc/trunk/rtl 'OPT=  ' all
make[6]: Entering directory `C:/lazarus/fpc/trunk/rtl'
make -C win32 all
make[7]: Entering directory `C:/lazarus/fpc/trunk/rtl/win32'
C:/pp/bin/i386-win32/ppc386.exe -Ur -Xs -O2 -n -Fi../inc -Fi../i386 -Fi../win -FE. -FUC:/lazarus/fpc/trunk/rtl/units/i386-win32 -di386 -dRELEASE -Us -Sg system.pp -Fi../win
generic.inc(2505,13) Fatal: Internal error 8
Fatal: Compilation aborted
make[7]: *** [system.ppu] Error 1
make[7]: Leaving directory `C:/lazarus/fpc/trunk/rtl/win32'
make[6]: *** [win32_all] Error 2
make[6]: Leaving directory `C:/lazarus/fpc/trunk/rtl'
make[5]: *** [rtl] Error 2
make[5]: Leaving directory `C:/lazarus/fpc/trunk/compiler'
make[4]: *** [next] Error 2
make[4]: Leaving directory `C:/lazarus/fpc/trunk/compiler'
make[3]: *** [ppc1.exe] Error 2
make[3]: Leaving directory `C:/lazarus/fpc/trunk/compiler'
make[2]: *** [cycle] Error 2
make[2]: Leaving directory `C:/lazarus/fpc/trunk/compiler'
make[1]: *** [compiler_cycle] Error 2
make[1]: Leaving directory `C:/lazarus/fpc/trunk'
make: *** [build-stamp.i386-win32] Error 2


_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Marco van de Voort
In our previous episode, [hidden email] said:
>
> I am trying to update my FPC from SVN, but for some reason I
> keep on getting a compilation error. The last build was from 21955 (23rd
> July 2012). See below for the makefile output.

The crucial bit of information, the version of the starting compiler, is
missing.

It should be 2.6.0, and nothing else.
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Darius Blaszyk

The starting compiler is also from SVN (21955).

 

 

On 16 okt '12, [hidden email] wrote:

In our previous episode, [hidden email]said:
I am trying to update my FPC from SVN, but for some reason I keep on getting a compilation error. The last build was from 21955 (23rd July 2012). See below for the makefile output.
The crucial bit of information, the version of the starting compiler, is
missing.

It should be 2.6.0, and nothing else.
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

 

 

 

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Vincent Snijders-3
2012/10/16  <[hidden email]>:
> The starting compiler is also from SVN (21955).
> On 16 okt '12, [hidden email] wrote:
>
> It should be 2.6.0, and nothing else.

Then the solution is simple, use fpc 2.6.0.

Vincent
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Marco van de Voort
In reply to this post by Darius Blaszyk
In our previous episode, [hidden email] said:
> The starting compiler is also from SVN (21955).

[bold][font size=10000][color=red][style=blink]
The starting compiler is only guaranteed to work if it is the last release.
And only the last release, 2.6.0.

Anything else can break at any time.
[/style][/color][/font][/bold]


_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Darius Blaszyk

I heard you the first time, don't worry. Just don't clown around so much. It was a perfectly normal reply on your mail. I will do as you proposed.

 

 

 

On 16 okt '12, [hidden email] wrote:

In our previous episode, [hidden email]said:
The starting compiler is also from SVN (21955).
[bold][font size=10000][color=red][style=blink]
The starting compiler is only guaranteed to work if it is the last release.
And only the last release, 2.6.0.

Anything else can break at any time. 
[/style][/color][/font][/bold]


_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

 

 

 

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Graeme Geldenhuys-3
In reply to this post by Marco van de Voort
On 2012-10-16 22:01, Marco van de Voort wrote:
>
> [bold][font size=10000][color=red][style=blink]
> The starting compiler is only guaranteed.... [snip]
> [/style][/color][/font][/bold]


hehehe.... It is rather crazy how often this same problem occurs on the
mailing list.


Just thinking out loud...
Couldn't there be a check in the build system that if the FPC version is
not the latest know released version, the build will immediately
terminate with same message your wrote. The build system in Trunk and
Fixes branch could be hard-coded to what the correct starting compiler
version should be (just like the compile has a constant to say what
version it is).

Optional: And if for some "advanced" reason a starting compiler other
than the last stable release version must be used, then a --force or
something like that parameter could be introduced too.

This will then hopefully reduce (or with some luck totally eliminate)
this very popular support question.


G.


_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Marco van de Voort
In our previous episode, Graeme Geldenhuys said:
> > [bold][font size=10000][color=red][style=blink]
> > The starting compiler is only guaranteed.... [snip]
> > [/style][/color][/font][/bold]
>
> hehehe.... It is rather crazy how often this same problem occurs on the
> mailing list.

And how old the problem is. It was already in the "make cycle faq" I think,
the precursor to the buildfaq.
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Rainer Stratmann
In reply to this post by Graeme Geldenhuys-3
Am Tuesday 16 October 2012 23:21:51 schrieb Graeme Geldenhuys:
> This will then hopefully reduce (or with some luck totally eliminate)
> this very popular support question.

I work like this.
I try to eliminate questions from the users.
In principle users of my progam only have to plug a USB Stick and the
powercable in the computer.

Without go deep in it likely it is possible to implement your suggestion.
But that means work...
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Graeme Geldenhuys-3
On 2012-10-16 22:37, Rainer Stratmann wrote:
> But that means work...

And how much waisted time was spend by users "debugging the issue" and
by developers answering the same question over and over. As Marco said,
this issue has been around for years!

Programmers write code to reduce work, not make more work. :)


Regards,
  - Graeme -

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Rainer Stratmann
Am Tuesday 16 October 2012 23:47:45 schrieb Graeme Geldenhuys:
> On 2012-10-16 22:37, Rainer Stratmann wrote:
> > But that means work...
>
> And how much waisted time was spend by users "debugging the issue" and
> by developers answering the same question over and over. As Marco said,
> this issue has been around for years!

Yes, of course. The work will be worthwhile, but someone has to do that
work...

>
> Programmers write code to reduce work, not make more work. :)

Recently I read a comment:
http://www.heise.de/developer/news/foren/S-Programmierer-tun-mir-leid/forum-238723/msg-22487244/read/
Translation (hope I do it right): I pity programmers, they will never finish.

>
>
> Regards,
>   - Graeme -
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

vfclists .


On 16 October 2012 22:58, Rainer Stratmann <[hidden email]> wrote:
Am Tuesday 16 October 2012 23:47:45 schrieb Graeme Geldenhuys:
> On 2012-10-16 22:37, Rainer Stratmann wrote:
> > But that means work...
>
> And how much waisted time was spend by users "debugging the issue" and
> by developers answering the same question over and over. As Marco said,
> this issue has been around for years!

Yes, of course. The work will be worthwhile, but someone has to do that
work...

>
> Programmers write code to reduce work, not make more work. :)

Recently I read a comment:
http://www.heise.de/developer/news/foren/S-Programmierer-tun-mir-leid/forum-238723/msg-22487244/read/
Translation (hope I do it right): I pity programmers, they will never finish.

>
>
> Regards,
>   - Graeme -
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

As the solution doesn't seem to be too difficult which file or files can "we" zoom in on to fix it?

--
Frank Church

=======================
http://devblog.brahmancreations.com

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Graeme Geldenhuys-3
On 2012-10-17 01:40, Frank Church wrote:
>
> As the solution doesn't seem to be too difficult which file or files can
> "we" zoom in on to fix it?


Thanks for showing interest in this. I know near zero about Makefiles
and Makefile.fpc. I'm still a bit confused with FPC though. Does FPC now
use fpmake everywhere? If yes, then why are there still so many
Makefiles in FPC Trunk? Quite possibly I just don't understand the use
of fpmake I guess.

The idea seems quite simple though. Do a `$compiler -iV` where $compiler
is the starting compiler use to compile the FPC source code. If that
version doesn't match a known "latest stable compiler version" constant,
then report an error and terminate.

Regards,
  - Graeme -



_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Mark Morgan Lloyd-5
Graeme Geldenhuys wrote:

> On 2012-10-17 01:40, Frank Church wrote:
>> As the solution doesn't seem to be too difficult which file or files can
>> "we" zoom in on to fix it?
>
>
> Thanks for showing interest in this. I know near zero about Makefiles
> and Makefile.fpc. I'm still a bit confused with FPC though. Does FPC now
> use fpmake everywhere? If yes, then why are there still so many
> Makefiles in FPC Trunk? Quite possibly I just don't understand the use
> of fpmake I guess.
>
> The idea seems quite simple though. Do a `$compiler -iV` where $compiler
> is the starting compiler use to compile the FPC source code. If that
> version doesn't match a known "latest stable compiler version" constant,
> then report an error and terminate.

Some slack would be desirable: stable is 2.6.0 but there are known
issues which are fixed by 2.6.1. Perhaps we need something like
"FORCE=1" to allow a minor version bump to be accepted, or "FORCE=1.1"
to accept anything up to 2.7.1.

However the thing that's really needed in my opinion is a clear
statement for each SVN tag which FPC version should be used for
compilation. Ditto for Lazarus, it shouldn't be necessary to delve into
the source to find this.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Jonas Maebe-2
In reply to this post by Graeme Geldenhuys-3

On 17 Oct 2012, at 10:53, Graeme Geldenhuys wrote:

> The idea seems quite simple though. Do a `$compiler -iV` where $compiler
> is the starting compiler use to compile the FPC source code. If that
> version doesn't match a known "latest stable compiler version" constant,
> then report an error and terminate.

See http://www.mail-archive.com/fpc-pascal@.../msg25868.html and the rest of the thread.


Jonas_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Rainer Stratmann
In reply to this post by Mark Morgan Lloyd-5
Am Wednesday 17 October 2012 11:10:22 schrieb Mark Morgan Lloyd:

> Graeme Geldenhuys wrote:
> > On 2012-10-17 01:40, Frank Church wrote:
> >> As the solution doesn't seem to be too difficult which file or files can
> >> "we" zoom in on to fix it?
> >
> > Thanks for showing interest in this. I know near zero about Makefiles
> > and Makefile.fpc. I'm still a bit confused with FPC though. Does FPC now
> > use fpmake everywhere? If yes, then why are there still so many
> > Makefiles in FPC Trunk? Quite possibly I just don't understand the use
> > of fpmake I guess.
> >
> > The idea seems quite simple though. Do a `$compiler -iV` where $compiler
> > is the starting compiler use to compile the FPC source code. If that
> > version doesn't match a known "latest stable compiler version" constant,
> > then report an error and terminate.
>
> Some slack would be desirable: stable is 2.6.0 but there are known
> issues which are fixed by 2.6.1. Perhaps we need something like
> "FORCE=1" to allow a minor version bump to be accepted, or "FORCE=1.1"
> to accept anything up to 2.7.1.

ACCEPTEDVERSION="x.x.x" also could be a flexible solution.

> However the thing that's really needed in my opinion is a clear
> statement for each SVN tag which FPC version should be used for
> compilation. Ditto for Lazarus, it shouldn't be necessary to delve into
> the source to find this.


_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Graeme Geldenhuys-3
In reply to this post by Mark Morgan Lloyd-5
On 2012-10-17 10:10, Mark Morgan Lloyd wrote:
>
> Some slack would be desirable: stable is 2.6.0 but there are known
> issues which are fixed by 2.6.1.

Nope, the FPC developers made the rules quite clear! Not even the fixes
branch is guaranteed to compile FPC Trunk. ONLY the last released FPC is
guaranteed. I have even stumbled over this too, where the fixes branch
couldn't compile FPC Trunk, but the latest released version could.

The fixes branch is "mislabelled". Contrary to the name, not only fixes
get applied to that branch. In recent months, more and more "minor new
features" got added to the fixes branch too.


> Perhaps we need something like
> "FORCE=1" to allow a minor version bump to be accepted, or "FORCE=1.1"
> to accept anything up to 2.7.1.

This is exactly what I mentioned too, but only for very specific cases
(though I don't know if such cases exist). Allow a --force or something
parameter to allow the developer to use a different starting compiler
(thus ignoring the version check), but ONLY if they know what they are
doing.


> However the thing that's really needed in my opinion is a clear
> statement for each SVN tag which FPC version should be used for

That will be a ridiculous amount of work. The existing rule of always
using the latest released FPC as the starting compiler is good enough.


Regards,
   Graeme.

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Graeme Geldenhuys-3
In reply to this post by Jonas Maebe-2
On 2012-10-17 10:15, Jonas Maebe wrote:
>
> See http://www.mail-archive.com/..../msg25868.html and the rest of
> the thread.

[embarrassed] Clearly my age is starting to show. :-) How do you find
this old messages in any case.


Your concern about cross-compiling could be an exception - FPC version
restriction is not applied in such cases. Cross-compiling in by far the
less used option. Most people that complain about this issue is simply
trying to compile a new FPC version for their current target.

The --force or --ignore-fpc-version option could still help those corner
cases, like new platforms where a previous released version did not
exist. The developers working on such features should know what they are
doing anyway, so fits in with my earlier statement too.

Regards,
  - Graeme -
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Mark Morgan Lloyd-5
In reply to this post by Graeme Geldenhuys-3
Graeme Geldenhuys wrote:
> On 2012-10-17 10:10, Mark Morgan Lloyd wrote:
>> Some slack would be desirable: stable is 2.6.0 but there are known
>> issues which are fixed by 2.6.1.
>
> Nope, the FPC developers made the rules quite clear! Not even the fixes
> branch is guaranteed to compile FPC Trunk. ONLY the last released FPC is
> guaranteed. I have even stumbled over this too, where the fixes branch
> couldn't compile FPC Trunk, but the latest released version could.

Graeme, I know what policy is. However I'd point out that right now you
/need/ 2.6.1 to compile FPC for SPARC due to code generation issues, and
there have previously been similar problems with ARM while FP stuff was
work-in-progress.

So saying "if it won't compile with stable then sod off" isn't helpful.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Reply | Threaded
Open this post in threaded view
|

Re: problems compiling FPC

Reinier Olislagers
On 17-10-2012 12:49, Mark Morgan Lloyd wrote:

> Graeme Geldenhuys wrote:
>> On 2012-10-17 10:10, Mark Morgan Lloyd wrote:
>>> Some slack would be desirable: stable is 2.6.0 but there are known
>>> issues which are fixed by 2.6.1.
>>
>> Nope, the FPC developers made the rules quite clear! Not even the fixes
>> branch is guaranteed to compile FPC Trunk. ONLY the last released FPC is
>> guaranteed. I have even stumbled over this too, where the fixes branch
>> couldn't compile FPC Trunk, but the latest released version could.
>
> Graeme, I know what policy is. However I'd point out that right now you
> /need/ 2.6.1 to compile FPC for SPARC due to code generation issues, and
> there have previously been similar problems with ARM while FP stuff was
> work-in-progress.
>
> So saying "if it won't compile with stable then sod off" isn't helpful.

Mark, I understand what you mean.

Regardless of the way Graeme put his point, I think having:
- a rough check on latest stable compiler
- a way to force the makefile to override the check for people who need
this such as SPARC users)
will lessen the amount of problems significantly


Thanks,
Reinier

_______________________________________________
fpc-pascal maillist  -  [hidden email]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
123