[fpc-pascal] Warnings crti.o and crtn.o not found

waldo kitty wkitty42 at windstream.net
Mon Apr 15 10:48:37 CEST 2013

On 4/14/2013 15:22, Marco van de Voort wrote:
> In our previous episode, waldo kitty said:
>> that i can't say as i don't know :( hopefully someone with deeeper knowledge
>> will ring in... i just wanted to offer what i could in the hope that it might be
>> helpful...
>> as it is, i'm just now updating my winboxen to 2.6.2 from
>> http://svn.freepascal.org/svn/fpc/tags/release_2_6_2... i don't see a
>> fixes_2_6_2 branch so i guess the next release is going to be 2.8.0 from trunk??
> Releases are never done from trunk. First, a fixes (fixes_2_8 in this case)
> is created, and then a beta and a RC are done from that branch, and
> typically about 4-6 months after the fixes branchpoint there is a release.

ok... but that will be branched from trunk, right? if so, i used the wrong 
terminology when i said "from "trunk"...

> (e.g. fixes_2_6 was branched in may or june, and release january 1st the
> next year)

ok... was it branched from trunk or was is taken from elsewhere?

> Rule of thumb for fixes releases is that there will be one more release from
> the current fixes branch unless the new fixes branch has been created or
> will be created very shortly after.

right... i understand that ;)

> I've always assumed that the next release will be 2.6.4.

hummm... i can't keep up with it because so many projects do things so many 
different ways... i was thinking it would be 2.8.0 because of trunk being 
2.7.1... but then i've been trying to figure out what fixes_2_6 was for other 
than only providing fixes for 2.6.2...

More information about the fpc-pascal mailing list