controls.pp(473,1) Error: Internal error 200611031
Hello.. I´ve downloaded and installed Lazarus 2.0.6 x32 from sourceforge.net but Kaspersky found a Trojan-downloader.win32-upatre.iekl.. Did someone already reported?
2. The TShellTreeView was suppose to have an added OnAddItem event, never made it.
For me it looks exactly like the 2.0.4 with no changes except for what the release build and version number is.
* We have just ended the update to 2.0.4 (a bare month or so ago) in all our dev machines. You release too quickly for us ;D
2. The TShellTreeView was suppose to have an added OnAddItem event, never made it.
No, it was NOT supposed to have that in fixes branch, as I have explained to you before.
It is not a bugfix but a new feature, and therefore does not belong in the fixes branch.
If you really need this, you're probably OK with just copying shellctrsl.pas from trunk (nothing much else has changed).
Bart
Ok, I can go with that, but I also showed a problem with the LazHtmlhelp example and the problem file, which is a BUG!
I uploaded the fixed file with what I think was plenty of time to get it in there.
* We have just ended the update to 2.0.4 (a bare month or so ago) in all our dev machines. You release too quickly for us ;D
Well it's free software (as in free = freedom to ...).
You are free to update, but there is no force. ;)
If 2.0.4 works well for you, you can keep using it.
Have a nice day and thanks for the update, what ever it was that got updated.
Here is the list of fixes for Lazarus 2.0.x:
http://wiki.freepascal.org/Lazarus_2.0_fixes_branch (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch)
We try to keep up to date but there are two problems: 1) Too many machines (close to 50, IIRC) ..... and the mostly "static" CP/M dinosaurs.
We try to keep up to date but there are two problems: 1) Too many machines (close to 50, IIRC)I set one fpcupdeluxe based Lazarus on main dev pc, and when finished I just copy to the same dir on all other dev pc. Shortcut is copied, too. Lazarus is 32 bit (64 has some cross compilation issues), and running on WinXP, Win7 and Win10 machines. Some machines with 32-bit and some with 64-bit OS. I compile IDE with -O2 -g- -Xs -CpPENTIUM4 -CfSSE3 to have it running even on some very old WinXP machines with old CPUs. Once I set up the IDE, running it on all other machines takes less then an hour. Similar thing is with linux machines.
Oh, wow, CP/M, Lazarus on 50 machines ? Lucamar, you will have to tell us a bit more about what you do please ?
Anyway, given that 206 is (almost) exclusively fixes, if you are not being bitten by those particular bugs, why would you bother to update ?
CP/M ? really ?
Unable to install on macOS Catalina.We are aware of this. Last I heard was that there were some issues to create that installer. So some work is needed. No idea how long that will take.
@jwdietrich: Did you recompile as 32Bit Carbon-based or 64bit Cocoa based IDE?Pull requests for Fink packages for carbon, cocoa, gtk2, Qt4 and Qt5 are out. According to my minimal tests on Mojave, all work.
If 64 Bit, how are your experiences on MacOS Mojave?
Regretfully couldn't manage to be so glad with new Lazarus 2.0.6 at my Ubuntu 19.10.
I have downloaded all 3 files from SourceForge via your link, installed FPC 3.0.4 and its sources then installed "lazarus-project_2.0.6-0_amd64.deb" and started Lazarus. And Lazarus IDE had immediately frozen my desktop at all. I had to switch to another one with Ctrl-Alt-F8 and restart. Tried then to recompile Lazarus to Qt widgetset with "make clean all LCL_PLATFORM=qt" but had finally just a fatal error:
...
(9022) Compiling resource ../units/x86_64-linux/qt/lazarus.or
(9015) Linking ../lazarus
/usr/bin/ld: warning: ../link.res contains output sections; did you forget -T?
/usr/bin/ld: cannot find -lQt4Pas
/usr/share/lazarus/2.0.6/ide/lazarus.pp(165,1) Error: (9013) Error while linking
/usr/share/lazarus/2.0.6/ide/lazarus.pp(165,1) Fatal: (10026) There were 1 errors compiling module, stopping
Fatal: (1018) Compilation aborted
make[2]: *** [Makefile:4144: lazarus] Error 1
make[2]: Leaving directory '/usr/share/lazarus/2.0.6/ide'
make[1]: *** [Makefile:4572: ide] Error 2
make[1]: Leaving directory '/usr/share/lazarus/2.0.6/ide'
make: *** [Makefile:3381: ide] Error 2
So I must assume, new Lazarus is not happy with GTK2 and GTK3 (my current distro provided GTK 2.24.32 and GTK 3.24.12) and also it's not friendly with some Qt5 (namely Qt 5.12 with 5.62 libs as it comes with distro). For there's only Qt5 at my system, lQt4Pas can't be found in /usr/bin/ld which is a link to x86_64-linux-gnu-ld.bfd, I guess.
So what can you suggest for the case?
Do I need to downgrade to older GTK or Qt or there is a fix? I'd not like to dig into all these makefiles myself :(
Regretfully couldn't manage to be so glad with new Lazarus 2.0.6 at my Ubuntu 19.10.
I have downloaded all 3 files from SourceForge via your link, installed FPC 3.0.4 and its sources then installed "lazarus-project_2.0.6-0_amd64.deb" and started Lazarus. And Lazarus IDE had immediately frozen my desktop at all. I had to switch to another one with Ctrl-Alt-F8 and restart. Tried then to recompile Lazarus to Qt widgetset with "make clean all LCL_PLATFORM=qt" but had finally just a fatal error:
Ariador, are your trying QT because of the freeze-ups ? The problem is not the widget set, there is "some issue" with U1910 I am afraid. GTK2 works fine on other distros and even other Ubuntu desktops but is very prone to do this freeze up on the default Gnome Desktop. People have found it works better using Wayland as display server (click the small gear symbol under the password field during log on and select Ubuntu on Wayland. GTK3 is experimental and quite a bit dodgy on Wayland by the way.AFAIK, with U1910 they switched Gnome to GTK3 as the "standard"-widget-set.
https://forum.lazarus.freepascal.org/index.php/topic,47240.0/topicseen.html
Davo
Ariador, are your trying QT because of the freeze-ups ? The problem is not the widget set, there is "some issue" with U1910 I am afraid. GTK2 works fine on other distros and even other Ubuntu desktops but is very prone to do this freeze up on the default Gnome Desktop. People have found it works better using Wayland as display server (click the small gear symbol under the password field during log on and select Ubuntu on Wayland. GTK3 is experimental and quite a bit dodgy on Wayland by the way.
https://forum.lazarus.freepascal.org/index.php/topic,47240.0/topicseen.html
Davo
Ariador, are your trying QT because of the freeze-ups ? The problem is not the widget set, there is "some issue" with U1910 I am afraid. GTK2 works fine on other distros and even other Ubuntu desktops but is very prone to do this freeze up on the default Gnome Desktop. People have found it works better using Wayland as display server (click the small gear symbol under the password field during log on and select Ubuntu on Wayland. GTK3 is experimental and quite a bit dodgy on Wayland by the way.
https://forum.lazarus.freepascal.org/index.php/topic,47240.0/topicseen.html
Davo
I've tested qt and qt5 under ubuntu 19.10 today and all I can say it works out of the box (default ubuntu 19.10) installation. Haven't tested with wayland since x11 is started as default. Even libQt5Pas is recent 1.2.7 version :)
AFAIK, with U1910 they switched Gnome to GTK3 as the "standard"-widget-set.GTK3 has been the 'standard' widgetset for some time. Its just that they are now no longer also including GTK2 in there. It needs to be added by you or as a result of a dependency check. Easy to resolve at the expense of a short download.
...Raspbian...
It would be nice if somebody could write an installer for Raspbian (the Debian incarnation for the Raspberry)...Raspbian Buster has already fpc3.0.4 and Laz 2.0 in the repositories.
I would do it myself, but lack the needed skills...
TNX
Alberto
....
Then build make clean all install useride.
Actually /usr/local where it belongs! e.g. fpcdeluxe has a non-conformant install... Follow the guidelines unless you need multiple parallel installs, usually advanced users. And even that is debatable because FPC installs to a versioned directory.
Disagree, 'install' is quite unnecessary, from memory it wants to push everything up unto /usr/ again.
And 'bigide' gets you the OnlinePackage Manager (unless I am mistaken).Bigide installs way too much and OPM can be installed afterwards. Two clicks away. Bigide is not a good idea on very basic, resource starved platforms like a Raspberry Pi, unless you have a Pi4 with 4 GB.
'useride' is a new one on me.Now you know. It is usually the better option for existing installs.
Actually /usr/local where it belongsThink you are confusing fpc and lazarus, never mind.
Bigide installs way too much and OPM can be installed afterwards. Two clicks away.OK, that makes sense. Thanks
If you are actually using Raspberry Pi's you will know this is sound advice.While I know its probably sound advice, I have never tried to use a Pi interactively. I have a couple running some 'housekeeping tasks' written in Python but never tried FPC on there. Thats why I am trying, politely, to collect some information about how to do it. And get that information on the wiki.
I've tested qt and qt5 under ubuntu 19.10 today and all I can say it works out of the box (default ubuntu 19.10) installation. Haven't tested with wayland since x11 is started as default. Even libQt5Pas is recent 1.2.7 version :)
FPC/Laz installed from Repo or from deb's?
Asking because i don't know if install from deb's forces dependency-install of libqt5pas
Error: Internal error 200611031
I'm using Linux Mint 19.1 Tessa. Ever since 1.8 I've been installing Lazarus using the .deb downloads from SourceForge - with gdebi-gtk. My problem with 2.0.6 is I get this error when I build:QuoteError: Internal error 200611031
At line 469 of /usr/share/lazarus/2.0.6/lcl/controls.pp.
@delI was just throwing the dice - somebody somewhere else mentioned that deleting some blank lines allowed a successful build. I added the comment with the same idea, thinking that maybe an uninitialized variable would take on a different random value and the error wouldn't happen. I can repeat the condition with another install if that would help answer any questions. At any rate I'm a happy camper.
So you triggered a change in a file there by forcing a rebuild of the files and now it works.
that tells me the BIN files don't match the source files, I've seen this before.
I was just throwing the dice - somebody somewhere else mentioned that deleting some blank lines allowed a successful build. I added the comment with the same idea, thinking that maybe an uninitialized variable would take on a different random value and the error wouldn't happen. I can repeat the condition with another install if that would help answer any questions. At any rate I'm a happy camper."make clean" would have done it.
I do "make clean" several times each day at work for C++ stuff. I didn't know it was an option with Lazarus. I did try "Clean up and Build ...". I'm probably not gonna have a fresh OS in a while, but I'm curious about the "make clean" for future reference. I'll uninstall and reinstall 2.0.6 to see if the problem comes back. Then I'll try "make clean". Not sure how to do that but one step at a time.I was just throwing the dice - somebody somewhere else mentioned that deleting some blank lines allowed a successful build. I added the comment with the same idea, thinking that maybe an uninitialized variable would take on a different random value and the error wouldn't happen. I can repeat the condition with another install if that would help answer any questions. At any rate I'm a happy camper."make clean" would have done it.
The compiler compiles each units, and maintains ppu files (with checksums to know when they are outdated).
And (most likely) something goes wrong there. A ppu is outdated, but not detected. It could be circular, then changing this file may affect the other ppu.
It is hard to say exactly what happens, since it happens at random.
If you have exact steps, how to reproduce on a system on which there never ever before was any fpc or Lazarus (maybe a fresh installed OS), then you should report it with those steps on the fpc bugtracker.
I do "make clean" several times each day at work for C++ stuff. I didn't know it was an option with Lazarus. I did try "Clean up and Build ...". I'm probably not gonna have a fresh OS in a while, but I'm curious about the "make clean" for future reference. I'll uninstall and reinstall 2.0.6 to see if the problem comes back. Then I'll try "make clean". Not sure how to do that but one step at a time.If the error is in LCL or packages, you can open the package, and from the toolbar "more" choose "recompile clean".
That may not be enough if it is dependent packages.... Go to menu Tools > Configure build Lazarus.
And there is a radio box "clean all" and you can rebuild the IDE, and with it most packages.
But changing the file did:
But changing the file did:
I have the same issue regurarly in some win32wsmenus.pp (happens almost everytime I edit grids.pas and thenrebuild LCL).
What helps for me is just adding an invalid token (e.g. an 'X') at the point the caret is in that file (win32wsmenus.pp)
Recompile -> syntax error.
Remove the invalid token
Recompile: OK.
It's faster than doing a clean build.
Bart
I love learning the Old Indian Tricks.But changing the file did:
I have the same issue regurarly in some win32wsmenus.pp (happens almost everytime I edit grids.pas and thenrebuild LCL).
What helps for me is just adding an invalid token (e.g. an 'X') at the point the caret is in that file (win32wsmenus.pp)
Recompile -> syntax error.
Remove the invalid token
Recompile: OK.
It's faster than doing a clean build.
Bart
Woow :o :o :o
I love learning the Old Indian Tricks.But changing the file did:
I have the same issue regurarly in some win32wsmenus.pp (happens almost everytime I edit grids.pas and thenrebuild LCL).
What helps for me is just adding an invalid token (e.g. an 'X') at the point the caret is in that file (win32wsmenus.pp)
Recompile -> syntax error.
Remove the invalid token
Recompile: OK.
It's faster than doing a clean build.
Bart
Woow :o :o :o
:D
This versione is not compatible with Catalina 64bit.
Try using FPCUpDeluxe and install in a user folder.
And you have to switch off GateKeeper.
This versione is not compatible with Catalina 64bit.
I install the files from https://sourceforge.net/projects/lazarus/files/Lazarus%20macOS%20x86-64/
installation is abort for this programs: LazarusIDE-2.0.6-macos-x86_64.pkg and fpc-3.0.4-macos-x86_64-laz.pkg
[[/li][li]There should be a clear warning when attempting to download the macOS version that it's not yet compatible with Catalina[/li][/list]What *exactly* are the problems, because I can not reproduce them...(I did not test cross- compilation yet)
[
Were you able to install fpc-3.0.4-macos-x86_64-laz.pkg ?
Are there any error messages in /var/log/install.log?
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: @(#)PROGRAM:Install PROJECT:Install-1000
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: @(#)PROGRAM:Installer PROJECT:Installer-965.1
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Hardware: Macmini8,1 @ 3.20 GHz (x 12), 16384 MB RAM
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Running OS Build: Mac OS X 10.15.1 (19B88)
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: fpc-macos-x86-64-laz Installation Log
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Opened from: /Users/will/Downloads/fpc-3.0.4-macos-x86_64-laz.pkg
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Package Authoring Error: <layout-direction> has an unsupported MIME type: X-NSObject/NSNumber
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Failed to load specified background image
Nov 13 23:06:31 Mac-mini-2018 Installer[1598]: Could not load resource readme: (null)
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: ================================================================================
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: User picked Standard Install
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: Choices selected for installation:
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: Install: "fpc-macos-x86-64-laz"
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: Install: "fpc-macos-x86-64-laz"
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: ================================================================================
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: Configuring volume "macOS SSD"
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: Free space on "macOS SSD": 155.46 GB (155457888256 bytes).
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: Create temporary directory "/var/folders/dn/2kt85pb54pbf4yff9_62070m0000gp/T//Install.1598Zrixdd"
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: IFPKInstallElement (1 packages)
Nov 13 23:06:43 Mac-mini-2018 Installer[1598]: PackageKit: Enqueuing install with framework-specified quality of service (utility)
Nov 13 23:06:43 Mac-mini-2018 installd[1222]: PackageKit: ----- Begin install -----
Nov 13 23:06:48 Mac-mini-2018 installd[1222]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “fpc-3.0.4-macos-x86_64-laz.pkg”." UserInfo={NSFilePath=./postinstall, NSURL=file:///Users/will/Downloads/fpc-3.0.4-macos-x86_64-laz.pkg#fpc-macos-x86-64-laz.pkg, PKInstallPackageIdentifier=org.freepascal.pkg.fpc-macos-x86-64-laz, NSLocalizedDescription=An error occurred while running scripts from the package “fpc-3.0.4-macos-x86_64-laz.pkg”.} {
NSFilePath = "./postinstall";
NSLocalizedDescription = "An error occurred while running scripts from the package \U201cfpc-3.0.4-macos-x86_64-laz.pkg\U201d.";
NSURL = "file:///Users/will/Downloads/fpc-3.0.4-macos-x86_64-laz.pkg#fpc-macos-x86-64-laz.pkg";
PKInstallPackageIdentifier = "org.freepascal.pkg.fpc-macos-x86-64-laz";
}
Nov 13 23:06:48 Mac-mini-2018 Installer[1598]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Nov 13 23:06:48 Mac-mini-2018 Installer[1598]: IFDInstallController 33B2B80 state = 8
Nov 13 23:06:48 Mac-mini-2018 Installer[1598]: Displaying 'Install Failed' UI.
Nov 13 23:06:48 Mac-mini-2018 Installer[1598]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.
What *exactly* are the problems, because I can not reproduce them...(I did not test cross- compilation yet)
It doesn't install. That's a pretty big problem. :Pon its own is not very helpful.
Installing the latest FPC does not work. It fails with the error: "Install failed. The installer encountered an error that caused the install to fail."
Mattias, please test "Lazarus" in new machine with Catalina!
I installed in new machine
3) Tools XCode
Did you run in a terminal before installing:
xcode-select --install
?
Note for others: This is not an official FPC release. I repackaged it using the x86-64 files from the FPC 3.0.4a release.
I'm wondering -- why can't the macOS version just be completely packaged in a Lazarus.app bundle? I mean, FPC, FPC-SRC and Lazarus all together in one app bundle, then it can just be dragged to the Applications folder instead of doing an install? :)
As the FPC team has not yet created a Catalina release yet I had to create one. The FPC 3.2 release will hopefully provide a macOS package for Catalina, which Lazarus can then use.
"ld: file not found: /usr/lib/crt1.10.5.o'
No, this line doesn't exist.
To my shame I cannot edit fpc.cfg in Catalina. No file rights.
I own this Macbook, just can't remember how to edit /etc/fpc.cfg - macOS doesn't allow modify this file.On a Terminal elevate yourself to superuser (su/sudo)?
I own this Macbook, just can't remember how to edit /etc/fpc.cfg - macOS doesn't allow modify this file.
"ld: file not found: /usr/lib/crt1.10.5.o'
Does your fpc.cfg contain
-XR/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk?
So it seems that re-compiled Lazarus in Catalina appears in another folder, and doesn't replace original files of Lazarus, as it was in Mojave.Yes, it goes into the user conf folder.
nope, its not stopped, its going very strongly... Working out the bugs for the next release :DDid you mean "removing bugs"?
does this application now stop? because I saw the website has not been updated since launching version 2.0.6
nope, its not stopped, its going very strongly... Working out the bugs for the next release :DDid you mean "removing bugs"?
Or did you (as the smiley might suggest) indeed mean "working out" (i.e., "arranging for")?
Can anyone give proof that this is false for GNU LINUX OS :
For first time I tried 64 bit version and there is some problem with recompiling IDE, it recompile IDE with new packages (e.g. anchordocking) but after new start nothing happend. It's same as previous. I also tried packages from online package manager, clean&build etc. No errors in outputsounds like using wrong "startlazarus"
In 32bit it's working fine.
(Windows 10 64bit)
No, I don't mean that. I mean using menu "Tools>Options..." it raises the exception, but I can right-click in some parts (for example the source code editor) to access to part of the configuration.Unless you're talking about Lazarus running in 19.10. Then I have only one issue (https://forum.lazarus.freepascal.org/index.php/topic,47269.msg350743.html#msg350743) with it (still not crashing though).Yeah, I saw that post. I was not sure what you meant by the "configuration dialog via menu", is that the dialog that pops up the first time you run a new install ? I guess you installed from a deb, did you use the startlazarus command ?
Great results with Manjaro (Linux). I switched over to Manjaro and using its package manager (pamac-manager) was very easy. Lazarus version 2.0.6-2, and the Help-About in Lazarus said it was built today (2020-03-22). That's pretty current. And the Lazarus Online Package Manager installed BGRABitmapPack with no hiccups. This is the easiest install I've ever done!Lazarus maintainer in Manjaro team seems to be a saner person than the one in that more well known distro.
Hello. When will the Lazarus 2.0.8 be released?
......
The energy now goes towards the next major version, Lazarus 2.2, which will be branched around the time FPC 3.2 gets released. Then there will be release candidates before the actual release.
If we see a Lazarus 2.2.0 release, will it be based on Lazarus trunk or Lazarus fixes ? While the process is clear in the minds of the developers, it would help people like me if it was a bit more transparent.It is completely transparent. Every trunk revision backported to fixes_2_0 branch is listed here :
Juha, thanks, I am sure the information I asked for is also in the wiki page you quote. Somewhere in that page....The process itself is explained here :
(I have looked at that page from time to time, at no point did I come away with the information I asked about. But I am sure its there.)