Hi,

I always updated source from svn and then build lazarus by "make LCL_PLATFORM=gtk2" but now this command doesn't work. I get error:

"The Makefile doesn't support target can't-executed,, please run fpcmake first. Stop"

Regards

What's this from- trunk? On what- Linux x86? How long's it been like this? Does it hurt when you cough?

Krzysztof hat am 29. August 2012 um 12:21 geschrieben:> Hi,

It works here.
What OS?
Please check via your svn tool that you don't have local modifications.

Try "make clean all LCL_PLATFORM=gtk2"

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120829/391263f9/attachment.html>

This is from trunk, but official release 1.0 has this problem too. But now I see that RC 2 branch has this problem too but 2 days ago it worked . Hmm it seems that something happened with my Free Pascal installation.

I have linux ubuntu 12.04 64 bit, stable FPC 2.6.0. I want remove FPC and install it again, but anyone know how to uninstall free pascal installed not from deb, but from instal.sh script included in FPC gz archive? "sudo ./install.sh uninstall" does nothing.

Krzysztof wrote

This is from trunk, but official release 1.0 has this problem too. But now I see that RC 2 branch has this problem too but 2 days ago it worked . Hmm it seems that something happened with my Free Pascal installation.

I don't see any problems in trunk directly related to gtk2, but have an error as shown below on 2.6.0 and 2.7.1... I'll look in more detail later.

Compiling sqlstringspropertyeditordlg.pas
..
Writing Resource String Table file: sqlstringspropertyeditordlg.rst registersqldb.pas(105,5) Fatal: Can't find unit sqldblib used by registersqldb
Fatal: Compilation aborted

I have linux ubuntu 12.04 64 bit, stable FPC 2.6.0. I want remove FPC and install it again, but anyone know how to uninstall free pascal installed not from deb, but from instal.sh script included in FPC gz archive? "sudo ./install.sh uninstall" does nothing.

Somebody put a list of the files to be deleted in one of the other mailing lists a few days ago, but I can't easily find it. In general I just delete the relevant directory from (e.g.) /usr/local/lib/fpc, and then look for any dangling symlinks in (e.g.) /usr/local/bin and check (e.g.) /etc/fpc.cfg.

Hmm seems that my last post to this discussion does not reached.

So after reinstall FPC, everything works fine

Krzysztof wrote

Hmm seems that my last post to this discussion does not reached. So after reinstall FPC, everything works fine

Trunk definitely needs a recent 2.7.1. RC1 and RC2 OK on 2.6.0 (i.e. current stable FPC) as expected.

Mark Morgan Lloyd hat am 29. August 2012 um

Trunk works fine with 2.6.0, and recent 2.6.1 and 2.7.1.

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120829/13471b49/attachment.html>

BTW two questions:
1. What is FPC 2.6.1? Is this stable version? If yes why on http://www.freepascal.org/ is 2.6.0 as latest? 2.6.1 is some patch?
2. When FPC 2.7.X is planned? We have now Lazarus 1.0, It would be nice if it worked with version 2.7.X

Since FPC and Lazarus are continuously developed, development versions (odd numbered) are always ahead of release versions (even numbered).

2.6.0 is the last FPC *release* (stable, well-tested, documented...). Lazarus 1.0 probably does compile with 2.7.x (I haven't tried this), but it does not require a 2.7. FPC, i. e. it does not use features introduced in the 2.7.x branch.

Howard

My understanding is as follows:

2.6.0 Current stable
2.6.2 Stable + fixes
2.7.x Development
2.8.0 Next stable

So 2.6.1 is 2.6.0 plus fixes which is considered to be unstable, and might later be rolled out as 2.6.2.

I think the notation comes originally from the Linux kernel where 2.4 and 2.6 were both stable but 2.5 was development. However kernel versions 2.6.0, 2.6.1 etc. were all equally intended as stable, while in the case of FPC the even/odd state of both the second and third numbers are significant.

It's important to appreciate that the next version after a hypothetical 2.6.9 is /not/ 2.7.0, it's 2.6.10: this has been a property of version control systems since the days of yore. For even murkier history, see http://www.udanax.com/green/febe/tumblers.html

But Morgan mentioned something about 2.7.1. RC1 (Release Candidate), so 2.7.1 will be stable or number finally jump to 2.8.0? For example Lazarus had 1.0 RC and stable is 1.0 too

But Morgan mentioned something about 2.7.1. RC1 (Release Candidate), so 2.7.1 will be stable or number finally jump to 2.8.0?

He was talking about FPC 2.7.1 and Lazarus 1.0 RC1, not about a FPC RC. 2.7.1 is the development version. When it will be released it will become 2.8.0.

R.

"Krzysztof" wrote

But Morgan mentioned something about 2.7.1. RC1 (Release Candidate), so 2.7.1 will be stable or number finally jump to 2.8.0? For example Lazarus had 1.0 RC and stable is 1.0 too

First we'll have a 2.6.2 release of 2.6.1 (which then turns to 2.6.3) and maybe also a 2.6.4 some months later. Only then we'll have a 2.8.0 or even 3.0.0. FPC's release cycles are quite long and definitely not coupled to those of Lazarus.

Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120830/afee71df/attachment.html>