Mailing lists / fpc-pascal / 2013-04
11 messages · 5 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi,
I just updated my FPC 2.7.1 from revision 23807 to 24236 and for every project I compile I now get warnings that crti.o and crtn.o are not found. Does anyone know why I suddenly get the warnings?
How do I get rid of the warnings?
This is on Ubuntu 12.10 AMD64.
R.
Reimar Grabowski wroteHi, I just updated my FPC 2.7.1 from revision 23807 to 24236 and for every project I compile I now get warnings that crti.o and crtn.o are not found.
based on prior discussions on these FPC/Lazarus lists, these are C runtime files...
2.7.1? that's trunk, right?
Does anyone know why I suddenly get the warnings?
have you looked at the commit messages?
How do I get rid of the warnings? This is on Ubuntu 12.10 AMD64.
maybe this commit??
Commit: 23892
Author: florian
Date: Sun Mar 17 14:51:19 2013 UTC (4 weeks ago) Changed paths: 4
Log Message: + warn if one of the linux libc startup code files is not found
Changed paths:
trunk/compiler/msg/errore.msg
trunk/compiler/msgidx.inc
trunk/compiler/msgtxt.inc
trunk/compiler/systems/t_linux.pas
2.7.1? that's trunk, right?
Yes.
Most likely.
Now the question remains why the files are not found. They are located in /usr/lib/x86_64-linux-gnu/.
R.
whew... viewvs made me walk thru every commit as i could not find a way to limit it to display only the commits for trunk... but i didn't look all that hard, either...
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??
i don't have trunk in place but might be able to do that shortly... this particular system is rather limited in drive space and it has to work first... then the other winboxen are mirrored from this one...
after that, i get to try (again) to figure out the best and easiest way to have lazarus for each installed FPC :?
On Sun, 14 Apr 2013 11:55:14 -0400 Yes. Most likely. Now the question remains why the…
i forgot to add to my previous that there's been other updates to trunk already... the latest commit was ~43 minutes ago from the time of this post...
24242 florian * better error reporting
which might tell more about this specific problem you are having... but the only file modified is trunk/compiler/classes.pas so i don't know...
I just updated my FPC 2.7.1 from revision 23807 to 24236 and for every project I compile…
I had this same problem a week or so ago:
To fix it I searched for those files and added the directory they were in to the library path. I hadn't had this problem until recently.
whew... viewvs made me walk thru every commit as i could not find a way to limit it to…
Click here http://svn.freepascal.org/cgi-bin/viewvc.cgi/ on the revision number next to "trunk".
The branch is called fixes_2_6
Regards,
Sven
whew... viewvs made me walk thru every commit as i could not find a way to limit it to…
In our previous episode, waldo kitty said:
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.
(e.g. fixes_2_6 was branched in may or june, and release january 1st the next year)
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.
I've always assumed that the next release will be 2.6.4.
Click here http://svn.freepascal.org/cgi-bin/viewvc.cgi/ on the revision number next to…
i tried that but it doesn't show me the files involved in the commit... clicking on directory listing link takes me to a listing of trunk and clicking on the commit number there takes me to the same page as before and around in circles we go...
ohhh... that's kinda confusing with there being fixes_2_6_0, too... what version is fixes_2_6 if trunk is 2.7.1?
In our previous episode, waldo kitty said: Releases are never done from trunk. First, a…
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...
i tried that but it doesn't show me the files involved in the commit... clicking on…
number
> next to "trunk". i tried that but it doesn't show me the files involved in the commit...
clicking on directory listing link takes me to a listing of trunk and clicking on the commit number there takes me to the same page as before and around in circles we go...
By clicking on the revision next to a directory you get to the commit log for that directory (with files the result is swapped). And when you click on a revision there you come to the changes of that specific revision.
version is fixes_2_6 if trunk is 2.7.1?
The fixes_2_6_0 was for last moment fixes before the release. The current version of fixes_2_6 is 2.6.3.
Regards,
Sven